Public bug reported:
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/Xsession),
this is accomplished by changing the value of $ERRFILE. It's
unfortunate that gdm lacks this functionality.
Relevant information:
jdr...@infinite-loop:/etc/X11$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
jdr...@infinite-loop:/etc/X11$ apt-cache policy gdm
gdm:
Installed: 2.20.10-0ubuntu2
Candidate: 2.20.10-0ubuntu2
Version table:
*** 2.20.10-0ubuntu2 0
500 http://ubuntu.media.mit.edu jaunty/main Packages
100 /var/lib/dpkg/status
** Affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
gdm should not hardcode name of ~/.xsession-errors
https://bugs.launchpad.net/bugs/382879
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
