Hi, While this actually solves one problem, there is another problem with xdg-desktop-portal-gtk which ignores the cookie in the Inhibit return message if its value is 0. This is not correct according to freedesktop specs[1].
The result is that, if using xdg-desktop-portal-gtk, the screen saver is disabled, but never enabled again. I opened a bug upstream on xdg-desktop-portal-gtk[2]. A workaround could be made in xssproxy to avoid the value 0 for the cookie, so it could be a reason to delay the upload. For the curious: Firefox is still using the /ScreenSaver path, so the problem is present when xdg-desktop-portal is installed, or when using Chrome for example. There is a good explanation of the situation in xscreensaver code[3]. How comes screen saver inhibition is so complicated? Kind regards, Nicolas. [1]: https://specifications.freedesktop.org/idle-inhibit-spec/latest/ [2]: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/528 [3]: https://sources.debian.org/src/xscreensaver/6.09+dfsg1-1/driver/xscreensaver-systemd.c
