Deal with low level apt error messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
Triaged
|
High
|
Sebastian Heinlein |
Bug Description
There can be an exception from apt at several times. Unfortunately APT only shows a translated error message and no codes. Often it is unclear what the user should do.
Furthermore there can be a broken system, e.g. delted /var/lib/
E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/
<https:/
E:Write error - write (28: No space left on device), E:Can't mmap an empty file, E:The package lists or status file could not be parsed or opened.
<https:/
E: The package google-
E:Type 'http://
<https:/
SystemError: E:The package index files are corrupted. No Filename: field for package ubufox.
<https:/
Changed in aptdaemon: | |
status: | New → Triaged |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in aptdaemon: | |
importance: | Medium → High |
Changed in aptdaemon: | |
assignee: | nobody → Matthew Paul Thomas (mpt) |
Changed in aptdaemon: | |
status: | Triaged → In Progress |
Changed in aptdaemon: | |
status: | In Progress → Fix Released |
affects: | aptdaemon → aptdaemon (Ubuntu) |
Changed in aptdaemon (Ubuntu): | |
status: | Fix Released → In Progress |
no longer affects: | ubuntu |
description: | updated |
So does this need fixing in apt, not just aptdaemon? If apt returned an error code, not just a translated error message, the aptdaemon GUI could offer ways of recovering from the error. For example, the "No space left on device" error might trigger an apt-get autoremove. The "The package lists or status file could not be parsed or opened" error (why isn't that two separate errors?) might trigger regenerating the package list or restoring it from backup. And so on.