Add talk permissions to non-freedesktop dbus screensaver apis

[quexten]

Had a user reporting locking on system lock not working in the Bitwarden browser extension on the Flatpak version of Brave. Chromium talks to more than just the freedesktop screensaver dbus interface (cf. https://github.com/chromium/chromium/blob/140ebdb86130d4a1bc3c5b08448897ea5c5bda56/ui/base/idle/idle_linux.cc#L44-L55) . Since the google-chrome flatpak manifest has the same permissions in this case, it causes the same issue as for Brave. This PR adds permission for the missing screensaver dbus apis.

[flathubbot]

Started test build 135763

[flathubbot]

Build 135763 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/118795/com.google.Chrome.flatpakref

[latin-1]

Is there any chance to get this PR merged?

[quexten]

@refi64 any chance to get this (and flathub/org.chromium.Chromium#416) merged?

[orowith2os]

Are upstream devs against talking to the portal equivalents instead, and/or the Wayland protocol?

[latin-1]

@orowith2os I didn't find any equivalent in wayland/xdg-desktop-portal.
Chrome wants to query/monitor the screen lock status (e.g. Idle Detection API), while the org.freedesktop.ScreenSaver can only inhibit the screen lock.

[latin-1]

@refi64 Would it be possible to get this merged?

[latin-1]

@refi64 Pinging again. Chrome now uses Ozone Wayland by default, and the missing permission can prevent features such as automatic locking in the 1Password extension from working properly. Would appreciate it if this could be merged.