Cannot install packages using the gui with a chroot backend
Bug #1599246 reported by
Christopher Townsend
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Libertine | Status tracked in Devel | |||||
Devel |
Fix Released
|
High
|
Larry Price | |||
Trunk |
Fix Released
|
High
|
Larry Price | |||
libertine (Ubuntu) |
Fix Released
|
High
|
Larry Price |
Bug Description
Using a chroot backend and the gui, trying to install a package fails with an error message of:
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
This doesn't happen when using the cli.
Related branches
lp:~larryprice/libertine/broken-chroot-packages
- Christopher Townsend (community): Approve
- Libertine CI Bot: Approve (continuous-integration)
-
Diff: 52 lines (+7/-8)2 files modifiedpython/libertine/Libertine.py (+5/-6)
tools/libertine-container-manager (+2/-2)
lp:~townsend/libertine/release-1.2.2
- Larry Price: Approve
-
Diff: 2202 lines (+838/-865)17 files modifieddebian/changelog (+30/-0)
debian/python3-libertine.install (+2/-0)
debian/rules (+3/-0)
libertine/qml/ExtraArchivesView.qml (+3/-6)
libertine/qml/GenericErrorDialog.qml (+17/-3)
libertine/qml/HomeView.qml (+51/-43)
po/CMakeLists.txt (+0/-3)
python/libertine/ChrootContainer.py (+26/-72)
python/libertine/ContainersConfig.py (+309/-0)
python/libertine/HostInfo.py (+71/-0)
python/libertine/Libertine.py (+17/-44)
python/libertine/LxcContainer.py (+19/-16)
python/libertine/utils.py (+1/-29)
tests/unit/CMakeLists.txt (+11/-7)
tools/libertine-container-manager (+269/-634)
tools/libertine-launch (+8/-8)
tools/libertine-session-bridge (+1/-0)
description: | updated |
Changed in libertine (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in libertine (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Larry Price (larryprice) |
To post a comment you must log in.
Looks like this is somehow caused by the "fix-integrity" command running.