gdm should not hardcode name of ~/.xsession-errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm |
Fix Released
|
Wishlist
|
|||
gdm (Ubuntu) |
Fix Released
|
Wishlist
|
Ubuntu Desktop Bugs |
Bug Description
When an error occurs during login, the gdm slave will redirect errors to ~/.xsession-errors. The gdm daemon will then attempt to display the contents of the file to the user. If the user's home directory is on a networked filesystem that the daemon process does not normally have permission to read (NFS, AFS, etc), the user will never get to see the errors.
The user then has to find a way to login (perhaps in a tty session) and read their .xsession-errors file simply to be able to see what failed. This makes it extremely difficult to troubleshoot login problems in a network filesystem environment.
Ideally, gdm should allow the administrator to define the path of the errors file. In the traditional Xsession script (/etc/X11/
Relevant information:
jdreed@
Description: Ubuntu 9.04
Release: 9.04
jdreed@
gdm:
Installed: 2.20.10-0ubuntu2
Candidate: 2.20.10-0ubuntu2
Version table:
*** 2.20.10-0ubuntu2 0
500 http://
100 /var/lib/
Changed in gdm: | |
importance: | Unknown → Wishlist |
status: | Unknown → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.