Sebastian Wick

Yeah, that explains how it manages to trigger it. The scope says just 'flameshot' but the desktop file is 'org.flameshot.Flameshot.desktop'. If you start flameshot from the shell and not via...

oh boy... more bugs. I'll need a more info: * exactly how the shortcut was created (from settings? with a command? the exact command!) * the contents of every desktop...

what happens when you launch via `gtk-launch org.flameshot.Flameshot.desktop`?

Alright, I have a complete picture now. The command in the shortcut (flameshot) doesn't match the desktop file (org.flameshot.Flameshot.desktop). This means that gsd-media-keys fails to get the correct app id...

I know. Flameshot should name the desktop file matching the executable name, i.e. 'flameshot.desktop' (obviously that doesn't apply to the flatpak version). You can open an issue on their bug...

https://github.com/flatpak/xdg-desktop-portal/pull/1087 I think this is the only actionable thing in xdg-desktop-portal. For everything else you have to talk with flameshot.

@jadahl it is started by a string that's interpreted as a command. Not sure how you want to go from there to the desktop file other than by name. Maybe...

So, we are not going for extended file attributes then? Would be nice to have some rationale for why this path has been chosen. I'm worrying a bit about the...

> Maybe a stupid question as this is something I know nothing about. Wouldn't extended file attributes as proposed in the original bug be GIO specific? No, extended file attributes...

One could write code to read the extended attribute just like they could write code to call the portal. There is no need to wait for GIO or anything else...