[gutsy] network-manager fails upgrade on gutsy with error code 2

Bug #174093 reported by Chris Malton
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

While performing a standard upgrade from Update Manager, the following happened (without the other stuff that got upgraded):

*** START
(Reading database ... 118140 files and directories currently installed.)

Preparing to replace libnm-glib0 0.6.5-0ubuntu16 (using .../libnm-glib0_0.6.5-0ubuntu16.7.10.0_i386.deb) ...

Unpacking replacement libnm-glib0 ...

Preparing to replace libnm-util0 0.6.5-0ubuntu16 (using .../libnm-util0_0.6.5-0ubuntu16.7.10.0_i386.deb) ...

Unpacking replacement libnm-util0 ...

Preparing to replace network-manager 0.6.5-0ubuntu16 (using .../network-manager_0.6.5-0ubuntu16.7.10.0_i386.deb) ...

Unpacking replacement network-manager ...

Setting up libnm-glib0 (0.6.5-0ubuntu16.7.10.0) ...

Setting up libnm-util0 (0.6.5-0ubuntu16.7.10.0) ...

Setting up network-manager (0.6.5-0ubuntu16.7.10.0) ...

 * Reloading system message bus config...

   ...done.

 * Restarting network connection manager NetworkManager

dpkg: error processing network-manager (--configure):

 subprocess post-installation script returned error exit status 2

Processing triggers for libc6 ...

ldconfig deferred processing now taking place

Errors were encountered while processing:

 network-manager

*** END

At this point, Firefox is no longer able to access the web, I can't launch gnome terminal, and the machine cannot be shut down because it hangs disabling network devices.

Revision history for this message
Chris Malton (chrism-cjsoftuk) wrote :
Revision history for this message
Chris Malton (chrism-cjsoftuk) wrote :

This all happened this morning (5 Dec 07) about 10 minutes after I powered on.

Revision history for this message
Kjell Braden (afflux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 173132, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.