[Bug 1554010] Re: Paths ($PATH, $LD_LIBRARY_PATH) in click package are set up in wrong order
Pat McGowan
pat.mcgowan at canonical.com
Tue Mar 8 22:09:32 UTC 2016
** Also affects: click (Ubuntu)
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Alejandro J. Cura (alecu)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1554010
Title:
Paths ($PATH, $LD_LIBRARY_PATH) in click package are set up in wrong
order
Status in Canonical System Image:
Confirmed
Status in click package in Ubuntu:
New
Bug description:
When binaries in click packages are launched, the paths inside the
click package are added to PATH and LD_LIBRARY_PATH so that app
developers don't need to fiddle with wrapper scripts when they ship
their own dependencies.
This usually works nicely, but can start to fail in unexpected ways if
the seed for the image changes or the user enables writeable mode and
apt-get installs things. As soon as self-shipped binaries and
libraries show up in the system with the same name for whatever
reason, those take precedence and the system-installed binary/library
is loaded instead of the one in the click package.
To solve this, the package-local variables should be set up in a
different order, so that package-local stuff has precedence.
This can be reproduced with the example of the app netscan.mzanetti in the store. It works fine when installing it on a freshly flashed device. Now enable rw mode and apt-get install nmap. The app will start failing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554010/+subscriptions
More information about the foundations-bugs
mailing list