package network-manager 0.6.5-0ubuntu17 failed to install/upgrade:

[Phil Norbeck]

Binary package hint: network-manager

Network-manager fails to upgrade when upgrading Ubuntu 7.10 to 8.04 alpha 1.

ProblemType: Package
Architecture: amd64
Date: Fri Nov 30 15:50:17 2007
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 2
Package: network-manager 0.6.5-0ubuntu17
PackageArchitecture: amd64
SourcePackage: network-manager
Title: package network-manager 0.6.5-0ubuntu17 failed to install/upgrade:
Uname: Linux phil-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux

[Kjell Braden (afflux)]

Thanks for taking your time to help making ubuntu better. Unfortunately, your report didn't include enough information for us to fix this bug. Could you please provide the output of the following command:

LC_ALL=C sudo apt-get install network-manager

Thanks

[Phil Norbeck (ptn107)]

The error first occurred during the distribution upgrade process. After the system rebooted, I opened a terminal and did a 'sudo apt-get upgrade' to attempt to install the network-manager again. It failed a second time for the same reason.

I noticed during the second attempt that package gnome-orca (gnome-orca_2.21.2-0ubuntu1_all.deb) was held back (this was not evident during the distribution upgrade process). I did a sudo apt-get install gnome-orca to force it to install. Apt-get downloaded and configured gnome-orca and THEN proceeded to install/configure network-manager. This time it was successful. The terminal output for the second attempt is such:

##BEGIN_DUMP
phil@phil-laptop:~$ sudo apt-get install gnome-orca
[sudo] password for phil:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  xf86dga libfaad2-0 beforelight ico xpmutils xgc bitmap
Use 'apt-get autoremove' to remove them.
Recommended packages:
  python-brlapi
The following packages will be REMOVED:
  python-orca-brlapi
The following packages will be upgraded:
  gnome-orca
1 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 436kB of archives.
After unpacking 336kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://us.archive.ubuntu.com hardy/main gnome-orca 2.21.2-0ubuntu1 [436kB]
Fetched 436kB in 1s (295kB/s)
dpkg: python-orca-brlapi: dependency problems, but removing anyway as you request:
 gnome-orca depends on python-orca-brlapi (>= 2.20.0-0ubuntu1).
(Reading database ... 90941 files and directories currently installed.)
Removing python-orca-brlapi ...
dpkg - warning: while removing python-orca-brlapi, directory `/usr/lib/python2.5/site-packages/orca' not empty so not removed.
(Reading database ... 90935 files and directories currently installed.)
Preparing to replace gnome-orca 2.20.0-0ubuntu1 (using .../gnome-orca_2.21.2-0ubuntu1_all.deb) ...
Unpacking replacement gnome-orca ...
Setting up network-manager (0.6.5-0ubuntu17) ...
 * Reloading system message bus config... [ OK ]
 * Restarting network connection manager NetworkManager [ OK ]
 * Restarting network events dispatcher NetworkManagerDispatcher [ OK ]

Setting up gnome-orca (2.21.2-0ubuntu1) ...
##END OUTPUT

[Phil Norbeck (ptn107)]

Well since the network-manager has installed after the third attempt, the output of LC_ALL=C sudo apt-get install network-manager is:

phil@phil-laptop:~$ LC_ALL=C sudo apt-get install network-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
network-manager is already the newest version.
The following packages were automatically installed and are no longer required:
  xf86dga libfaad2-0 beforelight ico xpmutils xgc bitmap
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
phil@phil-laptop:~$

Should I reinstall gutsy and try to upgrade again to reproduce the error before it was fixed?

[Kjell Braden (afflux)]

Phil, I guess you can't give the exact error message from the failing upgrade? If so, we could either close this bug or you could try to reproduce it, if you want.

[Phil Norbeck (ptn107)]

I'm going to try and reproduce it. What besides the terminal output would you need?

[Kjell Braden (afflux)]

Nothing, until we can locate the problem.

[Phil Norbeck (ptn107)]

Yep. Reproduced it exactly. The output of LC_ALL=C sudo apt-get install network-manager is below:

phil@ubuntu:~$ LC_ALL=C sudo apt-get install network-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
network-manager is already the newest version.
The following packages were automatically installed and are no longer required:
  xf86dga beforelight ico xpmutils xgc bitmap
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up network-manager (0.6.5-0ubuntu17) ...
 * Reloading system message bus config... [ OK ]
 * Restarting network connection manager NetworkManager [ OK ]
 * Restarting network events dispatcher NetworkManagerDispatcher [ OK ]

phil@ubuntu:~$

[Kjell Braden (afflux)]

Phil, the output you're providing only showed that it got installed cleanly. However, We ideally need the initial failure message.

[Kjell Braden (afflux)]

You can maybe obtain it from /var/log/apt/term.log.

[Phil Norbeck (ptn107)]

I dug through the /var/log/apt/term.log file and found this:

Setting up network-manager (0.6.5-0ubuntu17) ...

 * Reloading system message bus config... 
[ OK ]

 * Restarting network connection manager NetworkManager  dpkg: error processing network-manager (--configure):

 subprocess post-installation script returned error exit status 2

Thats all.

The full term.log is attached.

[Tab (jason-rubixnet)]

i am having the same issue since the last update on 12/5/2007.
Here is my term.log

I too see a unresponsive system when running this command.
LC_ALL=C sudo apt-get install network-manager

[Chris Malton (chrism-cjsoftuk)]

I personally think the priority of this bug should be increased.

It leaves me with a completely dead system and I have to power cycle to go anywhere.

I accidentally duped this bug at https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/174093

[Phil Norbeck (ptn107)]

I agree and believe the importance should be higher. It too made my system unresponsive at one point which required a cold boot to fix it.

[Pedro Villavicencio (pedro)]

In order to have more info, could you please add all the files contained in /var/log/dist-upgrade/ to your bug report as separate attachments? Thanks in advance.

[Phil Norbeck (ptn107)]

files from /var/log/dist-upgrade/ attached.

[derwiki (derewecki)]

I agree that this severity should be increased. Everytime I run `sudo apt-get install network-manager`, my system displays:

 * Restarting network connection manager NetworkManager
dpkg: error processing network-manager (--configure):
 subprocess post-installation script returned error exit status 2

My system hangs after that and I have to manually reboot. I'm just running Gutsy, I'm not trying to upgrade to the newest distribution.

[Tab (jason-rubixnet)]

I also want to note I was NOT doing an upgrade just a regular update with update manager when this problem cropped up. I am running Gutsy 7.10.

[Phil Norbeck (ptn107)]

Please attach your logs from /var/log/dist-upgrade/ That will help them out.

[DaMoisture (hckrmagoo)]

I too have the same problem whenever I try to install or update *any* package, using both apt-get or Synaptic. The result is the same error and an unresponsive system that needs a hard reboot. I'm running Gutsy with Gnome, not trying to update to 8.04.

[DaMoisture (hckrmagoo)]

And now that I think about it some more, I believe the first time the problem happened, I was able to shutdown the system properly. The system was responsive: however, there was no network functionality. That was the only time the system has recovered from the error. I don't know if it was because I ran the updater and them went to work (so it was able to sit all day and figure itself out), or is that it was just a fluke. For the record, I have no files in my /var/log/dist-upgrade/ directory. I'm kind of new to this whole thing, so let me know if there is anything else I can do to help get this bug resolved.

[Kjell Braden (afflux)]

I'll set this bug to triaged, as Phil Norbeck provided the requested files.

DaMoisture, please note that the symptoms you're reporting possibly have nothing to do with this bug and so should be reported as different bugs. This one is only about the failing upgrades.

[DaMoisture (hckrmagoo)]

Going back to my term.log, I see my network-manager package was to be upgraded on 2007-12-04. From the log:

Log started: 2007-12-04 16:36:13
(Reading database ... 105144 files and directories currently installed.)

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

Unpacking replacement network-manager ...
...
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

...
ldconfig deferred processing now taking place

Errors were encountered while processing:

 network-manager

Log ended: 2007-12-04 16:39:10

There has been an error that repeats itself every time I run Synaptic, Update Manger, or apt-get since the above update:

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

I'm running the AMD64 version, if that helps at all.

[Tab (jason-rubixnet)]

If this is not the right place for this bug where should it be?

I have this problem after applying updates on Dec 5.

I was not upgrading to 8.04 this was standard update of network-manager on 7.10 gutsy. I also see the same behavior when just restarting the network-manager services.

The services do not restart and the system becomes unresponsive after executing:

sudo /etc/init.d/network-manager restart

[DaMoisture (hckrmagoo)]

I got an error message yesterday when I started synaptic. I don't remember exactly what it said, but it was to the effect of: "there has been a problem with a package. Please run dpkg --configure -a" I ran that command (with sudo, of course) and now everything seems to be fine. The next entry in my term.log has no mention of network manager in it at all, and I can run synaptic and apt-get with no problems.

[Tab (jason-rubixnet)]

Awsome that did it but I did have to run dpkg-reconfigure -a in recovery mode.

[derwiki (derewecki)]

I tried `sudo dpkg --configure -a` and `dpkg-reconfigure -a` from recovery mode, and the problem is still exactly the same as it was before.

[mabovo (mabovo)]

I have upgraded nm-0.6.5 to nm-0.7 and downgraded it again to the original configuration of nm-0.6.5 just to check if some garbage wasn't migrated to the nm-0.7 installation. Now I am "testing" nm-0.7 without problem (wired connection).
The process I did was to download all network-manager deb packs from the repos with their dependent libs.
Also I removed all instances of wlan0, eth0 or ath0 in the /etc/network/interfaces and also removed wpasupplicant.conf file from /etc/wpasupplicant/.
Using dpkg I could reinstall network-manager and restore it to a previous working environment.