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 /etc/environment (which is the proper place to put system-wide environment variables), is not working. Hence even "/etc/environment for a solution to your problem" proposed by @ceg does not work. Bug #366728 also proposes a workaround by ~robinmillis : > However it seems that while Ubuntu does respect LD_LIBRARY_PATH, it has another mechanism for locating dynamic libraries. If you run sudo ldconfig --verbose, it rebuilds a cache of shared libraries. So if you add a shared library (as I did) to /usr/local/lib, the correct medicine to make it available to run sudo ldconfig. > Of course this doesn't solve the inconvenience that LD_LIBRARY_PATH is somehow unset during startup. Perhaps a wizard on ldconfig can explain more about this. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
