Flameshot does not work well with several monitors

[muellert]

Flameshot Version

Flameshot HEAD at 0x7aa69e4e253b0a69b67c018b701db5ee8448142c - identifies as 12.1.0

Installation Type

Compiled from source

Operating System type and version

Debian 12.9 amd64

Description

I have a problem with flameshot in my multi-monitor setup. It used to
work on a different machine, but since installing this new machine, it
doesn't. Please see the attached screenshot. There, you can see that
flameshot somehow does not recognize the borders of the monitors, and
treats them as one big monitor. But the result of that is that the area
which I want to capture, is usually on the boundary, and very difficult
to grasp. The same goes for the controls.

I have tried with the latest from flameshot-org/flameshot from Github as
well, but got only the same result.

One difference between this machine and the other that I can think of,
besides having different chips (intel vs. amd), is, that the other
computer ran with a built-in screen of 1920x1080 plus an external
monitor of 3840x2160, wheras this computer where things don't work, runs
with a built-in screen of 2560x1600 plus the same external monitor at
the same resolution. I have attached the Xorg.0.log for you.

I have also tried to switch the internal monitor to 1920x1080, but that
did not improve the situation at all.

Steps to reproduce

1. Running flameshot gui on the command line produces this:

$ flameshot gui                                
QVariant::load: unknown user type with name QList<CaptureTool::Type>.
QLayout: Attempting to add QLayout "" to SidePanelWidget "", which already has a layout
flameshot: info: Screenshot aborted.

2. Taking an actual screenshot of the primary monitor exhibits the problem. Please see the attached file.

Screenshots or screen recordings

No response

System Information

Monitor configuration - I have omitted the plethora of unused resolutions:

$ xrandr
Screen 0: minimum 320 x 200, current 6400 x 2160, maximum 16384 x 16384
eDP connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 329mm x 206mm
   2560x1600    120.00*+  60.00  
   1920x1200    120.00  
   1920x1080    120.00
   ...
HDMI-A-0 connected 3840x2160+2560+0 (normal left inverted right x axis y axis) 600mm x 340mm
   3840x2160     60.00*+  50.00    59.94    30.00    30.00    25.00    24.00    29.97    23.98  
   2560x1440     59.95  
   1920x1200     60.00
    ...

I am using awesome 4.3-7, as installed via apt, but not (eg.) Gnome or KDE.

I have attached the Xorg.0.log file from my computer.

Xorg.0.log

[FelixJochems]

Do you, by any chance, have a fractional scale set with the new display?

[muellert]

I'm not sure what that is, but operate both dispays at their native resolutions. I didn't adjust anything, as far as I'm aware. Everything is basically running as it has been auto-detected. I just noticed that I forgot to mention that the screen of the other laptop was actually a 4k screen, I was just operating it at only 1920x1080 because otherwise, most things were way too small for me to read.

[jekyllgrim]

I have an issue with a multi-monitor setup, although the issue itself is different. I have two monitors connected with DisplayPort and one with DVI, and the DVI one doesn't get detected by flameshot at all, it's not possible to screenshot it. This is on Windows 10.

[muellert]

For me, both monitors get "detected", but, as you can see in the image above, flameshot somehow skews the display to mangle everything, so it is impossible to take a meaningful screenshot in almost all cases, much less an easy way. For what it's worth, the fine line in the middle is the border of the screen. What you see on the top near the middle on the left, is my systray, which is on the right end of my screens, although not the same on both screens, and what you see on the right hand side, is the label switcher, which is originally on the left hand side of the screen. Please see the following screenshot, which I've taken with "shutter", which shows both screens side-by-side.

[jekyllgrim]

Actually, yeah, it's not really comparable to my case, sorry; I'll move my report to a separate issue.