Can not log in when homedir permissions are set `o-x`
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lightdm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
When mounting home directories over NFS with root squashing, users with home directories with the execute bit unset for other (i.e. `chmod o-x $HOME`) will not be able to log in via lightdm. The log in appears to be successful, the screen blinks, and then the log in screen returns. Users should be able to log in via lightdm in a root-squashed environment without requiring the execute bit set for everyone on the home directory.
$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10
$ apt-cache policy lightdm
lightdm:
Installed: 1.0.1-0ubuntu6
Candidate: 1.0.1-0ubuntu6
Version table:
*** 1.0.1-0ubuntu6 0
500 http://
100 /var/lib/
==> /var/log/
[+4245.45s] DEBUG: Opened ConsoleKit session 45a196b38946d74
[+4245.45s] DEBUG: Dropping privileges to uid 11248
[+4245.45s] DEBUG: Adding session authority to /u/jesusaur/
[+4245.47s] DEBUG: Restoring privileges
[+4245.47s] DEBUG: Launching process 10563: /usr/sbin/
[+4245.47s] WARNING: Failed to change to home directory /u/jesusaur: Permission denied
[+4245.48s] DEBUG: Registering session with bus path /org/freedeskto
[+4245.48s] DEBUG: Process 10563 exited with return value 1
==> /var/log/auth.log <==
Nov 3 21:23:57 sizeof lightdm: pam_unix(
| security vulnerability: | yes → no |
| security vulnerability: | yes → no |
| visibility: | private → public |
| visibility: | private → public |
| Reinhard Tartler (siretart) wrote | #1 |
| Lauri Tirkkonen (lotheac) wrote | #2 |
| Lauri Tirkkonen (lotheac) wrote | #3 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 877766, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.