Bug 494747 - After reverting scaling change on secondary screen, the screen indicated in visualizer and combobox doesn't match the settings below it
Summary: After reverting scaling change on secondary screen, the screen indicated in v...
Status: RESOLVED DUPLICATE of bug 490586
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: 6.2.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2024-10-14 16:02 UTC by hadrian.decurtins
Modified: 2025-03-17 19:48 UTC (History)
4 users (show)

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

Attachments
This is how it looks after reverting. The colors showing the inconsistencies (77.57 KB, image/png)
2024-10-14 16:02 UTC, hadrian.decurtins 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description hadrian.decurtins 2024-10-14 16:02:57 UTC 
Created attachment 174810 [details]
This is how it looks after reverting. The colors showing the inconsistencies

SUMMARY
After I changed the scaling on the secondary monitor and reverted the change, it somehow selects the primary monitor but the graphic still shows the secondary one being selected

STEPS TO REPRODUCE
1. Have a two monitor setup
2. Go to the display configuration
3. select the secondary monitor
4. change the scaling and hit apply (the one still in the same window as the settings)
5. revert (or let the timer run out and revert automatically)

OBSERVED RESULT
The Graphics shows the secondary monitor being selected but the changes I make affect the primary monitor

EXPECTED RESULT
Either correct the graphics so that the primary monitor is shown to be selected, or don't select the primary monitor after reverting in the first place.

SOFTWARE/OS VERSIONS
Linux: Arch Linux (6.11.3-arch1-1 (64-bit))
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Comment 1 Nate Graham 2025-03-17 19:37:06 UTC 
I can confirm this issue.
Comment 2 Nate Graham 2025-03-17 19:48:38 UTC 
*** This bug has been marked as a duplicate of bug 490586 ***