https://bugs.kde.org/show_bug.cgi?id=466193
--- Comment #24 from homem.gust...@gmail.com --- Some additional info: * initially this problem was not happening to me * but I fine-tuned the environment according to my preferences with the (nothing strange: favourites, background, widgets, etc) * at some point this problem started to happen - I don't know at which point because I noticed it after rebooting the system upon tweaking * the logs complained about kactivitymanagerd not being up so I scripted a loop that waist for kactivitymanagerd to be up * but this is not enough because the process being up does not guarantee that plasmashell will startup correctly (the same problem was happening even after waiting for kactivitymanagerd to be up with the initial message about kactivitymanagerd not being up not being shown any more but still the desktop failing to load) * I inserted an additional wait of 5s once kactivitymanagerd is detected as being up * result: it seems to work (preliminary conclusion after a couple of reboots) To sum up the most probable situation: 1. plasmashell only works after kactivitymanagerd is in a certain sane state 2. but plasmashell is launched in parallel without waiting for kactivitymanagerd to be in such state 3. this is a classic race condition: whether it happens or not depends on how many configuration files have been changed from the default, how many cores the system has, how fast each core is, the type of hdd, etc, etc... 4. ... which leads to "works on my computer" / "fails on my computer" type of situation I think that the dependency between this components needs to be explicitly checked during the startup of the Plasma environment. Environment: Dell XPS Developer Edition Core i7 1.8GHZ (4C/8T) with 16G RAM and SSD. -- You are receiving this mail because: You are watching all bug changes.
