Read-only filesystem causes "unhandlable error"
Bug #1079895 reported by
Matthew Paul Thomas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
Confirmed
|
Low
|
Matthew Paul Thomas |
Bug Description
When /tmp/ becomes read-only, aptdaemon fails with an "unhandlable error" instead of presenting a useful error message.
<http://
[Originally reported by "MHK11395" in <http://
Changed in aptdaemon (Ubuntu): | |
importance: | Undecided → Low |
Changed in aptdaemon (Ubuntu): | |
status: | New → Confirmed |
no longer affects: | aptdaemon |
To post a comment you must log in.
Am Freitag, den 16.11.2012, 21:38 +0000 schrieb Matthew Paul Thomas: imgur.com/ I97mZ> www.reddit. com/r/Ubuntu/ comments/ 139f5p/ new_guy_ here_im_ getting_ this_error_ whenever_ i/>.]
> Public bug reported:
>
> When /tmp/ becomes read-only, aptdaemon fails with an "unhandlable error" instead of presenting a useful error message.
> <http://
>
> [Originally reported by "MHK11395" in
> <http://
There are a lot of ways to break your system. Should aptdaemon deal with
all of them in end? There are also people removing essential system
files that break APT completely.
What kind of error should we show?
We could introduce a new ERROR_SYSTEM_BROKEN which informs the user that
there is a serious problem with the system from which we cannot recover.
The "/tmp is read only" message would be shown in the details only.
Perhaps we could add links to support entry points?
Cheers,
Sebastian