https://bugs.kde.org/show_bug.cgi?id=428537
Olav Seyfarth <bugs.kde....@seyfarth.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |bugs.kde....@seyfarth.de
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
--- Comment #4 from Olav Seyfarth <bugs.kde....@seyfarth.de> ---
I suffer the same bug on a newly (manually, clean) installed arch system. From
what I see in "journalctl -f" I suspect that at some point ~/.face is read by
the system settings applet - and fails if it doesn't exist.
I assume that all that needs to be changed is to make that file access
conditional (check if it exists prior to accessing it). After I manually
created such file with "touch .face" I could modify user settings and save
without error.
However, there are more bugs to solve here (that devs may want to open separate
tickets for):
(1) I tried to modify a user that I had created as admin, switched into that
user account via SDDM, logged out that user, returned to the initial admin and
tried to modify the user. (Only!) on journalctl I get an error that some
processes still run for that user. Same applies to "usermod -l". So modifying
its login name should be disabled if processes for that user still run. At
least, a proper error messages should be given to the user. I could delete that
user though, and recreate it with the desired settings.
(2) A similar issue applies to modifying the login name of the CURRENT user.
IMHO, this simply should not be allowed, thus that field should not be editable
for the current user.
--
You are receiving this mail because:
You are watching all bug changes.
