Thanks for the pointer!
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
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
The real bug in this case is bug #366728.
It is specific to LD_LIBRARY_PATH, and not other environment variables.
For example, if you set some environment variable in your /etc/profile
or ~/.profile, most likely the software will detect it.
However, LD_LIBRARY_PATH even if set in
PAM may be more appropriate then shell rc files (etc/pam.d)
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
See man pam_env, /etc/security/pam_env.conf and /etc/environment for
a solution to your problem.
If gdm used to source /etc/profile, and now stopped this misbehaviour,
that is good.
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug
Hope the solution above helps to understand this bug as invalid?
Shell config files are supposed to work only for (even specific) shells, pam is
more a global method.
** Changed in: ubuntu
Status: New = Invalid
--
LD_LIBRARY_PATH settings in /etc/profile lost
Hope the solution above helps to understand this bug as invalid?
Shell config files are supposed to work only for (even specific) shells, pam is
more a global method.
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
You received this bug notification
Hi microbug,
Can you try putting this line 'export LD_LIBRARY_PATH=some_path' into the
file /etc/bash.bashrc file and then checking whether still you get a blank for
'$LD_LIBRARY_PATH' or not?
Seems to be a bash related issue. Hence marking it as 'bash'...
--
LD_LIBRARY_PATH settings in
