Bug 144309 - More specific error message when KDE login fails
Summary: More specific error message when KDE login fails
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian stable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-16 19:16 UTC by Raga Prong
Modified: 2020-10-29 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raga Prong 2007-04-16 19:16:39 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Debian stable Packages
OS:                Linux

KDE login usually fails when there is no write access to $HOME (~/.). To make it easier for amateur administrators in home and office networks, it would be a great step forward to provide more specific error messages (rather than: Missing $HOME).

And this is what should be checked (and reported interactively) in case of failure:

 * Does $HOME exist at all (readable)?
 * Is there space left on $HOME?
 * Does quota exceed its limit?
 * Is there write access to $HOME? (Owner?)
 * Is the file system mounted where $HOME is?
   (if so, is it mounted r/w?)
 * If $HOME points to a network device (NFS)
   that is not mounted: Was this due to access
   issues (netgroups)? Is the server exporting
   NFS shares reachable?

It might be discussed, to what extend these informations should be provided/prepared by pre-login processes. But KDE login-failure must offer a way to forward this information. If there is no central "mocking box" defined, worst case display output of dmesg on demand...
Comment 1 20120808_bugs.kde.org 2010-02-20 11:17:05 UTC
related to the case presented in #81653
Comment 2 Nate Graham 2020-09-29 22:40:46 UTC
Is this still a problem in recent versions of Plasma 5, like 5.19 or later?
Comment 3 Bug Janitor Service 2020-10-14 04:33:15 UTC
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!
Comment 4 Bug Janitor Service 2020-10-29 04:33:34 UTC
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!