Adept not very smart about network being down
Bug #44105 reported by
Joshua Kugler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Adept Manager |
Unknown
|
Medium
|
|||
adept (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: adept
After my shiny new Kubuntu Flight 7 install, I went to install the 127 update packages available. Well, The updater (and stand alone adept) would start to install the upgrades, and then immediately tell me that the transaction failed.
I finally discovered that my network was not up (another bug, also reported). So, it would seem that instead of reporting "transaction failed" adept needs to first determine if the network is up, and return an informative error message about that.
Changed in ept: | |
assignee: | nobody → me-mornfall |
status: | Unconfirmed → Confirmed |
Changed in adept: | |
status: | Confirmed → Triaged |
Changed in adeptmgr: | |
status: | Unknown → New |
Changed in adeptmgr: | |
importance: | Unknown → Medium |
Changed in adeptmgr: | |
status: | New → Unknown |
To post a comment you must log in.
I don't agree with this bug being a "wishlist" bug. If a user does not know their network is not up, and they try to update, they are immediately going to write for help saying "Updates aren't working," or they are simply going to give up on Ubuntu because it "doesn't work right." I know I would have given up if I hadn't known to go to the prompt and type "apt-get upgrade," which is how I found out my network was down.