** Description changed: 1. 12.04.3 LTS - 2. + 2. lightdm: - Installed: 1.2.3-0ubuntu2.3 - Candidate: 1.2.3-0ubuntu2.3 - Version table: - 1.9.3-0ubuntu1 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - *** 1.2.3-0ubuntu2.3 0 - 990 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.2.1-0ubuntu1 0 - 990 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages + Installed: 1.2.3-0ubuntu2.3 + Candidate: 1.2.3-0ubuntu2.3 + Version table: + 1.9.3-0ubuntu1 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + *** 1.2.3-0ubuntu2.3 0 + 990 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.2.1-0ubuntu1 0 + 990 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages - 3. The expected behavior is to prioritize .bash_profile and then - .profile and execute interactively. + 3. The expected behavior is that .bashrc is called on login on desktop. + 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 .profile and .bashrc don't make any sense - because they they are called with a non-bash non-interactive shell. + presumably) and the provided .bashrc are not called because ligthdm- + session is non-bash non-interactive shell. - Please provide the expected workflow with regards to initializing an - environment. I'm quite vexxed why this has not been contested widely by - users. It was addressed here, but there is no explanation specific as to - the logic of this behavior and the contemplation regarding it is perhaps + 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://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/962270
-- 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/1252456 Title: Call ligthdm-session with bash interactive, check for bash_profile Status in “lightdm” package in Ubuntu: New 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://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages *** 1.2.3-0ubuntu2.3 0 990 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.1-0ubuntu1 0 990 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 3. The expected behavior is that .bashrc is called on login on desktop. 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://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/962270 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1252456/+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