Software-Center crash at launch if apt-history gzip archives are corrupted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
Fix Released
|
Medium
|
Olivier Tilloy | ||
Maverick |
Fix Released
|
Medium
|
Gary Lasker |
Bug Description
Binary package hint: software-center
If the apt history gzip archives contained in /var/log/apt/ are corrupted, then Software-Center crash at launch.
I attached the corrupted archive that triggered the bug on my laptop.
---
TEST CASE (for Maverick SRU):
1. Run Maverick.
2. In a terminal, type the following commands to temporarily swap in a corrupted apt history file (the original will be restored after):
wget https:/
sudo mv /var/log/
sudo cp history.log.5.gz /var/log/
3. Launch Software Center by typing the following into a terminal (this will allow you to verify the error output):
software-center
4. Verify that software-center crashes (does not start) and the error output in the terminal ends with:
"zlib.error: Error -3 while decompressing: invalid distance too far back"
5. Install the updated version of Software Center (3.0.9) from maverick-proposed.
6. Launch Software Center again from the terminal (or directly) and verify that Software Center now launches correctly (the main window is displayed, etc.).
7. Type the following in a terminal to restore your previous apt history log:
sudo mv /var/log/
Related branches
- software-store-developers: Pending requested
-
Diff: 73 lines (+31/-17)2 files modifieddebian/changelog (+8/-0)
softwarecenter/apt/apthistory.py (+23/-17)
Changed in software-center (Ubuntu): | |
importance: | Undecided → Medium |
Changed in software-center (Ubuntu Maverick): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
Changed in software-center (Ubuntu Maverick): | |
assignee: | nobody → Gary Lasker (gary-lasker) |
description: | updated |
description: | updated |
Changed in software-center (Ubuntu Maverick): | |
milestone: | none → maverick-updates |
Changed in software-center (Ubuntu): | |
assignee: | nobody → Olivier Tilloy (osomon) |
tags: | added: testcase |
Thanks for the report. I can confirm the issue with S-C 3.0.7 in maverick.
The issue was fixed in the trunk at revision 1284, available in S-C ≥ 3.1.1.
We may want to backport the fix to Maverick though, as it is a crasher that renders S-C unusable.