Upgrade to 7.10 hangs at "Modifying the software channels/Checking package manager"

Same here. update-manager hangs after confirming the dialog that support for some packages has ended. The state under the progress bar says "Asking for confirmation". After a coupe of minutes the update-manager in the taskbar tray reports that there are new updates available. The gutsy repositories have been added to the software packages list under third party packages. I have attached the dist-upgrade logs from after the crash.

Is there still CPU activity when this happens? I.e. does it show up in "top". Does the file /var/log/dist-upgrade/apt.log keeps changing (you can test by opening a terminal and running "tail -f /var/log/dist-upgrade/term.log" on it while doing the upgrade.

sorry, but i can't test any more because i've already performed a clean installation, leaving my /home partition.

I have the sam problem. Upgrade freeze at "Modifying the software channels/Checking package manager". No errors in logs. No disk and cpu activity.

I just tested it again: after the "some support for packages ended" dialog update-manager freezes. There is some disc and cpu activity for a little while after the freeze but then it just stops. The logs dont change anymore and the process called "gutsy" disappears from "top".

Have the same problem on a laptop at "Modifying the software channels/Checking package manager". But the problem doesn't appears on my desktop computer.

The day before the final release, I think this problem to be very important and urgent to solve !!!

BTW, I think its an important bug to solve.

If I kill the update-manager, the source-list keeps the modifications where "feisty" was replaced by "gusty". By this way, the update-manager believes on a normal update and propose the user to update normally.

I don't really know if this is bad (I've never tried), but I think logically that this will break the system. For beginners, not aware to the possible problem, this would results in an unusable linux.

So please, change the status to release critical.

Ok, I did some more testing and debugging on my machine:

The update-manager hangs on the this line in 'DistUpgradeViewGtk.py':

self.dialog_changes.set_transient_for(self.window_main)

None of the lines after that line are executed:

# work around problem that scroll_to() does not
# work when it is not realized
self.dialog_changes.realize()
self.treeview_details.realize()
self.treeview_details.set_cursor((0,))
self.treeview_details.scroll_to_point(0,0)
self.dialog_changes.window.set_functions(gtk.gdk.FUNC_MOVE)
res = self.dialog_changes.run()
self.dialog_changes.hide()
if res == gtk.RESPONSE_YES:
return True
return False

Here is what I did: I placed my own debug statements in the py file, recompiled and reran the gutsy executable from the temporary directory. The debug statements appeared in the main.log file up until the 'self.dialog_changes.set_transient_for(self.window_main)' line and stopped showing up on any line after that. This leads me to believe that either this line causes the problem itself or the problem occurs before in some other GUI function which freezes the GUI and finally hangs the entire program on this particular line.

Let me know if I can do some more debugging to get to the bottom of this.

Chris

For further clarification...

These are my statements from' DistUpgradeControler.py':

[...]
# My debug
logging.debug("Debug 1")

# ask the user if he wants to do the changes
res = self._view.confirmChanges(_("Do you want to start the upgrade?"),
                                        changes,
                                        self.cache.requiredDownload)

# My debug
logging.debug("Debug 2")
[...]

Result: Debug 1 appears in the log, Debug 2 doesnt. I traced the confirmChanges function with debug statements to the line of code mentioned in the comment above.

Hope this helps.

My upgrade froze at the last section "Installing Upgrades". The progress bar remains at 0% for applying changes.

I opened a terminal and ran, "ps aux | grep dist". There were four instances of DistUpgradeViewKDE.

I left it for 30 to 45 minutes as I got ready to go to work this morning. I ran the "ps aux | grep dist" again, and the four instances of DistUpgradeViewKDE were still there. The progress bar was still at 0%.

If there's something else I could check (after work), I'd be happy to help.

(P.S. This is my first bug report. I'm assuming the symptoms I'm seeing are related to the bug(s) described above. If not, I'd be happy to move this report.)

I am upgrading from rc to 7,10. The upgrade fails during the modifying software channels.
An error box appears saying the system is up to date.

closing the box and the wizard rolls the upgrade back.

running update goes back to the distribution update wizard.

I've got the same problem here. I'm trying to upgrade from feisty. hangs at fetching 54 of 59. Not sure what I'm supposed to do.

I can confirm the same problem on one of my desktops (after the "some support for packages ended" dialog, the update-manager freezes). Let me know if there is any information that I can collect to help debug this.

Same error :(

Hi!
I had got the same problem.

TO FIX:
Go menu: System / Administration / Software Sources.

I checked in the first tab:
Canonical-supported open....
Community-maintained open...
Propietary driver....
Sofware restricted by copyright....

I checked in the second tab:
Third-party....

I unchecked in the first tab:
Source code.....
Cdrom with Ubuntu 7.10.....

It works now perfect :D

Marquinos.

Aclaration:
I have got a hp nx7300 laptop ;) 1,8 Ghz, and 1 Gb RAM.

Me Too:

Upgrade from Feisty (released) to Gutsy (released) hangs on my Athlon K6 exactly as described by schroeder above.
I'm confused by marquinos workaround and am hoping someone can explain what is happening there, or preferably dig into schroeder's analysis.

This bug is preventing me from upgrading as well.
I have checked and unchecked in the manner described by marquinos as best as I could comprehend; however, I am still looking at a hung upgrade window.
This bug has borked my repositories. I'm sure I could go through and manually edit each one so I can continue using feisty, but I was hoping this bug would be resolved quickly enough to make this repair unworthy of my time.
Why is this bug not even being taken seriously? Not enough information (Excellent detective skills, schroeder). Not enough people affected (between this thread and the threads on the forums, it looks like the victims could be considerable)?
I implore you to increase the importance of this item.

Euclid, resetting the repos is easy. Go to System-Administration-Software Sources and check all desired repos and remove the gutsy stuff from the third party tab. Then you are back to feisty. I have done this multiple times, because I tried to ugrade over and over again. It is NOT an issue of a busy server or anything that would cure itself without intervention. The problem is also that everybody whose upgrade fails for whatever reason, thinks its THIS bug. And it is most likely not because all their problems seem to go away after a while. marquinos workaround didnt work for me, so he didnt have the same problem as us others here. And I, too, wish that it would get a little bit more attention. Of course I could do an 'apt-get dist-upgrade' from the console and probably be up and running with gutsy already but that's not the point. The point is we have an issue, let's take care of it.

I fixed my error with it hanging by going to System | Administration | Software Sources and switching the server to the US server instead of the 'Main Server'. After it reloaded the sources I ran the Update Manager and clicked the Upgrade button as recommended. It didn't hang then.

Ryan's solution didnt fix the problem. I still get the same error as before after using the US server. So, again it was proven that its not an issue with a server timeout like many people seem to have. Not surprising two days after the official release...

Going in System | Administration | Software Sources and switching the server to another server helped me. I'm French so I tried out Swiss servers.
But it doesn't explain why the cdupgrade from a DVD stops after the dialog giving the list of packages that are not supported anymore.

Switching servers did not solve it for me, either.

Thanks for the tip about resetting the repos, shroeder.

New aclaration: I did a new Ubuntu 7.10 intallation. Not an update.
I think that the repositories is uncheck is an important issue for solve.

Hi I have the same problem:

When upgrading from web it will hang at 'reading cache'.

When upgrading from the alternate cd it will hang at 'checking package manager'.

I tried changing source servers but that did not help.

This same issue has also been reported here:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/153984

p.s. here are the logs of /var/log/dist-upgrade

PartisanEntity and others arriving here because your Update Manager is hanging, you probably do _not_ have the same problem as the one for which this bug was opened. This bug is related to a hang of the Update Manager when it is "asking for confirmation" and apparently unable to pop up a confirmation box with the proposed updates/deletes.

If your update manager is hanging while "reading cache" or checking package manager your problem is probably related to the performance of the distribution servers and is discussed under the bug given by PartisanEntity: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/153984

Thanks schroeder!!

Changing the line you pointed out to just return True made my install/upgrade to continue.

The update-manager downloads the upgrade scripts and puts them in /tmp. What I did was to go into the directory /tmp/tmpwArERK/ (i assume the exact name will differ from machine to machine...) and change the line below in 'DistUpgradeControler.py':

Before change:
# ask the user if he wants to do the changes
res = self._view.confirmChanges(_("Do you want to start the upgrade?"),
                                        changes,
                                        self.cache.requiredDownload)
return res

After change:
#res = self._view.confirmChanges(_("Do you want to start the upgrade?"),
# changes,
# self.cache.requiredDownload)
return True #res

I then executed just the gutsy upgrade script (running update-manager again will not work since it downloads the script again):
sudo /usr/bin/python /tmp/tmpwArERK/gutsy --have-prerequists --with-network

I have to change directory to the /tmp/tmp* directory otherwise I get this error:
========================
user@ubuntu:~$ sudo /usr/bin/python /tmp/tmpn6vrDl/gutsy --have-prerequists --with-network
Traceback (most recent call last):
  File "/tmp/tmpn6vrDl/gutsy", line 30, in <module>
    logdir = config.get("Files","LogDir")
  File "/usr/lib/python2.5/ConfigParser.py", line 511, in get
    raise NoSectionError(section)

========================
This works, gotten further than before... Installing now:

#cd /tmp/tmpwArERK
#sudo /usr/bin/python /tmp/tmpwArERK/gutsy --have-prerequists --with-network

Henrik, that's a pretty slick hack. ;) Good to know that works.

Clemens, actually the confirmation box pops up and shows a list of packages that are not supported anymore. As soon as I hit "Close", update-manager freezes.

I would really like to know what the problem is but without some more knowledge about the workings of the script further debugging atempts dont make much sense.

Chris,
Sorry, my statement was misleading. Yes the "no longer supported" confirmation appears, but not the following "final list of added/removed packages for final approval/abort" confirmation. This problem has occurred on only one out of the three machines I've attempted to upgrade. If I can't figure it out in between doing other things today, I'll do what Henrik did,

Clemens, I agree. I will wait until tomorrow to see if there is any feedback and then go Henrik's route, too.

Since this seems to be a bug only with the GTK frontend, I simply circumvented it by using a different frontend, instead of hacking the scripts. This has the addidional benefit that you actually get the confirmation dialog, and can have a look which packages will be removed.

cd /tmp/tmpXXXXXX
./gutsy --help
sudo ./gutsy --frontend=DistUpgradeViewText --have-prerequists --with-network

You might also want to try DistUpgradeViewKDE (even if you're on Ubuntu) to get a graphical frontend (but I haven't tested it).

Chris: I tried commenting out the line you identified as the culprit in comment 8, but it didn't work, so either the real problem happens elsewhere, or the precompiled pyc files were used instead of the source scripts (my python is a bit rusty).

I had tried Kim's approach yesterday, but .../gutsy told me:
can't load DistUpgradeViewText, (No module named DistUpgradeViewText,)
GTK Accessibility Module initialized

... which I see now from the trailing comma was a cut and paste error. Sorry about that.

Kim, that was pretty clever. :) Thanks!

Upgrading...right...now.

I have the same issue.
Unfortunately Kim's solution did not work.
After downloading all packages system is trying to run Gtk for instalation process and of course hung.

"sudo update-manager -d"
 in fail-safe terminal session allow upgrade without any problems (at least on my machine).

Is anybody still having this problem or is running 'sudo update-manager -d' in a fail-safe session good enough. Future upgrades have aimed to solve this issue.

For now, I'm setting the Status to Fix Released. Feel free to set it back to New if the issue continues.

I had the same problem with 8.04 (and solved it the same way). When was the fix introduced? For Gutsy or is it going to be fixed in Intrepid?