Using bad multi-monitor setups cause bad single-monitor screenshots

[VideoGameSmash12]

Flameshot Version

Flameshot v13.1.0 ()
Compiled with Qt 6.9.1
linux: 6.17.1-zen1-1-zen
arch: unknown

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

Arch Linux

Description

I have quite possibly the most cursed multi-monitor setup known to mankind. Attempting to use Flameshot's selective screen functionality on my setup results in the output screenshots being offset by a considerable amount, making them effectively useless.

Steps to reproduce

1. Have a monitor setup that will get you sent straight to IT hell, like attached below
2. Use a command like flameshot screen -c -n <monitor number>
3. Look at what it produces

Screenshots or screen recordings

System Information

Arch Linux - Kernel 6.17.1-zen1-1-zen
This abomination of a multi-monitor setup
Cinnamon with the Muffin Window Manager, using X11

[JohnDoeDoe]

I have same issues, multi-montior doesn’t work, in fact has never worked, can only take single screenshots, but the real issue that was introduced recently, where even single monitors appear small when taking the screenshot is still present, the patch release didn’t work.

Arch linux X11 using exec /usr/bin/Xorg -keeptty -nolisten tcp "$@" vt$XDG_VTNR
bspwm window manager.
compton compositor.
xrandr output.
HDMI-0 connected (normal left inverted right x axis y axis)
1920x1080 60.00 + 59.94 50.00 29.97 23.98 60.05 60.00 50.04
DP-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
1920x1200 59.95*+

[iotshelnik]

Comment for flameshot Issue #4289

I believe I have the same type of issue, but on Ubuntu 24.04 (GNOME, Wayland).

Environment

• OS: Ubuntu 24.04 (GNOME 46) – Wayland session (echo $XDG_SESSION_TYPE → wayland)
• Flameshot: Flameshot v13.1.0 () — Compiled with Qt 6.4.2
• Packages: xdg-desktop-portal 1.18.4-1ubuntu2.24.04.1, xdg-desktop-portal-gnome 46.2-0ubuntu1, wl-clipboard 2.2.1
• Setup: Laptop + one external monitor; primary monitor screenshots fail

What happens

After upgrading Flameshot, selecting a region on the primary display fails: the selection UI appears, but capture is aborted and nothing is copied to the clipboard.

Terminal output:

QLayout: Attempting to add QLayout "" to SidePanelWidget "", which already has a layout
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::setCompositionMode: Painter not active
QPainter::translate: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
flameshot: info: Screenshot aborted.

Prior errors (now mitigated)

Initially also saw:

inotify_add_watch(...flameshot.ini) failed: (No space left on device)

I increased inotify limits and restarted portals; these inotify errors disappeared, but the primary-monitor capture still aborts with the QPainter errors above.

Inotify changes:

echo 1048576 | sudo tee /proc/sys/fs/inotify/max_user_watches
echo 10240   | sudo tee /proc/sys/fs/inotify/max_user_instances
printf "fs.inotify.max_user_watches=1048576
fs.inotify.max_user_instances=10240
" | sudo tee /etc/sysctl.d/99-inotify.conf
sudo sysctl --system

Tried so far

• Restarted portals:

  systemctl --user restart xdg-desktop-portal xdg-desktop-portal-gnome

• Relaunched ibus:

  killall ibus-daemon 2>/dev/null || true
  /usr/bin/ibus-daemon -drx

• Cleared Flameshot config/cache (fresh start):

  rm -rf ~/.cache/flameshot
  mv ~/.config/flameshot/flameshot.ini ~/.config/flameshot/flameshot.ini.bak 2>/dev/null || true

• Forced Wayland platform:

  QT_QPA_PLATFORM=wayland flameshot gui
  QT_QPA_PLATFORM=wayland-egl flameshot gui

• Verified clipboard works on Wayland:

  echo test | wl-copy
  wl-paste

• Matched display scales and disabled fractional scaling

Repro steps

1. Start flameshot gui on Wayland.
2. Try to capture a region on the primary monitor.
3. Capture is aborted; nothing saved/copied; see QPainter errors above.

Questions

• Does this align with the multi-monitor offset/portal issue discussed in Using bad multi-monitor setups cause bad single-monitor screenshots #4289 from the Qt/portal side?
• Any recommended debug flags (e.g., XDG_DESKTOP_PORTAL_DEBUG=1, QT_LOGGING_RULES="*.debug=true") to gather more info?
• Happy to provide portal logs or test a patched build if that helps.

Thanks!