https://bugs.kde.org/show_bug.cgi?id=454345
--- Comment #38 from Ric Grant <rich...@qweb.co.uk> --- (In reply to Uwe Dippel from comment #36) > "why is it so hard to remove any logik that touches that desktop-appletrc > file during plasmashell startup? " > I think I can. It's the old topic of systemd. It's water under the bridge. > Some 15 years ago, people wanted to enhance the user experience by > shortening the startup sequence, and therefore started things in parallel. I > never followed the gory details, since I am the old-fashioned style person, > and would have preferred the slow, and clean, start. AFAIK, systemd took > over many items, including login, and spawning independent items in > parallel. I THINK, with a totally clean sequential startup, no other process > would interfere - or could interfere - in desktop applet layout. > This is why I thought, the semaphore-like wrap around the startup, as > proposed recently, could solve the case by isolating the desktop rendering, > protecting the layout. > > [If you look around, you'll find some other startup-bugs, including some > affecting me, that could be attributed to parallelisms introduced by > systemd; leading to RANDOM - that is not always or even rarely occurring - > faulty behaviour. Systemd introduced a clever though not fully deterministic > startup behaviour. I am willing to bet that after taking out systemd and > revert to the old style rc-startup system - which is not possible, so that > this is hypothetical - all these problems would be gone. With a slow, though > fully sequential strictly one-task-at-a-time start sequence, race conditions > are clearly avoided whatever the lengths of the steps. Boringly long, I > agree.] I'm 'afraid' I can confirm it's not systemd related, no. Gentoo user here, and although I've used systemd in the past, this particular laptop hasn't ever seen it. Gentoo has profiles which basically define the base set-up, ( https://wiki.gentoo.org/wiki/Profile_(Portage) ), and this laptop has always been on the OpenRC based "desktop/plasma (stable)" profile, rather than the systemd based "desktop/plasma/systemd (stable)" profile (or any of the other many options), so there's literally never been anything systemd related to get in the way. OpenRC does also support launching startup daemons in parallel via an rc_parallel option in /etc/rc.conf but for me, this too has always been disabled so we can assume this isn't causing problems either. Besides, Plasma starts after X which I believe waits for its own dependencies to fire up anyway, even with a parallel boot, so by the time Plasma kicks in there should be very few daemons still initiating. Things like WiFi connections which need to wait for remote services might not be quite there yet, but probably nothing related to graphics at all. -- You are receiving this mail because: You are watching all bug changes.
