Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

[mechanism]

I used Adept to try to upgrade from 7.04 to 7.10. Soon after the installation begin, I received a message that some third party sources were deactivated in my sources list but I could enable them again after the installation. Okay. No problem.

The installation seemed to be going smoothly enough but after about the third step of the installation I received the following error message:

"Could not install "debconf" - the upgrade will continue but the "deb conf" package may not be in a working state. Please consider submitting a bug report about it. [subprocess post-installation script killed by signal (segmentation fault), core dumped."

A few seconds later - another error message along the same lines:

"Could not install /var/cache/apt/archives/x11-common_1%3a7.2-5ubuntu13-i386.deb."

A few more messages like that one appeared. Then, the whole download seem to freeze at 2%. It said it was "preparing liborbit2-dev" and that there were 5 hrs and 51 minutes remaining. After 1 hour, it was still at 2% completion with the same status.

So, fearing the worst, I canceled the upgrade. Now I am afraid to reboot my machine. I know Adept downloaded about 700 megs of files but I do not believe they were installed.

What should I do?

M

[integr8e]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

OK, this should be a simple fix:

Click this link to go to the 'Ubuntu sources.list Generator'. Fill in all the information, and check all the boxes for the repos you want (be sure to select the option for the Gutsy repos). Click the "Submit" button, which should generate a list of Gutsy repos; then, open /etc/apt/sources.list as root (kdesudo kate /etc/apt/sources.list), and replace everything in the file with the Gutsy repos you generated. Simply update your computer, reboot if you don't run into errors, and you should be running Gutsy!

Note: I've done this several times, and it has always worked for me. If you run into issues, remember the commands "sudo dpkg --configure -a" and "sudo apt-get install -f"; should those not fix the problem, let me know and I'll do my best to help

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Thanks for the reply! Now, is this for completing the upgrade to Gutsy or for restoring Fiesty the way I had it?

I did remember to save my sources.list to my thumb drive before attempting to upgrade.

m

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Oh crap! Never mind my last post. I re-read your post again and understand that I should be running Gutsy when I'm done. :P

It's been a long day!

I do have a question - should I make the above changes you listed and attempt another upgrade (on top of the files that were downloaded in the failed upgrade) before I reboot. I'm just afraid that rebooting will hose my system.

[integr8e]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Yes . . . when you update your computer, it will only upgrade what has not already been upgraded. If you reboot now, you may wind up with a broken system - then the fun really begins

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Yes . . . when you update your computer, it will only upgrade what has not already been upgraded. If you reboot now, you may wind up with a broken system - then the fun really begins

I launched Adept and received the below message;

You will not be able to change your system settings in any way (install, remove or upgrade software), because another process is using the packaging system database (probably some other Adept application or apt-get or aptitude). Please close the other application before using this one.

I am not using Adept in any other application right now. I suppose it is hung up due to the crash/me stopping the update. Is there a way to kill Adept without rebooting?

Also, should I do an update using Adept or the command line. If by command line, then what commands do I type?

Thanks.

M

[integr8e]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

I would suggest just using the command line. To unlock your system, try running the command:

sudo dpkg --configure -a

Then, update with the command

sudo aptitude update

If you receive the error:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
E: Couldn't rebuild package cache

and you don't have any other package managers running, delete "/var/lib/dpkg/lock" with the command

sudo rm /var/lib/dpkg/lock

That will "unlock" your system and allow you to continue with the update. Then, run the following commands to finish the upgrade:

sudo aptitude update && sudo aptitude full-upgrade

sudo dpkg --configure -a && sudo apt-get install -f

sudo aptitude clean && sudo aptitude autoclean

If successful, reboot and you should be good to go!

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Okay. Got it.

I'm going in. If I don't make it back, tell my wife and kids that I love them.

m

[Beren Camlost]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

I'm going in. If I don't make it back, tell my wife and kids that I love them.

That's the spirit!

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

I would suggest just using the command line. To unlock your system, try running the command:

sudo dpkg --configure -a

Then, update with the command

sudo aptitude update

If you receive the error:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
E: Couldn't rebuild package cache

and you don't have any other package managers running, delete "/var/lib/dpkg/lock" with the command

sudo rm /var/lib/dpkg/lock

That will "unlock" your system and allow you to continue with the update. Then, run the following commands to finish the upgrade:

sudo aptitude update && sudo aptitude full-upgrade

sudo dpkg --configure -a && sudo apt-get install -f

sudo aptitude clean && sudo aptitude autoclean

If successful, reboot and you should be good to go!

Okay - see the below hash

mrmsudawgs@closet:~$ sudo dpkg --configure -a
Setting up debconf (1.5.14ubuntu1) ...

Setting up libart-2.0-2 (2.3.19-3) ...

Setting up linux-libc-dev (2.6.22-14.47) ...
dpkg: dependency problems prevent configuration of gwenview:
gwenview depends on kdelibs4c2a (>= 4:3.5.7-1); however:
Version of kdelibs4c2a on system is 4:3.5.6-0ubuntu14.1.
gwenview depends on libexiv2-0; however:
Package libexiv2-0 is not installed.
gwenview depends on libstdc++6 (>= 4.2-20070516); however:
Version of libstdc++6 on system is 4.1.2-0ubuntu4.
dpkg: error processing gwenview (--configure):
dependency problems - leaving unconfigured
Setting up libasound2 (1.0.14-1ubuntu8) ...
You may need to execute the asoundconf(1) set-default-card macro.

Setting up libperl5.8 (5.8.8-7ubuntu3.1) ...

Setting up mcpp (2.6.4-1ubuntu2) ...
Setting up libdb4.4 (4.4.20-8.1ubuntu3.1) ...
Setting up x11-common (7.2-0ubuntu11) ...

dpkg: dependency problems prevent configuration of digikam:
digikam depends on kdelibs4c2a (>= 4:3.5.7-1); however:
Version of kdelibs4c2a on system is 4:3.5.6-0ubuntu14.1.
digikam depends on libexiv2-0; however:
Package libexiv2-0 is not installed.
digikam depends on libfreetype6 (>= 2.3.5); however:
Version of libfreetype6 on system is 2.2.1-5ubuntu1.1.
digikam depends on libgphoto2-2 (>= 2.4.0); however:
Version of libgphoto2-2 on system is 2.3.0-0ubuntu4.
digikam depends on libgphoto2-port0 (>= 2.4.0); however:
Version of libgphoto2-port0 on system is 2.3.0-0ubuntu4.
digikam depends on libjasper1 (>= 1.900.1); however:
Package libjasper1 is not installed.
digikam depends on libkdcraw1; however:
Package libkdcraw1 is not installed.
digikam depends on libkexiv2-1; however:
Package libkexiv2-1 is not installed.
digikam depends on libltdl3 (>= 1.5.2-2); however:
Package libltdl3 is not installed.
digikam depends on libsqlite3-0 (>= 3.4.2); however:
Version of libsqlite3-0 on system is 3.3.13-0ubuntu1.
digikam depends on libstdc++6 (>= 4.2.1); however:
Version of libstdc++6 on system is 4.1.2-0ubuntu4.
digikam depends on zlib1g (>= 1:1.2.3.3.dfsg-1); however:
Version of zlib1g on system is 1:1.2.3-13ubuntu4.
dpkg: error processing digikam (--configure):
dependency problems - leaving unconfigured

Errors were encountered while processing:
gwenview
digikam



Not knowing what qwenview was nor being to concerned if I lost digicam, I decided to continue with sudo aptitude update. All went well but I received a strange message stating

"This aptitude does not have Super Cow Powers"

All seemed to have updated and no actual errors were listed after the update so I continued with the following and received errors again about digicam and qwenview. Then everything just stopped.

mrmsudawgs@closet:~$ sudo dpkg --configure -a && sudo apt-get install -f
dpkg: dependency problems prevent configuration of gwenview:
gwenview depends on kdelibs4c2a (>= 4:3.5.7-1); however:
Version of kdelibs4c2a on system is 4:3.5.6-0ubuntu14.1.
gwenview depends on libexiv2-0; however:
Package libexiv2-0 is not installed.
gwenview depends on libstdc++6 (>= 4.2-20070516); however:
Version of libstdc++6 on system is 4.1.2-0ubuntu4.
dpkg: error processing gwenview (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of digikam:
digikam depends on kdelibs4c2a (>= 4:3.5.7-1); however:
Version of kdelibs4c2a on system is 4:3.5.6-0ubuntu14.1.
digikam depends on libexiv2-0; however:
Package libexiv2-0 is not installed.
digikam depends on libfreetype6 (>= 2.3.5); however:
Version of libfreetype6 on system is 2.2.1-5ubuntu1.1.
digikam depends on libgphoto2-2 (>= 2.4.0); however:
Version of libgphoto2-2 on system is 2.3.0-0ubuntu4.
digikam depends on libgphoto2-port0 (>= 2.4.0); however:
Version of libgphoto2-port0 on system is 2.3.0-0ubuntu4.
digikam depends on libjasper1 (>= 1.900.1); however:
Package libjasper1 is not installed.
digikam depends on libkdcraw1; however:
Package libkdcraw1 is not installed.
digikam depends on libkexiv2-1; however:
Package libkexiv2-1 is not installed.
digikam depends on libltdl3 (>= 1.5.2-2); however:
Package libltdl3 is not installed.
digikam depends on libsqlite3-0 (>= 3.4.2); however:
Version of libsqlite3-0 on system is 3.3.13-0ubuntu1.
digikam depends on libstdc++6 (>= 4.2.1); however:
Version of libstdc++6 on system is 4.1.2-0ubuntu4.
digikam depends on zlib1g (>= 1:1.2.3.3.dfsg-1); however:
Version of zlib1g on system is 1:1.2.3-13ubuntu4.
dpkg: error processing digikam (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
gwenview
digikam
mrmsudawgs@closet:~$



I would be happy to just uninstall these two programs if that would work. I sure hope you can pull me through this. Thanks!!!

[integr8e]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Gwenview and Digicam are just image viewing/basic manipulation programs, you can delete them without harm; the command "sudo apt-get install -f" should resolve the dependencies problem (i.e. install what they need), which you can run if you want to try to fix the packages. Either method will be fine (you can delete them now and reinstall them later if you want).

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Ok...making some progress here. I typed in

sudo dpkg --configure -a && sudo apt-get install -f


and received this

mrmsudawgs@closet:~$ sudo dpkg --configure -a && sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libglib-perl libdc1394-13 libxvidcore4 libssl-dev libgsm1 liblzo-dev
libcairo-perl libidn11-dev liba52-0.7.4
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 921 not upgraded.
mrmsudawgs@closet:~$

Does 0 upgraded, 0 newly installed, 0 to remove and 921 not upgrade imply that nothing happened and I need to repair something else? The entire routine only took about eight or ten seconds. Should I proceed with the final step which is

sudo aptitude clean && sudo aptitude autoclean ?

Mike

[dibl]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

I would interpret that message as "everything is good to go". Yes, you can proceed with the last command to "clean" and "autoclean" and your system should be fine.

The 921 not upgraded is a bit of a concern -- only because it seems like there was a problem with a prior update. You could try running

sudo apt-get update && sudo apt-get install

again (I wouldn't use the -f to force it this time) and see what you get.

[mechanism]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Okay...I completed the above steps, rebooted, then noticed that my Adept icon was indicating that an update was available. Launched Adept and about 900 files were available for update (possibly those same files that were being downloaded when Adept crashed the first time - see first post in this thread).

So, I allowed Adept to make the update. About an hour into the update I received a few messages about "Pam" and that I would have to do something mannually to it. Not sure what it meant but was able to select "Next" and the download continued. About 1 hour later, all the downloading had been completed and Adept begin to install what it had downloaded.

Soon after, I received this message:

"Could not commit changes. There was an error commiting changes. Possibly there was a problem downloading packages or the commit would break packages."

The only option Adept gave me was "OK". I selected it and Adept popped up a message saying "Update Complete".

So...am I done? Am I now running 7.10 or am I stuck somewhere in between 7.04 and 7.10? I'm not rebooting again until I'm sure the downloading / installation was actually completed.

Thanks!

Mike

[Snowhog]

Re: Upgrade From 7.04 to 7.10 Failed - Scared To Reboot!

Understand your concern. But, I believe you are okay, and you do need to perform a normal shutdown/restart. When you are back on your desktop, reopen Adept Manager and Fetch Updates again. I believe that Adept Manager needs to go through a second 'cycle' in a Feisty to Gutsy upgrade.