lightdm doesn't call bashrc
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lightdm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
1. 12.04.3 LTS
2.
lightdm:
Installed: 1.2.3-0ubuntu2.3
Candidate: 1.2.3-0ubuntu2.3
Version table:
1.9.3-0ubuntu1 0
500 http://
*** 1.2.3-0ubuntu2.3 0
990 http://
100 /var/lib/
1.2.1-0ubuntu1 0
990 http://
3. The expected behavior is that .bashrc is called on login on desktop if the user's shell is bash. Please standardize and specify documentation with regards to the expected workflow for initializing an environment and executing .bashrc on desktop login.
4. What occurs is that lightdm-session is called with sh (dash presumably) and the provided .bashrc are not called because ligthdm-session is non-bash non-interactive shell.
It was addressed here, but there is no explanation specific as to the logic of this behavior and the contemplation regarding it is perhaps inadequate as it was not immediately apparent to the responders what was happening though it should be quite obvious as environment initialization is quite important:
https:/
| MetaChrome (imagenesis) wrote | #1 |
| description: | updated |
| summary: |
- Call ligthdm-session with bash interactive, check for bash_profile + lightdm doesn't call bashrc |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in lightdm (Ubuntu): | |
| status: | New → Confirmed |
To clarify, this refers to the unclear behavior of ligthdm-session and the provided profile and bashrc files.
Presumably, lightdm-session should be run non interactively as it is executing the display manager daemon.
I guess then this is an issue of whether we want to retain the current behavior of running with sh and providing the documentation to initializing the display environment. Namely:
1. In general, for what reason does one not want to execute bashrc if it is not an interactive shell (as provided by the standard bashrc?)
Perhaps it would be valuable to specify the behavior in documentation and also specify how the selection of a user's shell type ties in as this is a question I have as well.