mythbuntu-bugs team mailing list archive
-
mythbuntu-bugs team
-
Mailing list archive
-
Message #02745
[Bug 574877] Re: Shutdown doesn't work from frontend in MythTV 0.23
@hinkie, This issue seemed to be targeted towards "Shutdown". If you
have an interest in the addition of a "Suspend" feature, Please can you
open a new bug. Thanks :)
--
Shutdown doesn't work from frontend in MythTV 0.23
https://bugs.launchpad.net/bugs/574877
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in ubuntu.
Status in MythTV: Fix Released
Status in “mythtv” package in Ubuntu: Fix Released
Bug description:
Binary package hint: mythtv
Since 0.23.0+fixes24158-0ubuntu2, a patch has been applied which causes mythtv to use DBus to attempt to shut down the system. Whilst this is a step in the right direction for the 'doing it right' argument. It breaks existing behaviour and causes dependencies which don't appear to be satisfied by the mythtv package itself.
Case in point;
My set-up was a custom installed ubuntu lucid system. Installed with minimal X and only whatever else I could get away with. Before this patch came in, I was using two custom commands to shut down and restart the system. Now they no longer work, and the dbus method appears to not work either. The only way I can shutdown currently is to log into the system and issue the command manually. The 'dbus' package is already installed, but it appears to not be enough to make this work. I do not know which package needs installing or configuring and this may add extra overhead this system cannot afford.
No error messages appear at all to tell me why anything has failed, so I have not included logs.
This patch appears to have made it in very late in Lucid's development cycle. At the very least the extra dependencies need to be added to the mythtv package so the system can shutdown and reboot. Ideally, I feel this update should be reversed until it has received more testing, as it did suddenly break a couple of machines when a feature freeze was in effect.
The behaviour in ubuntu1 version was fine, and worked as expected.
References