Add talk permissions to non-freedesktop dbus screensaver apis #416
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Started test build 135767 |
1 task
|
Build 135767 successful |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 chromium (and google-chrome) flatpak manifest has the same permissions regarding screensaver/lock dbus access, it causes the same issue as for Brave. This PR adds permission for the missing screensaver dbus apis.