https://bugs.kde.org/show_bug.cgi?id=403255
Kai Uwe Broulik changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=403255
--- Comment #5 from Leonard Lausen ---
Thanks Kai. Sorry if I misunderstood your previous comment as requiring
the env variable.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403255
--- Comment #4 from Kai Uwe Broulik ---
I see. I agree at least the lock screen definitely shouldn't lock the user out
because of this, which is what my patch is for.
Other than that I think it needs to be decided on a case-by-case basis how to
address
https://bugs.kde.org/show_bug.cgi?id=403255
--- Comment #3 from Leonard Lausen ---
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
https://bugs.kde.org/show_bug.cgi?id=403255
--- Comment #2 from Kai Uwe Broulik ---
Also, you may want to set KDE_HOME_READONLY in your environment if you use a
read-only home, as I don't think this is a supported usecase.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=403255
Kai Uwe Broulik changed:
What|Removed |Added
CC||k...@privat.broulik.de
Ever confirmed|0
