network manager prints errors to console during shutdown

[Martin Olsson]

I'm seeing several assert statements in network manager that fail when I shutdown my Ubuntu machine.
The errors I'm seeing are the following ones:
1. When the function nm_hal_deinit() is called, the libhal shutdown fails.
2. When the function nm_dbus_signal_device_status() is called, the following assert statement is not fulfilled:
cb_data->data->dbus_connection

There is also a message being printed saying that I should "make sure that message bus daemon is running". So, I'm guessing someone made some false assumptions about the order in which different daemons shut down, maybe?

I've attached a photo of the exact error text I see. These errors show up every single time I restart or shutdown Ubuntu hardy.

[Martin Olsson (mnemo)]

In case this error repros on just my NIC; I'm attaching the output of "lspci" and "lspci -n" from this machine which is a HP Pavillion DV6000 laptop with a Intel network card.

[LEVIS Cyril (atlas95)]

I have the same problem since a long time... I have a m1330 wifi abgn wlan card.

[elephantcrossing (david-schwaerzler)]

same thing happening here.

but i think it's not just related to the shutdown process. since i can already see some network-manager related error messages if i change to F1 right after entering my password at the gdm screen. but other than that network-manager works great.

[Martin Olsson (mnemo)]

I tried to watch CTRL-ALT-F1 right after the gdm logon but I saw only a black screen (maybe this is because my intel x.org driver has problems with virtual terminals, not sure). Also during my normal ubuntu usage, if I switch to CTRL-ALT-F1 then I see the normal console output there and I don't see any failing asserts at that point.

[elephantcrossing (david-schwaerzler)]

I only get some output talking about network-manager if I switch to the virtual terminal right after gdm logon. here's a picture of what i am talking about (at least the part i was able to take a picture of)

[[e-mail] (dakshay-deactivatedaccount)]

Exact same issue here too

[pixolex (pixolex)]

Just to confirm the bug.

I think this bug report is duplicated of #205482.

I have a ASUS W5F

lspci

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
07:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
08:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
08:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
08:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
08:03.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
08:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

[JPBoyer (jp-boyer)]

I have exactly the same problem, and have been looking everywhere for some light to no avail.
What's "funny" is that my machine is a desktop, with wired LAN. So I guess nothing to do with WiFi...
I am on fully updated Hardy Heron updated from Gutsy.
While some people seem to experience also a complete hang-up of the machine (never shuts down after showing the same blurb on the screen), mine does shut down as described in subject of this bug.
Very similar (well... identical except fo rthe "hang-up") to bug #138691 (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/138691)

[Prinknash (colin-colinandjenny)]

I take no credit for this - I read it on one of the Ubuntu forums - but it solved this problem on both my Dell machines that were suffering from it.

1. Go to System - Administration - Login Window.

2. Under 'General', press "Edit commands ...'

3. Select 'Halt command' - in 'Path' box, cut the text in quotes (I.e. "Shut down via gdm") - press "Apply command change" - paste the text back - press 'Apply command change'

4. Select 'Reboot command' and do as for 3. above

Try restarting a couple of times and see if this has fixed the problem. It seems to have done so for a number of people, including me - although I wouldn't care to have to explain exactly how it's fixed the problem!

[piero (piero-fr)]

It didn't fix my problem. My PC do not shutdown and freeze on the last screen (with a lot of error on network-manager)

see details on my post her
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/205482/comments/8

Do all those bugs have same causes ? (most look like can shutdown)
Bug #205482
Bug #216870
and maybe some of these
Bug #44874
Bug #138691
Bug #138794
Bug #161945
Bug #190312
Bug #200622

[Prinknash (colin-colinandjenny)]

I think it's a solution for some or all of the people whose machines DO shutdown but after a long pause and a screen full of Network Manager error messages. (And I assume it's a 'solution' only in the sense that it stops the error messages being displayed.) It isn't going to make shutdown possible when it wasn't before - but that's a different bug, isn't it?

[piero (piero-fr)]

Hi Prinknash,

I've found a solution for me adding acpi=force in the /boot/grub/menu.lst. it's explain (mix French and English !) by darkshado her
http://forum.ubuntu-fr.org/viewtopic.php?pid=1632610#p1632610

I'm afraid that is a old problem of my computer (I've post on launchpad) and probably a different bug
Bug #43961

sorry by mixing too different bug

good luck and thanks

[Peter de Kraker (peterdekraker)]

Pfff this bug is irritating me for at least a year or so? Gutsy had it always too and it didn't change with hardy.

On every PC I have Ubuntu installed I get those errors. I disabled the splashscreen, so I always see it when I shutdown. but note: my shutdown process is not slow or has problems. It only shows these messages.

Main PC has only a NIC, the others have WIFI.

Please let me know what information is needed, I really really like this bug to dissappear.

[JPBoyer (jp-boyer)]

There're quite a few solutions (though it seems that they do not always work for everybody) to by-pass the bug on the forum at http://ubuntuforums.org/showthread.php?s=30c564a89609f40a161cf027fc469262&p=4891868#post4891868
For info, since I did these, I have not had these message about network manager anymore at all. And in fact, I have changed... nothing. Just played a bit with the commands in the Login Window menu by deleting the sentence into brackets" AND putting them back again (i.e. = no change, except the date of the file?), and it works fine.

[Michael Monreal (mimox)]

Really irritating, I hope this will be resolved soon. My system shuts down in normal time but displays PAGES of errors before that.

[Michael Monreal (mimox)]

I installed Hardy on a VM now and this is what I get there... less lines, but still the DBus issue for example.

[Michael Monreal (mimox)]

The above screenshot was taken with "nosplash" btw. If booted with "splash" I don't see any console messages but the shutdown clearly stops for a few seconds (and the shutdown bar stops during this time).

[garythornton1956 (gary-scdynamics-eu)]

It happens for me too on all 4 machine where I run Ubuntu 8.04. These are a Thinkpad T61p with wireless, a Dell D51 laptop with wireless, a Fujitsu Scaleo desktop without wireless and an Acer FG without wireless. it looks untidy bur the machines all shut down. I suspected it might be the order that the services are stopped in rc.d but haven't bothered toi investigate.

[garythornton1956 (gary-scdynamics-eu)]

I've tried the solution posted by Prinknash and it seems to have worked on my Thinkpad. On my Dell D510 it crashed gdm but worked after a reboot. It hasn't worked on the Acer or Fujitsu though.

[exactt (giesbert)]

setting to confirmed due to the many reports and me experiencing the bug as well.

[Percy Leonhardt (p3y)]

Maybe this is already known or obvious, but I just wanted to add it: I only get this behavior (error messages from NM and a delayed splash screen) when shutting down using Gnome Power Manager - I mapped my powerbutton to "shutdown" - and when I press it it shows the described behavior. When shutting down via System / Quit I don't see the error messages and the splash screen comes immediately. The described changes to the GDM settings did not resolve the problem for me...

[Alexander Sack (asac)]

this is indeed an issue and also in NM 0.7 the case (though the messages are different).

[Harrison Neal (hantwister)]

Not that you all want to hear more of this, but this affects a Dell Inspiron 7000 Laptop running Xubuntu 8.04.1 with a TrendNet TU2-ET100 USB Ethernet Adapter (using the "asix" kernel module).

[Alexander Sack (asac)]

fix committed by rev 2927 on lp:~network-manager/network-manager/ubuntu.0.7 branch

[Pablo Castellano (pablocastellano)]

It's fixed! :)

[Mike (mikedorries)]

I found the fix, however, I don't exactly understand how to fix it. It states the files that need changed but I can't find where they are located and what exactly needs changed.