Kde is unable to start when user home is an NFSv3 share. I can also confirm this to happen when you try to run a kde application in other desktop environment like gnome or even mint. I get this error qt5ct: using qt5ct plugin XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "mtp" kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found kdeinit5: Aborting. No write access to $HOME directory (/home/user). No text-to-speech plug-ins were found. trying to load "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so" from "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so" XmbTextListToTextProperty result code -2 Segmentation fault (core dumped) STEPS TO REPRODUCE 1. Try login to a KDE session or a run a kde application on another desktop environment. 2. Application fails with kdeinit5 complaining of inability to write to home directory 3. Home directory is writable from the shell and other non kde applications are working fine OBSERVED RESULT qt5ct: using qt5ct plugin XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "mtp" kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found kdeinit5: Aborting. No write access to $HOME directory (/home/user). No text-to-speech plug-ins were found. trying to load "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so" from "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so" XmbTextListToTextProperty result code -2 Segmentation fault (core dumped) EXPECTED RESULT Kde application should run fine even in a nfs share which is well configured and writable to the user SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12 LTS KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
> kdeinit5: Aborting. No write access to $HOME directory (/home/user). That seems to be the precise problem.
Try setting KDE_HOME_READONLY in your environment
(In reply to Kai Uwe Broulik from comment #2) > Try setting KDE_HOME_READONLY in your environment Please kindly direct how best to do this. I created a env directory in .kde/env/kile.sh with the following content export $KDE_HOME_READONLY It however made no difference, I still have same issue. Also is there a way I can make this global just in case it fixes the issue.
This affects me as well (on Debian 10). The workaround using KDE_HOME_READONLY works for me, I created a file /etc/xdg/plasma-workspace/env/nfs_home_workaround.sh with the content export KDE_HOME_READONLY=x.
I can confirm this bug and workaround on kubuntu 20.04. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal $ $ ls -la $HOME/.config/plasma-workspace/env/nfs_home_workaround.sh -rwxr-xr-x 1 -------- -------- 42 Jun 3 12:03 /vol/home/----/.config/plasma-workspace/env/nfs_home_workaround.sh $ $ cat $HOME/.config/plasma-workspace/env/nfs_home_workaround.sh #!/bin/sh export KDE_HOME_READONLY=TRUE $
The KDE_HOME_READONLY workaround stopped working and failure behavior changed last week after I applied updates to kubuntu 20.04. Instead of a logout as previously experienced, NFS home now results in a black screen with a mouse pointer. See attached apt history.log and .xsession-errors for more details. Please let me know what additional information I can provide to help resolve this issue. Thanks.
Created attachment 129548 [details] apt history.log apt history log showing updates that correspond to timing of KDE_HOME_READONLY workaround no longer working.
Created attachment 129549 [details] .xsession-errors .xsession-errors file for new black screen behavior after recent updates. Note that the read-only home directory error is no longer displayed, so not sure how this relates to previous behavior.
We used nfs3 for years without issues and now nfs4 at work, please retry with a recent release.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Just tested again on Debian 11 with Plasma 5.20. Without the workaround mentioned above the problem persists.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
This is a fairly old bug report and the code has changed a lot since it was reported. In particular, kdeinit is gone entirely in Plasma 6. And people seem to be reporting multiple distinct issues here. I think at this point the sanest course of action is to open anew bug report for the specific issue you're experiencing, if you think it might be the same issue as this one. Because there's a good chance it's actually something different. Thanks everyone!