Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I was trying to upgrade my Lenovo T500 laptop from Kubuntu 12.04 LTS to Kubuntu 14.04 LTS.

Fired up the upgrade process, and finally after downloading a zillion packages the upgrade got going, only to get stuck...

It has been stuck for hours on:

 Installing the upgrades->Unpacking subversion

Last lines of error messages:

GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.

GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.

I don't care much about subversion anymore, I use git now; I don't care if subversion ends up in a bad state and I have to remove it...

I just want the upgrade to continue, and hopefully complete.

Any ideas????

Thanks,

Luis

share|improve this question
    
try uninstalling subversion and restarting installation? (I'm assuming it errored out after that?) –  hamhut1066 Apr 23 at 17:28
    
I am afraid of leaving the system in a really unstable state if I kill the upgrade outright, but yes, that might be the only option. –  Luis Apr 23 at 17:53
    
I tried installing using an upgrade, but it just died on me, I ended up re-installing. If you have a seperate home partition it should be a piece of cake, just create a live cd/usb before rebooting –  hamhut1066 Apr 23 at 17:56
3  
@hamhut1066 Ubuntu preserves the data in /home with a fresh install, it does not matter if /home is on a separate partition or not. This has been the behavior for Ubuntu for 6 + years. "Since Hardy it is possible to reinstall Ubuntu without losing the content of the /home folder (the folder that contains program settings, internet bookmarks, emails and all your documents, music, videos and other user files). This can be done even if /home is not on a separate partition " help.ubuntu.com/community/UbuntuReinstallation –  bodhi.zazen Apr 23 at 18:00
    
If you have problems with an upgrade, it is almost always easier and faster to do a fresh install. You should already have your data backed up ;) –  bodhi.zazen Apr 23 at 18:01

2 Answers 2

I had this problem as well but I figured out a way around it.

After the upgrade has stalled look for the process called "frontend" in the process tree of "python->sudo->trusty->trusty->...->...->frontend" that the upgrade-manager is running under. Once you kill this sub-process the installation process will start again and complete cleanly.

This is related to something involving updating of the man-db. It is not related to subversion, or python, or whatever was being unpacked. That was just the last bit in the logs. The problem is something related to man-db and (probably) perl.

Recommending a fresh install as a first course of action is not exactly helpful. That's what you do when problem solving fails. It isn't a solution.

share|improve this answer
    
This sounds totally legit, the problem for me was that it wouldn't allow me to open a terminal to look for the process and kill it. Not via the menu, not via CTRL ALT T, so I ended up restarting. It's now not booting, so it's going to be another fresh install to a new hd, along with setting everything up yet again. Goddamit, this is why it still isn't the year of the desktop... –  Fluffeh Sep 2 at 10:44
    
If you're ever in that situation again try switching to a text console with Ctrl+Alt+F6. To switch back to the X desktop press Ctrl+Alt+F7. –  superkuh Sep 6 at 7:03
    
@superkuh Thanks you helped me. I did the same thing but on my Xubuntu but the keys were atl + ctrl + f1 and alt + ctrl + f3. I recommend you put this peice of advice in your answer as comments can be deleted at any time. –  James Khoury Sep 24 at 8:52

I hit this exact problem doing an upgrade from 12.04 -> 14.04. I was unable to kill the frontend process as described above, because although I could launch an Xterm window, sudo and su segfaulted due to the system being half-upgraded.

However, I recovered from the situation by rebooting, going into recovery mode, and getting it to fix broken packages. This effectively restarted the upgrade process in command line mode and I ended up (eventually) with a usable 14.04 system.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.