https://bugs.kde.org/show_bug.cgi?id=523064
Bug ID: 523064
Summary: Inhibiting via DBus does nothing
Classification: Plasma
Product: plasmashell
Version First 6.7.2
Reported In:
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Power management & brightness
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
DESCRIPTION
Using DBUS to inhibit power saving via the standard interface,
results in a confirmation of success of inhibition,
but does not actually inhibit.
STEPS TO REPRODUCE
1. Run: qdbus org.freedesktop.PowerManagement.Inhibit
/org/freedesktop/PowerManagement/Inhibit
org.freedesktop.PowerManagement.Inhibit.Inhibit "$someExecutableFilePath"
SomeReason # In my case, inside the shell script $someExecutableFilePath.
2. Observe how a number is returned, suggesting success and an active
inhibition that can be removed again by using that handle.
2. Click on the GUI system tray icon for power.
OBSERVED RESULT
A panel opens, with a switch to inhibit power saving,
but no indication of above inhibition.
And the system will go to power saving after the configured delay.
EXPECTED RESULT
It should behave the same as if
elogind-inhibit --no-pager --no-legend --mode=block
--who="$someExecutableFilePath" --why="SomeReason" "$someExecutableFilePath"
had been executed, and $someExecutableFilePath was still running.
SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.18 (updated last Friday)
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
The elogind-inhibit does work, but only is active as long as
$someExecutableFilePath is kept running.
So it is not designed to be used with a handle, unlike the above DBUS call.
But AFAIK it should internally also just execute the above DBUS call, so this
is strange.
This bug existed for a bit. So since earlier versions than 6.7.2. But I don’t
know the exact moment.
So it is very unlikely that the bug is gone in later versions.
I have also checked for delays in the panel (see below) getting the info, of up
to 60 seconds. (I don’t understand why it could even be delayed, unless it was
using a polling system instead of an interrupt system to receive updates.)
--
You are receiving this mail because:
You are watching all bug changes.
