Upgrading to Ubuntu Edgy Eft a "Nightmare"

Theovon writes, "It's only been two days since the announcement of the official release of Ubuntu 6.10 (Edgy Eft), and the fallout has been very interesting to watch. By and large, fresh installs of Edgy tend to go well. Many people report improved performance over Dapper, improved stability, better device support, etc. A good showing. But what I find really interesting is the debacle that it has been for people who wanted to do an 'upgrade' from Dapper (6.06). Installing OS upgrades has historically been fraught with problems, but previous Ubuntu releases, many other Linux distros, and MacOS X have done surprisingly well in the recent past. But not Edgy." Read on for the rest of Theovon's detailed report.

Reports are flooding in to Ubuntu's Installation & Upgrades forum from people having myriad problems with their upgrades. One user described it as a 'nightmare.' Users are producing detailed descriptions of problems but getting little help. This thread has mixed reports and is possibly the most interesting read. Many people report that straightforward upgrades of relatively mundane systems go well, but anything the least bit interesting seems not to have been accounted for, like software RAID, custom kernels, and Opera. Even the official upgrade method doesn't work for everyone, including crashes of the upgrade tool in the middle of installing, leaving systems unbootable, no longer recognizing devices (like the console keyboard!), reduced performance, X server crashes, wireless networking problems, the user password no longer working, numerous broken applications, and many even stranger things. Some of this is fairly subjective, with Kubuntu being a bit more problematic than Ubuntu, with reports that Xubuntu seems to have the worst problems, and remote upgrades are something you don't even want to try. Failed upgrades invariably require a complete reinstall. The conclusion from the street, about upgrading to Edgy, is a warning: If you're going to try to take the plunge, be sure to make a backup image of your boot partition before starting the upgrade. Your chances of having the upgrade be a total failure are high. If you're really dead-set on upgrading, you'll save yourself a lot of time and headache by backing up all of your personal files manually and doing a fresh install (don't forget to save your bookmarks!).

Comments

It's been out, what, three days?

[Plug]

Users are producing detailed descriptions of problems but getting little help

I remember rushing to try XGL and Compiz the day they were released, and getting nowhere. About a week later the smart people who do such things had figured it out, and I was able to run it, but it was still pretty 'hardcore' and prone to breakage. About three weeks later it was simple.

Don't upgrade on the first day and expect things to go smoothly. You can only be as good as your last RC, and not enough people upgrade them to be able to find all the bugs. Wait a week and then answers will have been found for all the common problems.

Open source is crying out for more QA people. All you have to do is report a bug, or help by triaging the bugs that are there. It's a contribution that almost anyone can make.

Re:The change no-one mentioned: bash-dash

[ChrisJones]

This is a symptom of a long-standing misunderstanding about shell scripting.
If you have #!/bin/sh you should be using POSIX shell, which will execute fine in bash, dash or the old sh. People run into problems because they've put #!/bin/sh and then used bash-only syntax - ie they should already have used #!/bin/bash, but didn't because they didn't read any docs and don't know better.

Re:The change no-one mentioned: bash-dash

[cortana]

It would be nice if bash rejected the use of (or at least spewed warnings about) bash-extensions when it is invoked as sh.