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" "0x5a00005" 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 0x3800006' (0x3800006 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.
