Bug 430108 - In Display Configuration KCM it is possible to set up no primary screen, but not apply the configuration
Summary: In Display Configuration KCM it is possible to set up no primary screen, but ...
Status: RESOLVED DUPLICATE of bug 458180
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: 5.20.4
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-07 12:55 UTC by Oded Arbel
Modified: 2022-11-08 21:34 UTC (History)
2 users (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 Oded Arbel 2020-12-07 12:55:34 UTC
SUMMARY
In previous versions of Plasma, when the Display Configuration UI had a drop-down to select the primary display, one of the options was "No Primary Display". With the new Display Configuration (at least from 5.18, I believe) the primary display selection is a checkbox on each device, which - when checked in a device configuration - automatically unchecks the "primary" checkbox on all other devices, but the "primary" checkbox cannot be unchecked manually - clicking it again doesn't do anything.

But double clicking the "primary" checkbox can uncheck it, though that does not enable the "Apply" button, so that configuration cannot be applied.

STEPS TO REPRODUCE
1. Have multiple monitors connected.
2. Make sure one of the devices has the "primary" checkbox checked.
3. Double click the "primary" checkbox.

OBSERVED RESULT
The checkbox gets cleared, but this configuration cannot be applied.

EXPECTED RESULT
Probably the checkbox should not be cleared.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
I expect that this is a minor UI issue and the correct behavior is that there always must be a primary screen (unlike as it was in older Plasma versions).
Comment 1 Nate Graham 2022-11-08 21:34:06 UTC
Sorry for the forward-dupe.

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