https://bugs.kde.org/show_bug.cgi?id=505151
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |RESOLVED Resolution|--- |NOT A BUG See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=423187 --- Comment #9 from TraceyC <[email protected]> --- > It's been a while, but it happened again. The system clock in the lower > right corner stopped at 15:42:53. > Could this line be important? I don't know. > > "xdg-desktop-portal-kde[2499]: kf.config.core: Created a KConfigGroup on an > inaccessible config location ..." The system clock is a valuable clue. The time shown when the clock was frozen, 15:42:53, corresponds to the entries in the log: Aug 04 15:42:33 myhostname xdg-desktop-portal-kde[2499]: kf.config.core: Created a KConfigGroup on an inaccessible config location "/home/ABC/Lif/.directory" "Desktop Entry" Aug 04 15:42:33 myhostname xdg-desktop-portal-kde[2499]: kf.config.core: Created a KConfigGroup on an inaccessible config location "/home/ABC/Temp/.directory" "Desktop Entry" That indicates the NFS share was not available at the time KDE was trying to write to it. This would also mean that plasmashell wasn't able to read user preferences and cache values from their home directory. Unfortunately, if Plasma can't read or write from the user's home directory when it's temporarily inaccessible, that will cause issues like this. The main problem is the user's files being unavailable. This isn't something KDE can fix, you'll need to investigate whatever is causing the /home directory to be randomly inaccessible. -- You are receiving this mail because: You are watching all bug changes.
