Bug 444756 - Global scaling is not saved along with "save for only this specific display arrangement"
Summary: Global scaling is not saved along with "save for only this specific display a...
Status: RESOLVED DUPLICATE of bug 425225
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.23.2
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-01 07:23 UTC by deresiant
Modified: 2021-11-01 07:24 UTC (History)
0 users

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 deresiant 2021-11-01 07:23:01 UTC
Not sure if intended or not but when having `save display's properties for only this specific display arrangement` checked, it does not link/save the global display scaling setting with the display arrangement.


I was thinking that global display settings could be automatically changed whenever I plug in/unplug a monitor 
1. Have one monitor plugged in with 100% display setting saved with `save for only this specific display arrangement`
2. Plug in second monitor
3. Enable `save for only this specific display arrangement`
4. Change global display % setting to not 100%
5. Unplug monitor
6. What should happen is that it changes back to 100% display scaling because I thought it was saved when using `save display's properties for only this specific display arrangement

Instead, the global display scaling setting does not change when plugging in/unplugging monitors.




SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.15-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
Comment 1 deresiant 2021-11-01 07:24:43 UTC

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