Re: Preferred way for an application to inhibit suspend on KDE
- Date: Sun, 22 Jan 2017 17:30:50 +0700
- From: elboulangero <elboulangero@xxxxxxxxx>
- Subject: Re: Preferred way for an application to inhibit suspend on KDE
Just a follow-up.
On a fresh Neon install from the image
and after booting a few times, I can say that sometimes PowerManagement
is present on the bus, sometimes it is not.
When it's here, I can see both of the well-kown dbus names:
'org.freedesktop.PowerManagement' and 'org.kde.Solid.PowerManagement'.
When it's not here, none of these names are present on the bus.
On 01/21/2017 09:51 AM, elboulangero wrote:
>> If you are on a dev edition it's probably a temporary bug. User
>> edition should work fine.
> Well I downloaded the KDE Neon "User LTS Edition" from 2016-12-29. Now,
> I noticed on the website that there's another LTS edition from
> 2017-01-19, and I'm starting to wonder if the LTS edition might be a
> daily snapshot...
> Anyway, I'm grabbing this 2017-01-19 right now, whatever dev/daily/lts
> edition it might be, then I'll let you know if PowerManagement is back.
>> Also it was pointed out on IRC that login1 might not work with plasma
>> as the power manager tells login1 to sod off. Whether or not that is
>> in fact the case I do not know though ^^
> I already noticed that, although I'm not on KDE. But on my simple
> Openbox setup, where PowerManagement daemon is running, using
> `systemd-inhibit`has no effect. So I figured something like that...