search

flameshot-org / flameshot

Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:
https://flameshot.org
GNU General Public License v3.0
24.67k stars 1.58k forks source link

Not showing flameshot UI directly after running `flameshot gui` #3736

Open aarpabe opened 1 week ago

aarpabe commented 1 week ago

Flameshot Version

Flameshot v12.1.0 () Compiled with Qt 5.11.3

linux: 6.8.0-40-generic ubuntu: 22.04

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...), Using the ready-made package from Github Releases

Operating System type and version

Ubuntu 22.04.4 LTS, 64-bit, GNOME 42.9, Wayland

Description

For a while (some months I think), opening flameshot does not directly show the flameshot UI (with the purple border), but instead shows a Ubuntu-like screenshot window as shows here: image

When I then click Share, the flameshot UI appears and all is fine, but this extra step is super annoying. Also, the screenshots are always saved even though I usually just want to have it copied to my clipboard and reuse it somewhere.

Maybe this is just a misconfiguration somewhere, but I could not find anything helpful by now browsing through this repo or googling.

Steps to reproduce

No response

Screenshots or screen recordings

No response

System Information

Ubuntu 22.04.4 LTS, 64-bit, GNOME 42.9, Wayland

GeekCharmiing commented 6 days ago

I've found that disabling Wayland and rebooting gets it working properly. This issue was forced upon Flameshot by the developers of Gnome from my understanding.

To disable Wayland:

uncomment waylandenable=false @ /etc/gdm3/custom.conf and reboot your machine

aarpabe commented 5 days ago

Ah, nice. This actually works for me. And I have no experienced any unwanted side effects yet. Thanks for that!

Keeping this issue open, because this seems more like a workaround to me. If the maintainers think, it makes sense to close it, feel free.

GeekCharmiing commented 5 days ago

You're welcome! It's indeed a workaround. It effectively tells the OS to load X11 instead of Wayland, which is where the problem seems to lie when using Gnome. Has to do with permissions or something like that. I'm doubtful that the developers of Gnome will fix the issue, but one can hope.