Debconf interactions no longer working
Bug #1627757 reported by
Larry Price
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Libertine | Status tracked in Devel | |||||
Devel |
Fix Released
|
Medium
|
Larry Price | |||
Trunk |
Fix Released
|
Medium
|
Larry Price | |||
libertine (Ubuntu) |
Fix Released
|
Medium
|
Larry Price |
Bug Description
Yakkety, libertine trunk, python3-lxc 2.0.4.
To reproduce:
* Create a container
* Enable multiarch
* In the GUI, install "steam"
* Navigate to the PackageInfoView
* In the informational section, you are prompted to agree to TOS
* Type "1" to disagree or "2" to agree and hit Return
Nothing happens. The QProcess believes that it has sent the bytes to the process, but it seems that the container never gets it.
Related branches
lp:~larryprice/libertine/fix-debconf
- Libertine CI Bot: Approve (continuous-integration)
- Christopher Townsend (community): Approve
-
Diff: 196 lines (+32/-22)6 files modifiedlibertine/ContainerManager.cpp (+2/-2)
python/libertine/ChrootContainer.py (+2/-2)
python/libertine/Libertine.py (+8/-8)
tools/completions/libertine-container-manager (+2/-2)
tools/libertine-container-manager (+8/-8)
tools/libertine-container-manager.1 (+10/-0)
lp:~townsend/libertine/1.4.2-release
- Larry Price: Approve
-
Diff: 375 lines (+68/-40)11 files modifieddebian/changelog (+16/-0)
libertine/ContainerManager.cpp (+2/-2)
libertine/libertine.cpp (+1/-1)
libertine/libertine.h (+1/-1)
libertine/qml/ExtraArchivesView.qml (+1/-7)
python/libertine/ChrootContainer.py (+4/-4)
python/libertine/Libertine.py (+22/-13)
python/libertine/LxcContainer.py (+1/-1)
tools/completions/libertine-container-manager (+2/-2)
tools/libertine-container-manager (+8/-9)
tools/libertine-container-manager.1 (+10/-0)
Changed in libertine: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in libertine (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Larry Price (larryprice) |
To post a comment you must log in.
I'm fairly certain this is directly related to a bug I've filed with lxc where attach_wait permanently steals stdin from the python process (https:/ /github. com/lxc/ lxc/issues/ 1137).
After digging through the python-lxc code a bit, it's unclear to me why this might be happening. Also considering that the bug I filed has been completely ignored, I think we'll need to find a workaround instead of relying on a real fix upstream.
I'm going to investigate possibly pushing the attach_wait command into its own process, and then redirecting stdin/stdout as possible.