https://bugs.kde.org/show_bug.cgi?id=497273
--- Comment #4 from Noah Davis <noaha...@gmail.com> --- (In reply to Marco Rebhan from comment #3) > Ahh, I thought the X-KDE-DBUS-Restricted-Interfaces key in Spectacle's > desktop file controlled this access. But no, what I'm thinking of is the > following flow: > > 1. User starts application from the plasmashell launcher > 2. plasmashell (or whatever) sets up new scope for this app, attaches > information about the desktop file that launched it (something like this > already happens, for example for System Monitor) > 3. app ends up spawning a spectacle process or is spectacle itself, this > spectacle process of course ends up in the same app's scope > 4. spectacle tries to take a screenshot > 5. (new!) kwin checks the process's scope instead of the process path and > determines access based on that, shows confirm dialog if the user didn't > confirm access to screenshots for this desktop file yet. the system can ship > pre-existing rules to allow screenshots for spectacle when launched via its > desktop file so it won't ask there > > This is roughly based on how it seems like macOS's permissions checks work. > IMO this is something they got right. > > Implementing it like this is obviously something that would have to be done > on Kwin's side, though. That does sound like it could be better, depending on the implementation. The install location restriction is really annoying for developer setups because it forces you to also build kwin from source and install it with spectacle somewhere. -- You are receiving this mail because: You are watching all bug changes.
