https://bugs.kde.org/show_bug.cgi?id=479195
--- Comment #4 from Eevee <eevee.kdeb...@veekun.com> --- Same procedure but with dbus-monitor running, and the only mentions of org.freedesktop.ScreenSaver are: # starting love method call time=1710791833.031274 sender=:1.9319 -> destination=org.freedesktop.ScreenSaver serial=6 path=/org/freedesktop/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=Inhibit string "My SDL application" string "Playing a game" method call time=1710791833.031619 sender=:1.12 -> destination=org.kde.Solid.PowerManagement.PolicyAgent serial=366224 path=/org/kde/Solid/PowerManagement/PolicyAgent; interface=org.kde.Solid.PowerManagement.PolicyAgent; member=AddInhibition uint32 4 string "My SDL application" string "Playing a game" ... # locking signal time=1710791840.483870 sender=:1.14 -> destination=(null destination) serial=39716 path=/component/ksmserver; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "ksmserver" string "Lock Session" int64 243112269 signal time=1710791840.484068 sender=:1.12 -> destination=(null destination) serial=366228 path=/ScreenSaver; interface=org.kde.screensaver; member=AboutToLock signal time=1710791840.484073 sender=:1.12 -> destination=(null destination) serial=366229 path=/org/freedesktop/ScreenSaver; interface=org.kde.screensaver; member=AboutToLock signal time=1710791840.573955 sender=:1.14 -> destination=(null destination) serial=39717 path=/component/ksmserver; interface=org.kde.kglobalaccel.Component; member=globalShortcutReleased string "ksmserver" string "Lock Session" int64 243112269 ... # locking finished...? signal time=1710791842.146249 sender=:1.12 -> destination=(null destination) serial=366230 path=/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=ActiveChanged boolean true signal time=1710791842.146273 sender=:1.12 -> destination=(null destination) serial=366231 path=/org/freedesktop/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=ActiveChanged boolean true method call time=1710791842.146277 sender=:1.12 -> destination=org.kde.kglobalaccel serial=366232 path=/kglobalaccel; interface=org.kde.KGlobalAccel; member=allComponents signal time=1710791842.146536 sender=:1.24 -> destination=(null destination) serial=468463 path=/org/freedesktop/PowerManagement/Inhibit; interface=org.freedesktop.PowerManagement.Inhibit; member=HasInhibitChanged boolean true signal time=1710791842.146545 sender=:1.24 -> destination=(null destination) serial=468464 path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement.Inhibit; member=HasInhibitChanged boolean true ... # ??? signal time=1710791870.577083 sender=:1.12 -> destination=(null destination) serial=366245 path=/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=ActiveChanged boolean false signal time=1710791870.577304 sender=:1.12 -> destination=(null destination) serial=366246 path=/org/freedesktop/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=ActiveChanged boolean false signal time=1710791870.578015 sender=:1.24 -> destination=(null destination) serial=468465 path=/org/freedesktop/PowerManagement/Inhibit; interface=org.freedesktop.PowerManagement.Inhibit; member=HasInhibitChanged boolean true signal time=1710791870.578030 sender=:1.24 -> destination=(null destination) serial=468466 path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement.Inhibit; member=HasInhibitChanged boolean true as well as a couple calls to org.freedesktop.DBus that look like uninteresting interface inspection. Still seems like SDL is doing the right thing. Not sure what the last block of stuff is about, a conspicuous 30 seconds after my last input (pressing super+L). And the same steps without running `love` do leave my monitors asleep. -- You are receiving this mail because: You are watching all bug changes.
