-
-
Notifications
You must be signed in to change notification settings - Fork 198
Problems capturing screenshots with 4k display zoomed to 150% #535
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
Comments
Thanks for logging thin, I'll have a look into it. Do you use Wayland or X11? |
Hi! X11 ✦ ❯ loginctl 1 sessions listed. ✦ ❯ loginctl show-session 2 -p Type ✦ ❯ lsb_release -a Thanks, |
Hi! I found that with the combination of values for the variables below the application works! ✦ ❯ printenv | grep QT However, the aspect seems a little big in relation to the fonts and other windows as you can see below! |
Just tested with a fresh install of Ubuntu 20.10 and see there the same behavior, icons with fixed size are not correctly scaled but screenshots seem to be captured correctly as far as I can tell. |
I have address the incorrectly scaled UI elements here #549, those should be fixed now in latest version, thought the CI might need some time to build it. Regarding the screenshot issue you're facing, I might need more input from you on how to reproduce it. Best would be if you could try to reproduce it on a fresh installed VM @mrmodolo . |
Hi!
Unlike #276 in this case, I only have one monitor!
On Ubuntu 20.10 with a 4K monitor and scale factor of 150 the first time the application is run, the screen goes black, flashes several times and the cursor freezes. After pressing ESC and trying again, the screen shrinks to a fraction of the monitor.
I tried with different settings:
bin/ksnip-1.8.0-x86_64.AppImage
QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS="" bin/ksnip-1.8.0-x86_64.AppImage
QT_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS="" bin/ksnip-1.8.0-x86_64.AppImage
In all attempts, the behavior was the same!
Thanks,
Marcelo Módolo
The text was updated successfully, but these errors were encountered: