Ubuntu 24.10, Wayland: "Unable to capture screen" #3769
Labels
Comments
AndKe
changed the title
|
Try to build with the |
|
Thanks, ... so this flag is not used in the build from Ubuntu's repositories? (I think that is strange) |
|
It's definitely not optimal yeah, wayland has been such a big shift especially for applications that access screen(s) so adoption has been a bit slow. |
|
Try to follow the step-by-step instructions I included in this issue. |
|
Hello, to solve this I create a startup script that will start Flameshot on startup correctly configured. The problem is due to the missing |
Weel, it's very useful, when i change the keyshot for f1 to |
|
i'm also facing this issue with x-org session its working fine but with wayland it has the issue |
|
I'm also facing this issue with GNOME + Wayland + Arch. I tried the following:
I have also tried launching with It's a weird behavior. I suspect it's due to different environment variables.
|
Thanks for the advanced info, the DBUS info would be most telling though. I'm fairly confident that it's the DBUS event either not firing or not getting acted upon. The P.S. I think flameshot gives a warning about this and recommends recompiling with |
|
@FelixJochems Thanks for the instructions. Here are the full using shortcut
|
Don't use the "take screen" icon, just use the keyshot for one key which can be bind to execute |
You inspired me! I've tried different commands in shortcut:
I'm confused. How come redirecting |
|
@liblaf This is so cool, you have made so many attempts, and I don't know more for the specific one. I hope the author will pay attention to the progress we have found, good luck. |
|
I think the warning are still only in the git versions. It's been awhile since an official release. I've experimented with a couple setups on my own system and it got quite confused about the clipboard. Since X11 has a global clipboard while wayland doesn't. The 'unload from memory feature when no longer in use' gets triggered often when it shouldn't. Not technically crashing, but unwanted behavior nonetheless. It's an intricate mess between different OS settings as well. As for the standard in/out helping, I actually don't really know. I'll keep an eye out for it though. P.S. The error should display in the terminal when running flameshot from the terminal. For example I get this: |
|
I'm here to report this bug is present on Ubuntu 24.04.1 when installed from apt. @wanstarge 's fix resolved the issue. |
|
Same problem on Fedora 40 with Gnome Wayland. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Flameshot Version
Flameshot v12.1.0 (Debian 12.1.0-3)
Compiled with Qt 5.15.13
linux: 6.11.0-9-generic
ubuntu: 24.10
Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
Operating System type and version
Ubuntu 24.10 (already in the info above)
Description
This notification pops up instead:
Steps to reproduce
1 start flameshot
2 click "take screenshot"
Screenshots or screen recordings
No response
System Information
The text was updated successfully, but these errors were encountered: