Useless computer

[Goldy]

Asumming the upgrade failed: I can't boot no metter what - after a while drop to the shell command line.

I want you to program a fail-safe command: insted of having a useless computer (one unbootable operating system), I want to be able to fix it by: "sudo do-release-upgrade" so I could boot again in the future, as the problem solved in next release.

For many very annoing reasons, all I have is a cards-reader & a hard-drive.

Thank you!

[Chris Coulson (chrisccoulson)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

[Chris Coulson (chrisccoulson)]

Is there not more files in there?

[Goldy (sutrdudk)]

Whay R U erasing my key-words?

[Chris Coulson (chrisccoulson)]

The tag system is a useful tool for grouping bug reports and aiding workflow. When people start filling tags with generic keywords or general search terms, the number of tags grows and the whole thing becomes a lot less useful (there are so many tags that the useful ones are difficult to find and you may as well just use the search engine).

I've seen a lot of people use really silly tags, such as words in the title of the bug report (you can already search bug titles), the package names the bug is assigned to (you can already list the bugs assigned to a package), and words such as "the" and "and".

For this reason, I prefer to remove the less useful and non-value-added tags from a bug report when I touch it (some people might leave them as they are, and some people might disagree with me entirely)

In addition to that - "update" is a tag we already use for tagging bug reports requesting the introduction of a new upstream version of a package. This bug report isn't requesting a package update so it shouldn't have that tag. Your other tags had nothing to do with this bug report, which is an upgrade failure.

I hope you understand that.

FYI, we have some common tags used for upgrade failures. In your case, an appropriate tag is "intrepid2jaunty". Some common tags used by the bugsquad can be found here: https://wiki.ubuntu.com/Bugs/Tags. There are many other teams that use their own tags too.

[Goldy (sutrdudk)]

A) Then let only 'professional' responders to add tags.

B) I ment to EVERY upgrade, not just the 8.10 to 9.04, but something like "present2future" or similar.

C) Please add a simulator program that will allow the user to SIMULATE the ISO file, as if it has been installed. that way the user will not have to waste time & hardware. (Isit a new bug?)

Thanks.

[Chris Coulson (chrisccoulson)]

I'm slightly confused here. Are you reporting a specific upgrade bug or not?

[Goldy (sutrdudk)]

Not a specific: after any upgrade; it's possible that the boot process will fail: droping to the shell command line & that it (typing "exit" will necessarily cause kernal panic).
I want the possbility to fix the problem by being able to upgrade as soon as the problem being solved (next release).

OR: to save "burn + boot from USB", it's better to have a program that will simulate the ISO file, as if the computer has been boot from.

Do one of the above. Thanks.

[Krzysztof Debski (fantom15)]

1. You already have an option to make bootable USB (System->Administration menu)
2. You can use virtual machine to "simulate the ISO file, as if the computer has been boot from.":
http://www.virtualbox.org/

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]