kubuntu-devel-release-upgrade -- crashes

[Spadge]

I've just started following the upgrade how-to on https://help.ubuntu.com/community/Qu...grades/Kubuntu and during the process the kubuntu-devel-release-upgrade crashes.

I'm a bit concerned now as all my software sources have been updated.

The process gets part way through 'setting channels' and just exits without any message.

Any advice on where to look for what's causing the problems?

Thanks

[Spadge]

2012-09-27 21:17:35,437 DEBUG running doUpdate() (showErrors=True)
2012-09-27 21:17:35,787 DEBUG openCache()
2012-09-27 21:17:35,787 DEBUG failed to SystemUnLock() (E:Not locked)

last 3 lines from 'cat /var/log/dist-upgrade/main.log' - I don't know if it means anything particularly.

[Shimapan]

No idea what happened there, but it was the same for me when I upgraded two weeks ago. After setting up sources and all, it silently exited. Launched it a second time, it exited a second time.

Don't Panic!

That doesn't really matter actually, as you can complete the upgrade all by yourself, once the sources have been set up. I simply started up Synaptic, reloaded the new repository list, marked all avaiable upgrades, took a *close* look at what it wanted to update, install and remove, and then lowered the flag for the big upgrade race
After it had downloaded all the stuff, it took a good while (about an hour) to apply all the changes, but it all went very smooth and without any errors.

Note: If you have the xorg-edgers repository installed, you need to add the Quantal version of the xorg-edgers repository *before* applying the changes, then reload the repository list once more, mark all updates, and you're good to go.

The above *might* also work with the Muon package manager. Then again, it might not. It's up to you if you want to risk to use it for such a long and complicated operation.

[claydoh]

If it crashed after setting the software sources, and did not proceed any further, the upgrader has only edited the apt sources lists. You should be able to go and correct this to change all the repoitories from specifying "quantal" back to "Precise". If you attempt to install software in this state, it could pose problems as it may want to install Quantal packages that will likely give you dependency errors, but it may also attempt to upgrade everything. You can also try upgrading to 12.10 by running:

sudo apt-get update
sudo apt-get dist-upgrade

If you are unsure if the info given before proceeding is OK, just copy and paste the output here and we can look at it before proceeding.


Now, if the upgrader only changed the sources without installing anything, you can fix that and remain in Oneiric, this can be done in a number of ways. One is to open Muon Package Manager (yes, Shimapan Muon ) and look for "Configure Software Sources" in the Settings menu. Selecting that option will open an external application that manages your sources (the same thing opens when you select the same option in Synaptic. btw. This way you don't have to attempt to install new software, and in your current state, as you may have dependency errors trying to do this). Once in there, in the "Other Software" tab will be a list of repositories. With each listing that is checked, you can select it, click Edit, and change Quantal to Precise. If you have any PPA's installed, the will have been labeled as having been disabled for the upgrade, so will be un-checked in the main listing. You can edit those as well, and re-check them. after that, it will refresh your package list and you should be back to where you were.

Another way is to open Kate with kdesudo (hit alt-f2, then type "kdesudo kate").
Open your /etc/apt/sources.list file, and change any instance of "quantal" back to "precise", making sure not to edit anything else and that everything is using the proper case - precise with a small 'p'. Then you can manually update.

The upgrade tool does a bit more behind the scenes than just changing your software sources, and it does prompt you before it does any actual downloading, installing, or removing anything. This is why you should be OK doing this if you want to go back.

Please do report your bugs to launchpad if you can. The upgrader can be run from a terminal, using either the command given in the wiki instructions, or by typing

sudo do-release-upgrade -d

which will run it completely in the terminal. Either way might give valuable info as to where and why it crashed.

[Shimapan]

Now, if the upgrader only changed the sources without installing anything...

Yes, it only sets up the sources and such, but silently exits before it downloads, much less installs anything.
Going from the image in the guide:



It performs the first two steps (Preparing and Setting up), but silently exits after that and never gets to the third step ("Getting new packages").
Thus, there won't be any dependency problems, because nothing was installed yet. As all repositories have already been set up for Quantal at that step, you can just go to Synaptic, reload the list, and mark all upgrades (just remember to add the xorg-edgers repository for Quantal if you have been using it before.) Or, you could also use Muon for that, at your own risk.

[Spadge]

The end of the output from 'do-release-upgrade -d' is:

9 packages are going to be removed. 202 new packages are going to be
installed. 1438 packages are going to be upgraded.

You have to download a total of 11.7 M. This download will take about
2 seconds with your connection.

Installing the upgrade can take several hours. Once the download has
finished, the process cannot be canceled.

... I think I will leave it until tomorrow. I have to boot into windows for some gaming in 3 hours.

BTW, I have British English localisation so 'canceled' ought to be 'cancelled'.

[Shimapan]

The end of the output from 'do-release-upgrade -d' is:

9 packages are going to be removed. 202 new packages are going to be
installed. 1438 packages are going to be upgraded.

You have to download a total of 11.7 M. This download will take about
2 seconds with your connection.

Installing the upgrade can take several hours. Once the download has
finished, the process cannot be canceled.

Did you take a look at the packages it wants to remove? It shouldn't be anything serious, but better safe than sorry.

BTW, I have British English localisation so 'canceled' ought to be 'cancelled'.

So it's really "Canceled" in American English? Good heavens. Those ghastly Yankee spellings really give me the creeps
And it's so inconsequent, too. Why don't they write "hor" instead of "hour"? After all, they also write "color" instead of "colour"

[Spadge]

Did you take a look at the packages it wants to remove? It shouldn't be anything serious, but better safe than sorry.

The only package it wanted to remove that looked in any way suspicious was amarok. I say suspicious because it was keeping the -common and other stuff that goes with it.

So it's really "Canceled" in American English? Good heavens. Those ghastly Yankee spellings really give me the creeps
And it's so inconsequent, too. Why don't they write "hor" instead of "hour"? After all, they also write "color" instead of "colour"

I know! Barbarians.

[Shimapan]

The only package it wanted to remove that looked in any way suspicious was amarok. I say suspicious because it was keeping the -common and other stuff that goes with it.

Pretty pointless to keep -common and such, when amarok itself is removed... Just go ahead and remove the rest as well. Clementine is better, anyway

I know! Barbarians.

Guess they just can't help it, as their school system is a true Epic Fail. Just take a look at the result of their school system
http://www.youtube.com/watch?v=fJuNgBkloFE

[SteveRiley]

Why don't they write "hor" instead of "hour"? After all, they also write "color" instead of "colour"

We can't drop the "u" from "hour" because it would change the pronunciation! J. Random American would probably go pretty crazy if the answer to "What time is it?" sounded like "23 hundred whores." Oh, wait, J. Random American wouldn't understand 24-hor time anyway.

[Spadge]

Just a thought ... if you're removing nvidia-current as a matter of course, and replacing it with nouveau, would it not be a *really* good idea for the update script to check to see if nvidia-current has added a blacklist file into /etc/modprobe.d/ before offering to restart the machine?

[Spadge]

The command line option worked for me without any hitches. I strongly recommend it over the flaky GUI version.

In fact, I don't know what I was thinking! I always prefer to do stuff like that on the CLI rather than the desktop.

Thanks everyone for all the help.

[Shimapan]

We can't drop the "u" from "hour" because it would change the pronunciation! J. Random American would probably go pretty crazy if the answer to "What time is it?" sounded like "23 hundred whores." Oh, wait, J. Random American wouldn't understand 24-hor time anyway.

There are other examples still, but this is getting too off-topic here. We'd better continue here:
http://www.kubuntuforums.net/showthr...ican-spellings

The command line option worked for me without any hitches. I strongly recommend it over the flaky GUI version.

In fact, I don't know what I was thinking! I always prefer to do stuff like that on the CLI rather than the desktop.

Thanks everyone for all the help.

Glad that everythink worked out for you.