https://bugs.kde.org/show_bug.cgi?id=346961
--- Comment #58 from Adam <sidepip...@gmail.com> --- Ok, not sure if this offers any clues, or if it's something unrelated. Logged in this morning and the screen layout had been reset. After trying a few times ( normally logging out/back in fixes it now the kscreen file is ro ) it still wasn't working, so I looked in .local/share/kscreen/ and found that it had got around the ro file thing by creating a new file dated yesterday - I deleted that and things were back to normal when I logged back in. That leads me to a train of thought. Maybe, sometimes during the boot process, kscreen fails to read the kscreen directory. This has more weight because my entire /home is a luks partition mounted with pam_mount - so could it be that there's a timing issue here? pam_mount hasn't completed before kscreen tries to initialise? Is there an easy way I can test this theory ( put a delay in somewhere, force kscreen to rely on pam_mount completing, or some such? ) -- You are receiving this mail because: You are watching all bug changes.
