https://bugs.kde.org/show_bug.cgi?id=346961
--- Comment #26 from David Lukeš <dafydd.lu...@gmail.com> --- OK, a status update: in my case, purging `~/.config` (and `~/.kde` for good measure, but I think the catch was in the former) resolved the issue. It's been several reboots since and I'm getting hopeful. I had briefly used both KDE4 and Gnome on this box before settling on KDE5, which suggests that the problem (or at least my version of it) is either related to switching from KDE4 or just hotswapping DEs in general. The easiest way to verify whether that's your case too is to create a fresh user, reboot and log in with this new user. I've only copied over specific application-related files from the old config folders and put the new ones under version control, so should the issue once again rear its ugly head, I'll investigate and report back :) Conspicuously missing from the new `.config` directory is `monitors.xml` which I know is used by Unity and probably Gnome too to determine monitor setup. But if KDE just ignores it, I'm not quite sure how it could mess up its startup. -- You are receiving this mail because: You are watching all bug changes.
