** Description changed: Binary package hint: update-manager Hello - When something went wrong during updates, apport start and report the error. - Then nothing more, the normal-user is layed on his own, with a system in an incomplete (sometimes unusable) status. - If the bug is really present in the package, this is the only and right way, but if not? - Too many times peoples reports bugs that can be fixed with cleaning the cash and running again the update. - So why the update-manager don't tray to manage this issue (clean cache - update - upgrade) invocking apport only at the second issue of the wrong update? - As Ubuntu is every day much more joined by not expert user i think that this point need to be evaluated in-depht + When something went wrong during updates, apport started and reported the error. + Then nothing more, the normal-user is left on his own, with a system in an incomplete (sometimes unusable) status. + If there is a bug present in the package, this is the only and right way, but what if not? + Too many times people report bugs that can be fixed with cleaning the cash and running again the update. + So why doesn't the update-manager try to manage this issue (clean cache - update - upgrade)? + As Ubuntu is every day much more joined by not expert users, I think that this point needs to be evaluated. + + Final thoughts:---- + Have the update manager offer the user a few things to try *before* reporting a bug. Common things like clearing the cache and performing apt-get update. Maybe a nice GTK window that has 2 buttons can pop up when an error is encountered during upgrade. One to close the error window, and one to report a bug. If the user wants he/she can try some of the items on the list in that window to solve the issue. If it still doesn't work, then on performing the next system-upgrade the user can select to "Report a bug" from that same GTK window.
** Description changed: Binary package hint: update-manager Hello When something went wrong during updates, apport started and reported the error. Then nothing more, the normal-user is left on his own, with a system in an incomplete (sometimes unusable) status. If there is a bug present in the package, this is the only and right way, but what if not? Too many times people report bugs that can be fixed with cleaning the cash and running again the update. So why doesn't the update-manager try to manage this issue (clean cache - update - upgrade)? As Ubuntu is every day much more joined by not expert users, I think that this point needs to be evaluated. - Final thoughts:---- + Final thoughts:---- Have the update manager offer the user a few things to try *before* reporting a bug. Common things like clearing the cache and performing apt-get update. Maybe a nice GTK window that has 2 buttons can pop up when an error is encountered during upgrade. One to close the error window, and one to report a bug. If the user wants he/she can try some of the items on the list in that window to solve the issue. If it still doesn't work, then on performing the next system-upgrade the user can select to "Report a bug" from that same GTK window. ** Description changed: Binary package hint: update-manager Hello - When something went wrong during updates, apport started and reported the error. - Then nothing more, the normal-user is left on his own, with a system in an incomplete (sometimes unusable) status. - If there is a bug present in the package, this is the only and right way, but what if not? - Too many times people report bugs that can be fixed with cleaning the cash and running again the update. - So why doesn't the update-manager try to manage this issue (clean cache - update - upgrade)? - As Ubuntu is every day much more joined by not expert users, I think that this point needs to be evaluated. + When something went wrong during updates, apport started and reported the error. Then nothing more, the normal-user is left on his own, with a system in an incomplete (sometimes unusable) status. If there is a bug present in the package, this is the only and right way, but what if not? Too many times people report bugs that can be fixed with cleaning the cash and running again the update. So why doesn't the update-manager try to manage this issue (clean cache - update - upgrade)? As Ubuntu is every day much more joined by not expert users, I think that this point needs to be evaluated. Final thoughts:---- Have the update manager offer the user a few things to try *before* reporting a bug. Common things like clearing the cache and performing apt-get update. Maybe a nice GTK window that has 2 buttons can pop up when an error is encountered during upgrade. One to close the error window, and one to report a bug. If the user wants he/she can try some of the items on the list in that window to solve the issue. If it still doesn't work, then on performing the next system-upgrade the user can select to "Report a bug" from that same GTK window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696755 Title: Update manager has to manage issues -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
