https://bugs.kde.org/show_bug.cgi?id=449855
Bug ID: 449855
Summary: Proxy makes Night Color fail to apply on Plasma start
Product: systemsettings
Version: 5.24.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_nightcolor
Assignee: plasma-b...@kde.org
Reporter: openmind...@gmail.com
CC: kwin-bugs-n...@kde.org
Target Milestone: ---
SUMMARY
***
Proxy makes Night Color fail to apply on Plasma start, which in turn makes
setting of primary monitor fail.
***
STEPS TO REPRODUCE
1. Pick a laptop with Wayland session, connect external monitor, set it as the
primary output, go to Night Color settings, activate it setting to be based on
current location or manual location, go to Network Settings and set up proxy (I
use URL auto-config file).
2. Log out, log in: your primary screen got reset to laptop's. Night Color
failed to apply on Plasma start.
3. Switch off proxy, log out, log in: the external monitor is your primary
screen again. Night Color is applied from the beginning of the session.
OBSERVED RESULT
This happens in X11 too, but there Kscreen or what is in charge for screen
manipulation overrides this error and after some blinking sets the primary
screen according to user configuration anyway.
EXPECTED RESULT
If I'm allowed to suggest how it should work, I'd rather would expect Night
Color to be applied some time after Plasma has started, like 1-2 minutes, in
order to connections to be established just in case. Or, if a user selects
manual location in NC settings, it should not need internet access on Plasma
start then.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.12.2
ADDITIONAL INFORMATION
This has been happening ever since Night Color was introduced in KDE. For
years.
--
You are receiving this mail because:
You are watching all bug changes.
