Bug 467634 - Spectacle not respecting scaling when saving or copying to clipboard
Summary: Spectacle not respecting scaling when saving or copying to clipboard
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 23.03.80
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
: 467667 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-03-21 04:08 UTC by Nathaniel Mason
Modified: 2023-04-01 12:11 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathaniel Mason 2023-03-21 04:08:24 UTC
STEPS TO REPRODUCE
1. Run spectacle on Wayland with scaling
2. Capture screenshot using "Rectangular Region"
3. Attempt to save image or copy image to clipboard

OBSERVED RESULT
The preview shows the correct image, but upon saving or copying the image, the right and bottom sides of the image get cropped.

EXPECTED RESULT
The image should be exported correctly as shown in the preview

SOFTWARE/OS VERSIONS
Linux: 6.2.6
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I have my monitor at 150% fractional scaling. The top-left corner of the exported image always matches correctly with the desired screenshot. It appears to exclusively crop out the right-most and bottom-most thirds of the image.
Setting my scaling to 100% causes spectacle to work as intended, and at 200% scaling only the upper-left quarter of the intended screenshot is captured, so it seems as if there's an error with calculating the position of the bottom-right vertex of the image when scaling is involved.
Comment 1 Patrick Silva 2023-03-21 22:37:32 UTC
*** Bug 467667 has been marked as a duplicate of this bug. ***
Comment 2 Noah Davis 2023-03-30 01:55:27 UTC
I can't reproduce this and https://bugs.kde.org/show_bug.cgi?id=467398 seems to have some similarities. Can anyone else confirm whether this has been fixed?
Comment 3 Nathaniel Mason 2023-04-01 01:10:29 UTC
Just updated to 23.03.90, and it all seems to be working as expected again. Although I downgraded back to 23.03.80 out of curiosity and it's suddenly working properly again, so that's a bit bizarre. Either way, really nice to have it working again!