Thanks for your report, Muru. Even if the default ~/.bashrc is protected from being run through a test at the top of the file, I think this will take care of a few cases where users with custom configuration have been somewhat confused.
** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Status: New => In Progress ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: gdm (Ubuntu) Importance: Undecided => Medium ** Changed in: gdm (Ubuntu) Status: New => Triaged ** Changed in: gdm (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: gdm (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1482641 Title: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc Status in gdm package in Ubuntu: In Progress Status in lightdm package in Ubuntu: In Progress Bug description: The fix for https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421 leads to `.profile` being sourced by bash instead of dash. This leads `.bashrc` being sourced indirectly via .profile. IMHO, `.bashrc` should not be sourced even *once* in this situation. I suggest that sourcing .profile actually be done with BASH_VERSION unset: BASH_VERSION= . "$CONFIG" At the very least, a check should be done whether bash is the user's login shell. It can be done thus: [ "$SHELL" != "/bin/bash" ] && BASH_VERSION= . "$CONFIG" utilizing `$SHELL` given it stores the login shell (http://unix.stackexchange.com/questions/45458/why-shell-doesnt- change-when-i-run-new-shell). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1482641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp