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

When Flameshot is opened from GUI, screen sometimes shrinks. #2054

Closed
mi1ez opened this issue Nov 8, 2021 · 9 comments
Closed

When Flameshot is opened from GUI, screen sometimes shrinks. #2054

mi1ez opened this issue Nov 8, 2021 · 9 comments
Labels
MacOS MacOS related Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@mi1ez
Copy link

mi1ez commented Nov 8, 2021

Flameshot version
0.10.1 (4e406ec)

Describe the bug
When taking a screenshot using the GUI, the visible screen will sometimes shrink to less than a quarter of the monitor size and be cropped. This seems to happen most frequently after the machine has been put into a sleep state, but not every time. I'm also not sure if having a second monitor connected is an agravating factor.

Before opening Flameshot:
flameshot-not-open

Once Flameshot is opened:
flameshot-open

Closing and reopening Flameshot returns it to expected behaviour.

Not sure if this is the "fractional scaling" issue mentioned in the FAQs as the description isn't very clear. Either way, I have no scaling set, and this is affecting applications that aren't fullscreen as the FAQs imply.

To Reproduce
Unable to reproduce consistently.

Expected behavior
Screen visible area to remain the same whilst taking screenshot.

System Information
MacOS 11.6

@borgmanJeremy
Copy link
Contributor

On macOS there is an issue where if your screen config changes after starting flameshot, you must restart Flameshot.

I should probably add this to the FAQ as it's a pretty common complaint.

@veracioux
Copy link
Contributor

@borgmanJeremy I'm assuming this won't be as much of a problem after the DBus PR?

@borgmanJeremy
Copy link
Contributor

I don't see why the dbus stuff would fix it, but maybe I'm missing something.

I haven't tried to troubleshoot this one yet.

@veracioux
Copy link
Contributor

@borgmanJeremy The way I understand it: Currently there is a time interval between launching the daemon and launching the GUI capture. In that time interval, the screen config can change. If flameshot gui is self-contained (as it will be after #2003), then the screen config will be synced at each run of that subcommand.

@borgmanJeremy
Copy link
Contributor

Is that PR in a place where I could test it on a Mac?

@mi1ez
Copy link
Author

mi1ez commented Nov 9, 2021

On macOS there is an issue where if your screen config changes after starting flameshot, you must restart Flameshot.

I should probably add this to the FAQ as it's a pretty common complaint.

Nothing about the way MacOS deals with a second monitor surprises me any more. All round terrible experience.

Every time my Macbook goes to sleep or turns the screen off it seems to forget the second monitor exists, so that would line up with what you're saying, although it doesn't seem to happen every time.

@mmahmoudian
Copy link
Member

Isn't it weird that the message and the sidebar button are neither vertically nor horizontally aligned to the monitor or the scaled picture, but the shade has filled the monitor fully.
Feels like there are three different dimensions in play:

  1. The actual monitor size (shade respects it properly)
  2. The smallest one which the screenshot is shrunk to
  3. The one in between where the message and the sidebar button are using to align themselves

@mmahmoudian mmahmoudian added MacOS MacOS related Unconfirmed Bug The bug is not confirmed by anyone else. labels Nov 18, 2021
@thapaliya19
Copy link

thapaliya19 commented May 27, 2024

I encountered a similar bug in my Archlinux installation with kernel version 6.9.1-arch1-2 with a KDE desktop environment. My current flameshot version is v12.1.0. Are there any solutions to this issue?

Update: This issue is with a fractional display scaling factor. Initially, my display was scaled 1.1x when I encountered this problem. I reverted to 1x scaling, and flameshot is working fine.

@Dasonic
Copy link

Dasonic commented Jun 30, 2024

Same issue, when scaling is set to 125% then this bug happens. Setting scaling to 100% fixes it, but this is far too tiny.

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

No branches or pull requests

6 participants