https://bugs.kde.org/show_bug.cgi?id=354802
--- Comment #172 from Uwe Dippel <udip...@gmail.com> --- Thanks, Chango, for #170! Because it confirms my own observation, here and in other bugs, that it is not just a predictable problem of shifting around icons at changes of resolution, as mostly tackled in here. I am 'glad' that it is not only me, who experiences a loss of all settings, default desktop background and 'listing' of all icons at some boots, though infrequently. Despite of a physical setup with any modification w.r.t. cables et al, sometimes at login to KDE it seems that the built-in screen is activated first, before switching to the external monitor; while some times it is the external monitor that is activated immediately. How do I know? In the first case, all icons are positioned in the upper left corner, exactly filling the area implemented by the laptop screen. Meaning, that during startup the resolution of the laptop screen is read and applied briefly. (Then I reset the icon locations) Some times the icons remain at their pre-allocated positions on the monitor with a larger resolution; indicating that the monitor switch as set in the System Settings (internal monitor disabled) happens earlier, before getting the external monitor up. In a nutshell, you seem to confirm my suspicion, that the plasma desktop goes through unpredictable phases and sequences at its start-up. I didn't look at the details, but I can imagine that it has to make with task parallelization, like with systemd. In any case, the plasma desktop is brought up in a non-reproducible, non-controlled, not predefined sequence, so it looks like. Your workaround confirms this: During startup, certain processes read and write configuration files at undefined moments of the sequence. With some bad luck (it happens once per around 50 or 70 start-ups here) it doesn't find what it is looking for, and subsequently starts its layout from scratch. The passage through initial laptop display respectively immediately bringing up the external monitor immediately rather is distributed 1:1 here. (I really wonder if the kde developer use their own product, or have likewise implemented workarounds for their machines?) -- You are receiving this mail because: You are watching all bug changes.
