Sander Sweers

But luckily it does use the same arguments and function names. Looked at Gnome in a VM and it also implements `org.freedesktop.ScreenSaver`. Any other relevant desktops I need to check?

If they expose `org.freedesktop.ScreenSaver` I don't have to specifically handle them. xdg-screensaver doesn't work for me on plasma and I doubt it still work on gnome. I'll have a look...

> > If they expose org.freedesktop.ScreenSaver I don't have to specifically handle them. > > They don't. The names I mentioned are both the bus and interface names. Object paths...

I'm really tempted to just open a PR that removes it. If someone want to resurrect it with a method that works on various desktops they can open a PR.

I got a clue `$ gdbus call --session -d org.freedesktop.ScreenSaver -o /org/freedesktop/ScreenSaver --method org.freedesktop.ScreenSaver.Inhibit "test" "test"` also doesn't work while in blueman it does. It looks like the calling process...

It doesn't support xfc4's screensaver, wip https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/38 Ah, and I was right about the process needing to be running, here is why it doesn't work on plasma https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/114 (only 5...

> A screensaver / locker should not jump in during gaming sessions anyway, at least due to regular input, no? Controller and joysticks are not considered regular input and won't...

ugh, why is it making it a dbus method call 😞 . If you want to just get it working quickly remove this line @bulgariamitko https://github.com/blueman-project/blueman/blob/2-3-stable/blueman/gui/manager/ManagerDeviceList.py#L138 @cschramm you want to...

Wait, does blueman work even with these errors @bulgariamitko ?

How about a spinner like this. [spinner.webm](https://user-images.githubusercontent.com/3465730/232230559-63f3e3f2-f52a-4eca-8d74-dbbb24cab0b2.webm)