You are not logged in.
Flameshot gets to the system tray as expecten when opened normally, but when I click on icon a notification pops up and says "Unable to capture screen". When I use the screenshot shortcut I added through Plasma, another notification that says "Screenshot aborted." in addition to the previous one pops up.
I rebooted the my PC many times and reinstalled the Flameshot, but didn't fix it.
Versions:
flameshot: 12.1.0-6
plasma-desktop: 6.4.0-1
Last edited by brogolem35 (Today 09:37:48)
Offline
I found the problem but not the solution. When I tried to run `flameshot gui` on Alacritty (my terminal), a pop up asked "Allow Alacritty to Take Screenshots? Alacritty wants to be able to take screenshots any time.". After clicking OK flameshot worked but only when called through Alacritty. I tried other terminals such as Kitty, Foot, and Ghostty. The pop up showed up only the first time I try to run `flameshot gui` on them. On the ones that I clicked Cancel, Flameshot didn't work and the same notifcations I mentioned poped up. It seems that I accidentally denied the said permission to Flameshot and I couldn't find where to revert it. I will ask this on KDE subreddit.
Edit: Both Spectacle and COSMIC Screenshot did not asked for this permission at all, yet they work. Not sure if they are using a different API to handle this.
Last edited by brogolem35 (Today 05:43:55)
Offline
$ rm ~/.local/share/flatpak/db/screenshot
$ systemctl restart --user xdg-permission-storeDon't know about COSMIC, Spectacle hooks directly into KWin for screenshotting.
Last edited by arojas (Today 09:30:34)
Offline
$ rm ~/.local/share/flatpak/db/screenshot $ systemctl restart --user xdg-permission-store
Thanks a lot! It did work.
But why does KDE use the Flatpak for the screenshot permission? Or is Flameshot uses some Flatpak API (idk how Flatpak works btw) even though it is installed as a system package and Plasma treats it as a Flatpak because of it?
Offline
From https://wiki.archlinux.org/title/XDG_Desktop_Portal:
Portals were designed for use with applications sandboxed through Flatpak, but any application can use portals to provide uniform access to features independent of desktops and toolkits. This is commonly used, for example, to allow screen sharing on Wayland via PipeWire, or to use file open and save dialogs on Firefox that use the same toolkit as your current desktop environment.
So the settings are stored in ~/.local/share/flatpak purely for historical reasons.
Offline
From https://wiki.archlinux.org/title/XDG_Desktop_Portal:
Portals were designed for use with applications sandboxed through Flatpak, but any application can use portals to provide uniform access to features independent of desktops and toolkits. This is commonly used, for example, to allow screen sharing on Wayland via PipeWire, or to use file open and save dialogs on Firefox that use the same toolkit as your current desktop environment.
So the settings are stored in ~/.local/share/flatpak purely for historical reasons.
So, because it uses Portals, which in a way are Flatpak API (because they are designed to be used with it), and is treated like a Flatpak app because of it. Am I correct?
Also, did Plasma changed its screenshot portal in 6.4? It never asked me before while I was using Flameshot.
Offline
So, because it uses Portals, which in a way are Flatpak API (because they are designed to be used with it), and is treated like a Flatpak app because of it. Am I correct?
It is not "treated like a Flatpak app". It is using portals, which is a technology originally developed for Flatpak but is widely used nowadays outside Flatpak too.
Also, did Plasma changed its screenshot portal in 6.4? It never asked me before while I was using Flameshot.
It didn't change anything. You just missed the front page news so you are now inadvertently using Wayland (which you should unless there are any actual issues preventing you to) and not X11.
Offline
It didn't change anything. You just missed the front page news so you are now inadvertently using Wayland (which you should unless there are any actual issues preventing you to) and not X11.
I have been knowingly using Wayland since Plasma 6 came out and been running Wayland exclusive apps like Waydroid as well.
Offline