Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Very often Flameshot does not see the second display to make the screenshot #3760

Open
bkalika opened this issue Oct 23, 2024 · 5 comments
Open
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@bkalika
Copy link

bkalika commented Oct 23, 2024

Flameshot Version

Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 10.0.19045
windows: 10

Installation Type

Compiled from source

Operating System type and version

Windows

Description

Very often Flameshot does not see the second display to make the screenshot. The app only select main display for making the screenshoot, to overcome this, need to relaunch the app. It's reproduced on my 2 laptops (Windows 10 and Windows 11).

Steps to reproduce

In my case it can be reproduced (maybe other option also reproduced):

  1. Launch the app in Windows startup
  2. You can do your work connecting the second display, you can run the laptop to sleep mode and so on and for example, in the next day, you do not have possibility to make a screenshot in the second display.

Screenshots or screen recordings

No response

System Information

In my case it reproduced in Windows 11 Pro (hope that all Windows updates are installed) and Windows 10.

@bkalika bkalika added the Unconfirmed Bug The bug is not confirmed by anyone else. label Oct 23, 2024
@NAICOLAS
Copy link

NAICOLAS commented Oct 23, 2024

I can't take a screenshot of any of my multiple monitors. Only works on my main screen (laptop screen).
Using Flameshot (v12.1.10) on macOS Sonoma 14.6.1 (23G93).

I'm using a MacBook Pro M1 Max.

@novcop
Copy link

novcop commented Oct 24, 2024

Confirm. And works well for a few shots only if I restart the app.
Another issue is when it tries to get a sceenshot it enlarge the screen and you can't take the area you need. Again if you reboot the app it works well for a while.

UPD.
Flameshot v12.1.0 (96c2c82) Compiled with Qt 5.15.5
darwin: 24.0.0
osx: 15.0

@NBruls
Copy link

NBruls commented Nov 1, 2024

I have the same issue on my Windows laptop. It used to work perfectly, but the last few months it fails to detect my second monitor after initial startup. I have to reboot the app to fix it.

Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 10.0.22631
windows: 10

@theguly
Copy link

theguly commented Nov 6, 2024

confirm on macos and wayland (hyprland). if you change the primary monitor to the external one, only that one can be shotted even if the focus is on the other one.

at least to me, if i got it right, disconnecting the external monitor also helps.

there is one more, when it start "not seeing" the non-primary monitor i also see that the shottable image is smaller than the screen. the external/primary monitor is bigger than the laptop one and looks like the screen is shrinked to a smaller size.

@LaiKash
Copy link

LaiKash commented Dec 3, 2024

confirm on macos and wayland (hyprland). if you change the primary monitor to the external one, only that one can be shotted even if the focus is on the other one.

at least to me, if i got it right, disconnecting the external monitor also helps.

there is one more, when it start "not seeing" the non-primary monitor i also see that the shottable image is smaller than the screen. the external/primary monitor is bigger than the laptop one and looks like the screen is shrinked to a smaller size.

The last part happens to me pretty often. After some time, when I want to take a screenshot, the area (and the whole screen) shrinks into a small square at the top left of the screen. Works after restarting Flameshot, for some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.
Projects
None yet
Development

No branches or pull requests

6 participants