[mythtv-users] Mythbuntu 16.04.1 (0.28) Frontend not visible

[Stephen Worthington]

On Sat, 12 Nov 2016 09:36:17 +1100, you wrote:

>
>
>-----Original Message-----
>From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of
>Michael T. Dean
>Sent: Thursday, 10 November 2016 11:26 PM
>To: Discussion about MythTV <mythtv-users at mythtv.org>
>Subject: Re: [mythtv-users] Mythbuntu 16.04.1 (0.28) Frontend not visible
>
>On 11/10/2016 12:01 AM, Andrew Potter wrote:
>>
>> OK I had Mythbuntu 14.04 and wanted to upgrade to Mythbuntu 16.04 LTS.
>>
>> I downloaded the 16.04.1 ISO and installed on a fresh SSD drive. 
>> Keeping the old disk as this is a production system.
>>
>> After the installation I restored the old Database (14.04 database) 
>> tot he new system. I can see in the logs that the database was 
>> upgraded and the settings all look to be correct via myth-setup.
>>
>> But the local frontend does not get to the display screens. I have to 
>> hot alt-f4 and I get the this window is busy dialog do you wan t to 
>> stop it.
>>
>> I have looked at the front end logs but cannot see anything
>>
>> The last log I see is about successfully reading the airplay rsa key.
>>
>> The logs are available here http://pastebin.com/KvnVSX4w
>>
>> I am thinking it is possibly a QT issue, ie not rendering a display 
>> correctly, but I do not know enough to diagnose. Of course I could 
>> also be well off the mark.
>>
>> Any help is greatly appreciated.
>>
>
>You're killing mythfrontend in the middle of the MythMusic database schema
>upgrade (specifically--at least in the logs provided--during the backup it's
>making before the upgrade).  If you let it run farther in any previous runs,
>it may have gotten into the middle of the upgrade, at which killing
>mythfrontend may have done bad things.  Remember that the
>backend/mythtv-setup upgrades the TV schema.  All plugin schemas are
>upgraded by the plugins themselves, which run inside the frontend.
>
>In other words, you need to look at more than the last line in the
>log--2 lines before it said what was happening.
>
>Nov 10 08:48:46 Master-Backend mythfrontend.real: mythfrontend[6935]: E
>CoreContext dbutil.cpp:604 (DoBackup) Backing up database with script: 
>'/usr/share/mythtv/mythconverg_backup.pl'
>
>So, you just need a bit more patience when upgrading versions, because
>backing up the database takes quite a bit of time, even if the upgrades go
>quickly (and they don't always).  (And, yes, ideally mythfrontend would tell
>you what's happening, but until someone completely
>redesigns/refactors/rewrites our database upgrade code, we don't have access
>to the (new) UI at the time when we're doing the upgrade, so we can't put up
>any messages.)
>
>Mike
>
>
>OK,
>
>Tried running the frontend from a terminal session using 
>
>frontend -v gui
>
>It seemed to do the same thing but I got the following logs only on the
>terminal , not in the actual frontend logs.
>
>
>2016-11-12 08:46:59.178493 C  Backed up database to file:
>'/mnt/NAS/Public/mythconverg-1344-20161111213327.sql.gz'
>ICE default IO error handler doing an exit(), pid = 3369, errno = 32
>QWaitCondition: cv destroy failure: Device or resource busy
>QWaitCondition: mutex destroy failure: Device or resource busy
>andrew at Master-Backend:~$
>
>
>I checked on the net and tried renaming the .ICEauthority file to
>.ICEauthorityold
>Then ran 
>
>Frontend -v gui again
>It went through the database backup again and then Got the dame thing 
>
>??
>
>Andrew

It looks like you may need to change where your database backup files
are stored, as the backup done by mythfrontend seems to be failing,
likely as a result of it not having the right access rights to write
to your NAS.  If you run mythtv-setup, you can change the storagegroup
setting for "DB Backups" to point to a location that mythfrontend is
able to do a backup to.