-
-
Notifications
You must be signed in to change notification settings - Fork 198
Wrong area is captured on a Wayland screen scaling #691
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
Will have a look into this. |
@trustin one question though, do you have single or dual monitor (or more) setup? |
I encountered the same issue. |
Thanks for the feedback, I'll have a look. |
I have a single monitor setup. Thanks a lot for looking into! |
Can someone double check if the issue still happens with the continuous build? I have just pushed a fix, it might need ~20min to get published. Thought it targets another issue but might affect this one too. |
I just tried the latest(1d98db4) continuous build. The issue is not fixed. I also tried other capture methods. "Full Screen" and "Active Window" functions are correct. "Current Screen" is wrong. |
Thanks for checking, I'll look into it further. |
Can you please check with latest build if the issue persists? |
Assuming this one is fixed, closing the issue. If the problem persists please reopen. |
Hi, I have the same issue |
@xriser Is the rect selection area incorrectly positioned? |
yes, it is incorrectly positioned(like shifted left and top) and the resulting image is zoomed and cropped |
Describe the bug
When I choose a rectangular area on my screen, a wrong area of the screen is captured. The captured area has incorrect X and Y coordinate and incorrect scale. It has correct width and height.
To Reproduce
Steps to reproduce the behavior:
ksnip --rectarea
Expected behavior
The capture area has to match the rectangular area a user selected.
Screenshots
Will post once requested.
Desktop (please complete the following information):
pacman
~/.config/monitors.xml
:Additional context
None
The text was updated successfully, but these errors were encountered: