Bug 495150 - Preview of rectangular screenshot displays improperly
Summary: Preview of rectangular screenshot displays improperly
Status: RESOLVED DUPLICATE of bug 462860
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 23.08.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-21 16:20 UTC by magnus.amann
Modified: 2024-10-21 19:14 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description magnus.amann 2024-10-21 16:20:29 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
When using the screenshot tool to crop a rectangular area for a screenshot the screen changes what is shown on it and displays it improperly (offset to the side and height), making it difficult to select the correct area for the screenshot.

STEPS TO REPRODUCE
1. Use spectacle (kde-spectacle)
2. Make new screenshot
3. choose screenshot of rectangular area

OBSERVED RESULT
The screen is shown and an area can be selected.
The screenshot will match what was shown in the area.

EXPECTED RESULT
The screen is shown in a distorted way and an area can be selected.
The screenshot matches the normal screen, not the distorted one, thus making the screenshot appear as taken in the wrong place.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
Comment 1 Noah Davis 2024-10-21 19:14:45 UTC
Fixed in 24.02

*** This bug has been marked as a duplicate of bug 462860 ***