add more sanity to the exit states of synapitc
Bug #58400 reported by
Christoph Wolk
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-app-install (Ubuntu) |
Fix Released
|
Low
|
Sebastian Heinlein | ||
Bug Description
We don't know what went wrong if gksu fails. Either the password dialog itself failed by provind a wrong password or synaptic could not apply the changes:
- failed download
- failed installation/
- falied lock
| Changed in gnome-app-install: | |
| assignee: | nobody → glatzor |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Michael Vogt (mvo) wrote | #1 |
| Changed in gnome-app-install: | |
| importance: | Untriaged → Medium |
| description: | updated |
| Changed in gnome-app-install: | |
| importance: | Medium → Low |
| Changed in gnome-app-install: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
We probably want to fix this by keeping a list of the expected results and comparing that to what we get when we re-read the package cache. Using the exit-status may be too unreliable, especially since gksu may mess with this status.