https://bugs.kde.org/show_bug.cgi?id=452251
Bug ID: 452251
Summary: Incorrectly handling default panels in multi-monitor
setups with PRIME
Product: systemsettings
Version: 5.24.4
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: jeanniesteven...@protonmail.com
Target Milestone: ---
When there is an external display connected over PRIME to a laptop that
external display does not load anything until after SDDM launches KDE. This, in
it of itself, isn't a problem but this is likely the cause of the problem I'm
about to describe.
You see when logging into KDE the panel configured for the default monitor is
loaded on the laptop's internal display, underneath/behind the laptop internal
display's panel. This is likely because the external monitors are not
active/detected until logging in.
KDE is probably
1. detecting that there are no external monitors at first
2. loading the default monitor's panel
3. then detecting the external display(s)
4. loading the panels for the internal display and other external displays
Leaving the internal display's panel on top of the default monitor's panel and
leaving the default monitor with no panel at all.
I see two potential solutions. Either KDE adds some logic to load in panel's
later after the external displays are detected or "refresh" the display setup
similar to what happens every time a setting in Display Configuration is
changed.
Alternatively, SDDM could be changed to detect and activate external monitors
connected over PRIME and pass that information along to KDE.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
--
You are receiving this mail because:
You are watching all bug changes.
