[mythtv-users] mythwelcome / mythshutdown / hibernate / mythtv 0.26 / fedora 16

[dlknight2]

Hello folks,

Haven't been along in awhile, I upgraded from mythtv 0.24.3 fixes about 
a week ago to 0.26 fixes. I'm really enjoying the new music player but 
I've noticed a problem with my hibernate scripts which have been working 
fine on this box for about 5 years. From the number of experiments I 
have undertaken it appears that when mythtv triggers the shutdown event 
(e.g. mythshutdown --check returns 0) the hibernate script is executed 
but stalls because mythwelcome does not close. By

My system is a combined BE/FE with no additional BEs or FEs, my mythtv 
user has sudo (without password) privileges to required programs e.g. 
mythshutdown and hibernate programs.

The script I run pre-hibernate does the following -

killall -w -q mythwelcome
systemctl stop mythbackend.service

I can see the killall -w is listed in the process monitor and does not 
complete as it is waiting for mythwelcome to gracefully shutdown which 
never happens (have left system 24 hours). I get the idle countdown from 
120 - 0 seconds and the script is launched (viewing the backend log) but 
gets stuck waiting for mythwelcome to close.

Then the hibernate script does a bunch of things including unloading 
the DVB drivers (otherwise they do not work after the restart).

If I manually kill mythwelcome (having to execute the kill command 
twice) and run the hibernate script manually then all works as expected.

I'm pretty sure that if I reverted to mythtv 0.24.3 the problem would 
be gone, I'm happy to test this theory as I have database backups and 
also the RPMs still for 0.24.3.

Looking in the mythwelcome log the only events that are logged after 
the shutdown attempt are -

mythwelcome[1746]: I CoreContext mythmainwindow.cpp:2537 
(LockInputDevices) Locking input devices
mythwelcome[1746]: I CoreContext mythmainwindow.cpp:2539 
(LockInputDevices) Unlocking input devices

I've done some searches and found a similar issue reported by other 
users relating to EIT. I do have EIT enabled so I have extended the 
timeout before initiating a scan to 600 seconds and my timeout for 
shutdown of mythtv is 120 seconds.

I'm launching mythwelcome from a KDE Autostart script as I have done 
for the last 5 years or so.

Thanks

Dave K.