https://bugs.kde.org/show_bug.cgi?id=463352
Bug ID: 463352
Summary: ksmserver: No write access to $HOME directory
(/home/userName)
Classification: Plasma
Product: ksmserver
Version: 5.26.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: devnu...@magenta.de
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
After login, a warning/msg box is shown: Something like "No write access to
$HOME directory (/home/userName) Plasma can't be started"
STEPS TO REPRODUCE
1. chmod 500 ~/
2. Log out and log in.
3.
OBSERVED RESULT
The said msg box appears, but plasma started "normal" after closing the window
EXPECTED RESULT
ksmserver shouldn't need write access to ~/ (top directory) or at least not
require the user to close the msg box before anything can be done. A
notification would suffice.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Graphics Platform: Wayland
ADDITIONAL INFORMATION
My home directory(top level) is r-x------
The config, cache and data directories are rwx------
AFAIK Plasma ecosystem has implemented the base directory specification to
read/write its cache/configuration and data files from/to the user defined
locations (with fallback to ~/.cache ~/.config ~/.local/{state,share} if not
defined).
But ksmserver wants write access to ~/. After closing the mentioned msg box,
plasma starts fine as far as I can tell. Am using it and filling this bug
report now ... This implies, that write access is not really needed.
I must admit, that 99% of users may not notice this as they wouldn't change
manually the permissions of their $HOME and well, "who cares about the 1%". I
know, you guys have plenty of other more important things to do and I can
understand if you close the bug report. Nevertheless, I would appreciate if
someone would care, even a workaround will do the job, just don't want
ksmserver or any other part of my beloved desktop to stay in my way.
===============================
Here is the log from systemd journal (removed user and host name):
===============================
$ journalctl --user status ksmserver.service
× plasma-ksmserver.service - KDE Session Management Server
Loaded: loaded (/usr/lib/systemd/user/plasma-ksmserver.service; disabled;
preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-12-22 18:13:20 CET; 4min 41s
ago
Process: 13065 ExecStart=/usr/bin/ksmserver (code=exited, status=255/EXCEPTION)
Main PID: 13065 (code=exited, status=255/EXCEPTION)
CPU: 206ms
Dez 22 18:12:07 systemd[1278]: Starting KDE Session Management Server...
Dez 22 18:12:08 ksmserver[13065]: The following installation problem was
detected
Dez 22 18:12:08 ksmserver[13065]: while trying to start Plasma:
Dez 22 18:12:08 ksmserver[13065]: No write access to $HOME directory
(/home/userNAME).
Dez 22 18:12:08 ksmserver[13065]: Plasma is unable to start.
Dez 22 18:13:20 systemd[1278]: plasma-ksmserver.service: Main process exited,
code=exited, status=255/EXCEPTION
Dez 22 18:13:20 systemd[1278]: plasma-ksmserver.service: Failed with result
'exit-code'.
Dez 22 18:13:20 systemd[1278]: Failed to start KDE Session Management Server.
=================================
Here the listing of my user directory (redacted):
=================================
$ ls -lad ~
dr-x------ userNAME userNAME /home/userNAME/
$ ls -la ~
drwxr-x--- userNAME userNAME .cache/
drwxr-x--- userNAME userNAME .config/
drwxr-x--- userNAME userNAME .local/
--
You are receiving this mail because:
You are watching all bug changes.
