[Bug 1315307] [NEW] [wishlist] Add a “big friendly button” in case do-release-upgrade crashed in the middle of the upgrade.

[Martin Bodin]

Public bug reported:

Hi,
I hope you won’t mind if I’m not looking for dupplicates, as I’m now writing this bug report directly on Links due to a dist-upgrade crash.

If you’re using Ubuntu, that’s probably not the first time you tried to
dist-upgrade your computer to a new version of Ubuntu and have d
-release-upgrade that crashes in the middle.  I may using it wrong—from
what I’ve seen in this Links session in the Internet, it seems that “do-
release-upgrade” is depreciated and that we should use “update-manager-
text”, which is *not* a package installed by default (who said Ubuntu
should be simple to use? ☺)… that already seems like a good bug report.

What I’m asking for such crash-in-the-middle cases, is that do-release-upgrade (or upgrade-manager-text, I don’t mind as soon as the wrong one asks if we’re sure we shouldn’t using the right one) add an option to Grub at the beginning of the upgrade, option that will be removed as soon as everything is sure to be finished.
This option (that I call a “big friendly button”) should run a consol-mode program able to:
→ Recomfort the user by explaining to him/her that yes, something crashed, but there is now this option that shows that we’re still taking care of his/her case.
→ Suggest some option—and explaining them (please do not forget that the causal user is not necessarily a fan of Links, or able to fix the network-manager package by his/herself!)—such as “sudo dpkg --configure -a”, and all the options that do-release-upgrade could launch if it had crashed in the middle.
→ Suggest some command to run to check that the fix really worked:  it’s always an akward moment when you *think* that the system is fixed, but you’re not *sure* of it.  A command that would check that everything seems right would be extremely appreciated.

Please, think about people like me that actually know nothing about the innerthings of package managment and what really is a dist-upgrade, but whose luck sistematically lead to a crash in the middle of the upgrading (while a message was displayed in the beginning:  “do not interupt the installation under any reason once the installation process is started”, which just stress me more when I discover the computer crashed in the middle of it :-\).
Thanks by advance!
Martin.

** Affects: update-manager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1315307

Title:
  [wishlist] Add a “big friendly button” in case do-release-upgrade
  crashed in the middle of the upgrade.

Status in “update-manager” package in Ubuntu:
  New

Bug description:
  Hi,
  I hope you won’t mind if I’m not looking for dupplicates, as I’m now writing this bug report directly on Links due to a dist-upgrade crash.

  If you’re using Ubuntu, that’s probably not the first time you tried
  to dist-upgrade your computer to a new version of Ubuntu and have d
  -release-upgrade that crashes in the middle.  I may using it
  wrong—from what I’ve seen in this Links session in the Internet, it
  seems that “do-release-upgrade” is depreciated and that we should use
  “update-manager-text”, which is *not* a package installed by default
  (who said Ubuntu should be simple to use? ☺)… that already seems like
  a good bug report.

  What I’m asking for such crash-in-the-middle cases, is that do-release-upgrade (or upgrade-manager-text, I don’t mind as soon as the wrong one asks if we’re sure we shouldn’t using the right one) add an option to Grub at the beginning of the upgrade, option that will be removed as soon as everything is sure to be finished.
  This option (that I call a “big friendly button”) should run a consol-mode program able to:
  → Recomfort the user by explaining to him/her that yes, something crashed, but there is now this option that shows that we’re still taking care of his/her case.
  → Suggest some option—and explaining them (please do not forget that the causal user is not necessarily a fan of Links, or able to fix the network-manager package by his/herself!)—such as “sudo dpkg --configure -a”, and all the options that do-release-upgrade could launch if it had crashed in the middle.
  → Suggest some command to run to check that the fix really worked:  it’s always an akward moment when you *think* that the system is fixed, but you’re not *sure* of it.  A command that would check that everything seems right would be extremely appreciated.

  Please, think about people like me that actually know nothing about the innerthings of package managment and what really is a dist-upgrade, but whose luck sistematically lead to a crash in the middle of the upgrading (while a message was displayed in the beginning:  “do not interupt the installation under any reason once the installation process is started”, which just stress me more when I discover the computer crashed in the middle of it :-\).
  Thanks by advance!
  Martin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1315307/+subscriptions