flameshot-org
Only primary monitor is grabbed by the screenshot. (Wayland)
Flameshot Version
Flameshot v13.3.0 (88c951e) Compiled with Qt 6.9.3 linux: 6.17.0-6-generic org.kde.Platform: 6.9
Installation Type
Flatpak from Flathub
Operating System type and version
Ubuntu 25.10
Description
screenshot "flashes" both displays, but only primary monitor is in the screenshot and is editable.
Steps to reproduce
install , run : flatpak run org.flameshot.Flameshot gui
Screenshots or screen recordings
No response
System Information
andre@andre-wks:~$ loginctl show-session $(loginctl show-user $(whoami) -p Display --value) -p Type --value wayland andre@andre-wks:~$ xrandr --listactivemonitors Monitors: 2 0: +*DP-2 2560/600x1440/340+0+0 DP-2 1: +HDMI-1 2560/600x1440/340+2560+0 HDMI-1 andre@andre-wks:~$ dbus-monitor --session sender=org.flameshot.Flameshot signal time=1763543721.920644 sender=org.freedesktop.DBus -> destination=:1.1224 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.1224" signal time=1763543721.920892 sender=org.freedesktop.DBus -> destination=:1.1224 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.1224"
Behavior on Windows 11 with Flameshot v13.3.0: click LMB on a main monitor, press Print Screen, the image from main monitor is shown on the second monitor, and main monitor becomes black (no image there)
Same here on Kubuntu 25.10 Wayland Flameshot captures my secondary monitor and my main, but the entire editable 'overlay' is only present on the main monitor, with the upper left origin of the secondary monitor moved down to the upper left origin of my main. May be the same bug.
ralek@Ralek-Shed:~$ xrandr --listactivemonitors Monitors: 2 0: +*HDMI-A-1 5120/597x2880/336+2160+960 HDMI-A-1 1: +DP-3 2160/609x3840/355+0+0 DP-3
an interesting observation: while fooling around with AppImage I discovered this:
This works fine: './Flameshot-13.3.0.x86_64.AppImage gui'
the command outputs: 'Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.' ...and works fine
This screenshots one monitor: 'QT_QPA_PLATFORM=wayland ./Flameshot-13.3.0.x86_64.AppImage gui '
So the wayland support seems broken.
Also: running the .AppImage from terminal work fine, but from a keyboard shortcut, results in an error:
(unless I run it thru a .sh)
Same. Win10, whole image shift to 1 screen left (have 3 screens, right one black and it's images with main one shifted to left)
Same issue on Win11, https://github.com/flameshot-org/flameshot/issues/4347#issuecomment-3514250860
Also have this issue on Windows 11 with one external monitor. Reverting to version 12.1.0 seems to resolve this particular issue.
Found on what version problem appear: v13.2.0 If you're on Windows/Linux just back to 13.1.0 via replacing files, for me it helps on both OS
Found on what version problem appear: v13.2.0 If you're on Windows/Linux just back to 13.1.0 via replacing files, for me it helps on both OS
I've tried uninstalling and installing v13.1.0 and it didn't solve it. Maybe caching/remaining files?
I've tried uninstalling and installing v13.1.0 and it didn't solve it. Maybe caching/remaining files?
Well, i just opened flameshot folder and replace all files from archive, without deleting cache or smth else, maybe it works on ubuntu/Win10, but not in win11 for example, try diff versions
I experience this issue on EndeavourOS Plasma v6.5.3 in a Wayland session.
Flameshot v13.3.0 Compiled with Qt 6.10.0 Version: 13.3.0-1
Edit: Lenovo X1 Extreme Gen2 with USB-C portable monitor. I can screenshot the laptop screen only.
Hi,
for me it's the same on Windows 11 25H2, reverted to latest v12 where it starts working again.
Hi,
I had the same issue on Windows 11 25H2, reverted to v13.1, it solved the issue. One strange things I noticed when I went to remove 13.2, was that I found two versions of Flameshot installed. I therefore uninstalled both before reinstalling it. Only the monitor set as default monitor can be screenshotted (not my laptop's screen or the other monitor)
Thanks for your great works !!
Same behavior on Ubuntu 24.04.3. Only the laptop screen can be screenshot.
FWIW - my workaround is:
$ cat flameshot_gui.sh
#!/bin/bash
#required to screenshot both monitors.
./Flameshot-13.3.0.x86_64.AppImage gui
then call that shellscript from a keyboard shortcut. Just like from the shell, starting the AppImage from shellscript works, contrary to when started from shortcut.
Samething on Windows: Flameshot v13.3.0 (da913d7f) Compiled with Qt 6.9.2
If I downgrade 12.1.0-win64 worked for me. It started after I upgrade to v13.X
I'm seeing this issue with the deb installed from Debian Trixie. The flameshot gui workaround does not work for me.
I'm having the same problem in my environment consisting of a laptop screen (1920x1200 - Scale: 125% - screen1) and primary monitor (1920x1080 - Scale: 100% - screen2). When I copy the screen, all the content is sent to the screen1, but the scale changes and black bars appear in the screen2. I use the portable instalation flameshot-13.3.0-win64.zip
Flameshot v13.3.0 (da913d7f) Compiled with Qt 6.9.2 winnt: 10.0.26100 windows: 11
I don't have this problem in version 12.1.0.
Both screens flash, but only the first screen has the gui. Windows do not minimize, I just didn't have anything up while taking the screenshot for this.
Gnome 49.2 (wayland) Flameshot v13.3.0 () Compiled with Qt 6.10.1 6.17.9-arch1-1
Asides from the other mentioned behaviors, copy to clipboard also appears to not work.
Flameshot org.flameshot.Flameshot 13.3.0 stable system
Linux 6.14.0-37-generic #37~24.04.1-Ubuntu
GNOME Shell 46.3.1
xwayland 2:23.2.6-1ubuntu0.7
Asides from the other mentioned behaviors, copy to clipboard also appears to not work.
Flameshot org.flameshot.Flameshot 13.3.0 stable system Linux 6.14.0-37-generic #37~24.04.1-Ubuntu GNOME Shell 46.3.1 xwayland 2:23.2.6-1ubuntu0.7
That's a different bug, already reported elsewhere, already fixed in the current development branch.
Thanks for the correction. I am aware it's a different bug, but was convinced it was corrected in main branch, and this was just a resurgence.
@edggoncalves As a stop-gap, if you pin and copy to clipboard twice it seems to work for me. However the pinned image sticks to my mouse if I use right click on it, which is annoying, but not a huge issue.
For the only primary screen can capture, I also experienced it in hyprland, but I was able to use grim there to resolve it.