[mythtv-users] Potential issues with Qt 5.7.1?

[Stuart Auchterlonie]

On 21/12/16 22:33, Tom Dexter wrote:
> On Wed, Dec 21, 2016 at 10:33 AM, Stuart Auchterlonie
> <stuarta at squashedfrog.net> wrote:
>> On 21/12/16 13:29, Tom Dexter wrote:
>>> On Wed, Dec 21, 2016 at 5:33 AM, Stuart Auchterlonie
>>> <stuarta at squashedfrog.net> wrote:
>>>>
>>>> Works just fine on Fedora 25.
>>>>
>>>> It's a shame you don't want DBus, that's how we now control the
>>>> screensaver, and it works nicely.
>>>>
>>>>
>>>> Regards
>>>> Stuart
>>>>
>>>
>>> I upgraded yesterday and everything seems to be working great. I'm a
>>> little confused regarding screensaver. I'm using xscreensaver within
>>> fluxbox and that always seems to work fine. Is that using alternate
>>> methods when dbus isn't in use? I have almost as little desire to use
>>> dbus as I do for systemd frankly.
>>>
>>
>> xscreensaver is the "legacy" way and does still work. I kept that on
>> purpose to not break existing setups. For new systems where that isn't
>> installed by default, the dbus method has the advantage that it
>> "just works" without the user having to install an additional
>> package.
>>
>> As interfaces go, it's much cleaner than xscreensaver.
>>
>> It fixes the issue where the screensaver would stay disabled if the
>> frontend crashed out without restoring the screensaver state.
>> With the DBus API, DBus knows the client (ie. the frontend) has gone
>> away and there for cleans up and restores the screensaver state.
>>
>> But i'm not going to force you to use it :)
>>
>>
>> Cheers
>> Stuart
>>
> Ahh...got it. Thanks for the clarification! I have noticed one issue
> on some rare cases where the frontend has crashed. I have my frontend
> login configured (as others do in Gentoo sometimes) to respawn via
> inittab. Sometimes after a crash, xscreensaver will not exit screen
> saver mode as a result of the LIRC remote...just via the keyboard. Is
> that related to the issue you're referring to or does that sound like
> something else?
> 

Does sound similiar. IIRC the way the xscreensaver code works is it
just runs xscreensaver to disable and enable the screensaver, and also
uses it to "poke" the screensaver. If the crash occurs after the disable
then the screensaver remains disabled.

I ended up implementing it because the other old way was using the
xdpms calls, and that had stopped working from about Fedora 23. The code
thought it had worked, but it never inhibited the screensaver.

It's part of my ongoing desire to make mythtv "just work" when it's
installed.

Regards
Stuart