| Summary: | Kdeinit5 unable to write to NFS share | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kinit | Reporter: | Bobby <bigbrovar> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | christoph, kde, kdelibs-bugs, kelleher, max.schettler, nate |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
apt history.log
.xsession-errors |
||
|
Description
Bobby
2019-05-23 07:06:42 UTC
> 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. 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! 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! |