Bug 449855 - Proxy makes Night Color fail to apply on Plasma start
Summary: Proxy makes Night Color fail to apply on Plasma start
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.24.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-09 13:44 UTC by Vladimir Yerilov
Modified: 2022-04-02 08:59 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Yerilov 2022-02-09 13:44:20 UTC
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.
Comment 1 Martin Riethmayer 2022-02-09 13:55:33 UTC
I can reproduce this on KDE neon, 5.24.0, KDE FW 5.90, QT 5.15.3, Wayland.

I've used an empty URL auto-config (so that obviously fails) as proxy.
Comment 2 Vladimir Yerilov 2022-02-09 14:00:03 UTC
Okay, maybe not exactly *this* is happening on X11, but a similar thing. NC regularly fails to get applied on Plasma X11 startup even without proxy. On Wayland, with proxy it fails as I described initially.
Comment 3 Vladimir Yerilov 2022-02-10 07:42:03 UTC
Today it started happening with X11 as well after I had edited some kwin-related settings (effects, titlebar / window actions). And this happens even when Night Color is set to "Custom time". Seems like it always tries to connect to Mozilla or whatever location services on Plasma startup.
When I disable proxy and login again, my external monitor is set to primary screen as I configured it.