Pop!_OS (Linux)@lemmy.worldEnglish · 1 year ago

Is it possible to skip the share screen permission check for screenshot apps like Flameshot?

Pop!_OS (Linux)@lemmy.worldEnglish · 1 year ago

Whenever I take a screenshot with Flameshot (an app installed via flatpak) there is a window that pops up asking permission to “share” the screen with Flameshot.

Apparently since August 2022, it is possible in Gnome to check a box once that offers permission forever after, for apps like Flameshot. This way, the screenshot-taking experience is simple and unobstructed.

Has this landed in Pop!_OS yet? Is there a way to enable it?

Chat

canadaduaneOP
link
fedilink
English
arrow-up
1·
1 year ago
Thanks, yeah, I did check Flatseal. It doesn’t show an option to enable without asking each time as far as I can see.

Pop!_OS (Linux)@lemmy.world

pop_os@lemmy.world

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We’re all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the “Support Pop” button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we’ll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like “RTM” or links to LMGTFY. Linking to direct sources that answer the asker’s question is fine, but it’s advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic “It’s bad” or other simple negative comments don’t help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don’t post malicious “advice”

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn’t serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

25 users / day
42 users / week
141 users / month
752 users / 6 months
76 local subscribers
5.19K subscribers
348 Posts
1.51K Comments
Modlog