flameshot icon indicating copy to clipboard operation
flameshot copied to clipboard

Two screens different resolutions [BUG]

Open ahfauth opened this issue 1 year ago • 3 comments

Flameshot Version

Flameshot v11.0.0 (11.0.0-2 Debian) Compiled with Qt 5.15.2 linux: 6.8.0-76060800daily20240311-generic pop-os: 22.04 Plasma KDE Xorg

Installation Type

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

Operating System type and version

pop-os: 22.04 linux: 6.8.0-76060800daily20240311-generic

Description

I have 2 screens. Laptop screen is 3072 x 1920 (16:10) and second external screen 1920 x 1080 (16:9).

When I try to take a screenshot the location on the screen changes completely and I cannot do anything.

Can some replicate that?

Steps to reproduce

No response

Screenshots or screen recordings

No response

System Information

linux: 6.8.0-76060800daily20240311-generic pop-os: 22.04 Plasma KDE Xorg

ahfauth avatar Apr 23 '24 02:04 ahfauth

I second that. I have this setup:

Laptop with internal screen + 2 identical monitors connected via Displaylink. The laptop is the leftmost screen (with 1920x1080 resolution), the 2 external monitors extend to the right (with 2560x1440 resolution).

Whenever I use Flameshot to capture a screen, all windows move about 400-600 pixels to the left. The capture works, but some information moves out of range as it is moved out of the left side of visible area.

One thing to note is: Disabling the laptop monitor (I've set it up so on close of the laptop lid the monitor deactivates) does not fix the problem. If it has something to do with the different resolution of the screens, I'd expect the problem to disappear when the laptop screen is not active/enabled, which does not happen.

System information:

EndeavourOS KDE Plasma Linux thinkpad 6.6.28-1-lts #1 SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 10:11:09 +0000 x86_64 GNU/Linux XDG_SESSION_TYPE=x11

Flameshot version:

Flameshot v12.1.0 (-) Compiled with Qt 5.15.10

TheDromundKaas avatar Apr 23 '24 07:04 TheDromundKaas

known issue for a while... Its been happening on wayland since the update to kde6

wolfsilver00 avatar May 01 '24 14:05 wolfsilver00

A temporary fix for this is to make a kwin rule for Flameshot where you force the window to open in fullscreen and force the initial placement to be "Random" I don't know why it's called that and I don't know what it's supposed to do but the effect it does have is that the Flameshot gui opens correctly (albeit with a small delay)

insunaa avatar May 07 '24 09:05 insunaa