[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=381160

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=381160

--- Comment #5 from Kishore Gopalakrishnan  ---
(In reply to David Edmundson from comment #4)
> xdg-screensaver is a script that does different things for each desktop.
> 
> The one that tries to use the standard fd.o interface is just completely
> wrong.
> 
> From the spec:
> "Inhibition will stop when the UnInhibit function is called, or the
> application disconnects from the D-Bus session bus (which usually happens
> upon exit)."
> https://people.freedesktop.org/~hadess/idle-inhibition-spec/ch03.html
> 
> 
> dbus-send (called from the xdg-screensaver script) exits immediately after
> sending
> 
> We follow the fd.o spec so correctly remove the inhibition.
> 
> xdg-screensaver needs fixing, not plasma.
> 
> Please report to freedesktop.org
> 
> (FWIW, code to xdg-screensaver is here:
> https://cgit.freedesktop.org/xdg/xdg-utils/tree/scripts/xdg-screensaver.in)

I've reported the bug here
(https://bugs.freedesktop.org/show_bug.cgi?id=102124), but since I don't know
much about the issue, I just copied your comment #4 from above. Could you
please add a comment there in case I've missed any relevant information?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=381160

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM
 CC||k...@davidedmundson.co.uk

--- Comment #4 from David Edmundson  ---
xdg-screensaver is a script that does different things for each desktop.

The one that tries to use the standard fd.o interface is just completely wrong.

>From the spec:
"Inhibition will stop when the UnInhibit function is called, or the application
disconnects from the D-Bus session bus (which usually happens upon exit)."
https://people.freedesktop.org/~hadess/idle-inhibition-spec/ch03.html


dbus-send (called from the xdg-screensaver script) exits immediately after
sending

We follow the fd.o spec so correctly remove the inhibition.

xdg-screensaver needs fixing, not plasma.

Please report to freedesktop.org

(FWIW, code to xdg-screensaver is here:
https://cgit.freedesktop.org/xdg/xdg-utils/tree/scripts/xdg-screensaver.in)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=381160

David Edmundson  changed:

   What|Removed |Added

 CC||kdeb...@fratti.ch

--- Comment #3 from David Edmundson  ---
*** Bug 383296 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381160

--- Comment #2 from kishor...@gmail.com ---
(In reply to Kai Uwe Broulik from comment #1)
> When I run xdg-screensaver from console I can see it telling
> org.freedesktop.ScreenSaver on DBus which in turn tells PowerDevil.  Then it
> immediately uninhibits because the application (xdg-screensaver) that
> requested the inhibition quit.
> 
> powerdevil: Scheduling inhibition from ":1.10" "0x5a5" with cookie 1 and
> reason "xdg-screensaver"
> powerdevil: Releasing inhibition with cookie  1
> 
> I don't actually have mpv installed here, so I don't know if this behavior
> applies to it at all. I just don't understand why the inhibition still holds
> after it, screen locker also uninhibits in this case. Are you sure the
> inhibition is applied? Perhaps it's doing another thing (simulate user
> activity) repeatedly.
> 
> In any case the "appName" which is ":1.10" with reason "xdg-screensaver" is
> just plain wrong and perhaps that causes the issue of it not showing up,
> ":1.10" is not a valid application name after all.

It seems mpv calls 'xdg-screensaver reset' at regular intervals
(https://github.com/mpv-player/mpv/issues/3851).

However, as a test, I got the window ID of my konsole window using 'xwininfo',
and then ran 'xdg-screensaver suspend 0x386' (0x386 was the window ID).
I was still not able to see any notification in the battery monitor plasmoid or
any new messages in my system logs (running 'journalctl -f').

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[Kai Uwe Broulik]

https://bugs.kde.org/show_bug.cgi?id=381160

--- Comment #1 from Kai Uwe Broulik  ---
When I run xdg-screensaver from console I can see it telling
org.freedesktop.ScreenSaver on DBus which in turn tells PowerDevil.  Then it
immediately uninhibits because the application (xdg-screensaver) that requested
the inhibition quit.

powerdevil: Scheduling inhibition from ":1.10" "0x5a5" with cookie 1 and
reason "xdg-screensaver"
powerdevil: Releasing inhibition with cookie  1

I don't actually have mpv installed here, so I don't know if this behavior
applies to it at all. I just don't understand why the inhibition still holds
after it, screen locker also uninhibits in this case. Are you sure the
inhibition is applied? Perhaps it's doing another thing (simulate user
activity) repeatedly.

In any case the "appName" which is ":1.10" with reason "xdg-screensaver" is
just plain wrong and perhaps that causes the issue of it not showing up,
":1.10" is not a valid application name after all.

-- 
You are receiving this mail because:
You are watching all bug changes.