https://bugs.kde.org/show_bug.cgi?id=403255
--- Comment #3 from Leonard Lausen <leon...@lausen.nl> --- Thanks Kai. I would argue that KDE_HOME_READONLY should not be required to avoid this freeze. Requiring KDE_HOME_READONLY means that a user must consciously want to run on a read-only system, which I guess is not very useful / common. But read-only remount due to kernel bug or cosmic ray is somewhat common, so KDE should still support users investigate and fix the root-cause if that happens. If KDE locks up the X Session, this makes debugging harder and may encourage users to force reboot their system, which in turn would make documenting and recovering from the kernel issue / bit-flip data corruption issue harder. -- You are receiving this mail because: You are watching all bug changes.
