If a user has a 'set' command like: set noclobber or set filec in their .bashrc file, then when logging in from gdm, the .bashrc file is executed from /etc/X11/gdm/Xsession. The argument of the last 'set' command is inserted as the command that is run in place of the correct session. This is fixed by moving the line: command="$1" in /etc/X11/gdm/Xsession from its current position, up to somewhere before the .bashrc file is executed. Reproducible: Always Steps to Reproduce: 1. put: 'set noclobber' into a user's .bashrc file 2. try to login as that user from gdm Actual Results: The session fails to start correctly with an error saying that 'noclobber' can't be found.
this seems to be similar to 39215
this should be fixed now, see upstream: http://bugzilla.gnome.org/144007 and the diff: http://cvs.gnome.org/viewcvs/gdm2/config/Xsession.in?r1=1.12&r2=1.13
