Adept Manager doesn't recover from interrupted dpkg runs
Bug #172592 reported by
Dennis Murczak
This bug report is a duplicate of:
Bug #48627: Poor resolution of "database locked" problem.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| adept (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: adept-manager
If Adept Manager crashes during installing some packages, it starts nagging about another running instance of a package manager and refuses to run. In fact, it just doesn't detect that the dpkg run had been interrupted. apt-get suggests dpkg --configure -a, which solves the problem. Adept Manager should be able to handle this situation too and just continue installing when it is run the next time, preferably after showing a helpful message explaining the problem to the user.
Revision history for this message
| Juan Carlos Torres (jucato) wrote | #1 |
| Changed in adept: | |
| status: | New → Fix Released |
Revision history for this message
| Juan Carlos Torres (jucato) wrote | #2 |
To post a comment you must log in.
This functionality has been added to the latest Adept version in Gutsy. It should ask you if you want to automatically resolve the problem when you start up Adept Manager. Selecting Yes will (ironically) crash Adept Manager once, but then it will resume normal working conditions after that.
I'm marking this bug as Fix Released. Please feel free to reopen it if there are other issues. Thanks for your efforts to make Kubuntu rock. :)