https://bugs.kde.org/show_bug.cgi?id=361437
--- Comment #5 from James <ja...@nurealm.net> --- Now plasma-workspace 5.6.3-1 Still strange. The environment does not change, before and after running startplasmacompositor. systemd does not clear the files in /tmp/, just logging out and in again, so /tmp/ files do not seem a likely cause. I fixed my problem with plasmshell not starting automatically. That was caused by a fragile and obfuscated startkde, not setting XDG environment variables, when XDG_CONFIG_DIRS has already been set in .bash_profile to some incompatible value. startkde has: # TODO: Use GenericConfigLocation once we depend on Qt 5.4 scriptpath=`qtpaths-qt5 --paths ConfigLocation | tr ':' '\n' | sed 's,$,/plasma-workspace,g'` which can, apparently, fail when XDG_CONFIG_DIRS has already been set. But that is a separate issue. Any thoughts about how to make plasmashell produce some actually usable debugging output, describing why it has "hung", and not started the other kde background processes? -- You are receiving this mail because: You are watching all bug changes.
