"ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Fix Released
|
High
|
Unassigned | ||
apport (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Triaged
|
High
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned |
Bug Description
[ Impact ]
Extracting a crash file will always fail in case the crash report was processed.
[ Test plan ]
1. Create crash (e.g. with divide-by-zero):
```
sudo apt install chaos-marmosets
divide-by-zero
```
2. Click on "show details" in Apport crash UI, then close it
3. exract crash report:
```
tmpdir=$(mktemp -d)
apport-unpack /var/crash/
rm -rf "$tmpdir"
```
The extraction should work and not print a stack trace.
[ Where problems could occur ]
The change touches the problem report reading code which is used in several places. This could cause regressions in reading the problem report.
[ Original report ]
The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator:
$ grep separator /var/crash/
separator:
Traceback (most recent call last):
File "/usr/bin/
pr.
File "/usr/lib/
raise ValueError('%s has no binary content' %
ValueError: ['separator'] has no binary content
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
ProcVersionSign
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckR
CrashReports:
640:1000:
640:1000:
640:1000:
CurrentDesktop: i3
Date: Wed Jul 29 12:22:54 2020
InstallationDate: Installed on 2019-05-07 (448 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitec
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)
description: | updated |
Changed in apport: | |
milestone: | none → 2.23.0 |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in apport (Ubuntu): | |
importance: | Undecided → High |
Changed in apport: | |
status: | Fix Committed → Fix Released |
Changed in apport (Ubuntu Bionic): | |
status: | Confirmed → Triaged |
Changed in apport (Ubuntu Focal): | |
status: | Confirmed → Triaged |
Changed in apport (Ubuntu Jammy): | |
status: | Confirmed → Triaged |
Changed in apport (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in apport (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in apport (Ubuntu Jammy): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.