[Intrepid] Shutdown is blocked since last update of network manager.

[FredBezies]

Binary package hint: network-manager

Since last update of network manager, it is impossible to get a clean shutdown. In the first time, I thought I was facing bug #274995, but the workaround proposed (shutting down connection before asking for full shutdown) doesn't work for me.

I took a screenshot - splash screen disabled - and I saw this message :

nm-dispatcher.action : Caught signal 15, shutdown.

I will attach part of syslog related to a classic shutdown try (without closing connection before) and a "custom" one.

And my lspci log.

[FredBezies (fredbezies-deactivatedaccount)]

Forget to add that I had to press a key to get shutdown complete.

[Brion Swanson (brions)]

Pressing any key continued the shutdown? I have a similar issue in that I can neither shutdown or restart without an interminable hang. Pressing keys does not seem to make it do anything.

Like you Fred I have an Intel HDA sound card (on-board) using the snd_hda_intel driver and Compiz for what it's worth.

I've been following several other bugs including bug #274995 but nothing seems to be helping in my case. I even grabbed the latest intrepid-proposed kernel (2.6.27-8-generic) that is supposed to have some kernel patches for the snd_hda_intel drivers but I have not yet seen a difference.

[FredBezies (fredbezies-deactivatedaccount)]

Well, my problem is that acpid is blocked in some ways. I also noticed that the leds above my ethernet plug are blinking a lot on shutdown, just after end screen scrollbar is emptied.

Annoying to say the least.

[Brion Swanson (brions)]

There is another bug created by me (bug #302452) which may be a duplicate of this one or vice versa. If your computer actually shuts down after some period of time or by pressing a key, then it is a different bug.

[FredBezies (fredbezies-deactivatedaccount)]

For your info, I have enabled intrepid-proposed repository.

Packages version :

linux-image : 2.6.27.10.13
apcid : 1.0.6-9ubuntu4

Please tell me which log could be useful to help fixing this bug.

[FredBezies (fredbezies-deactivatedaccount)]

Sorry for not marking it as a duplicate of your bug. Real life was upon me ;)

[Brion Swanson (brions)]

Fred, did you ever find a resolution for this bug?

Look at bug #388291 - that is a true duplicate of my reported bug but with better detail I think. I've removed the duplicate marker of this bug to bug #302452 so I can mark that one a duplicate of 388291.

I think I may have found the solution to my problem. Do you have any network mounts in a nested folder directory?

Put another way, do you have network mounts such as: /mnt/mount1/mount2 where mount1 and mount2 are two different network mounts? If so, try mounting mount1 and mount2 in sibling folders such that if you type 'sudo umount /mnt/*' it succeeds.

That solved my problem since mount1 was listed in /etc/fstab before mount2 in order to get them to "nest" properly, but when unmounting it tries to umount mount1 first and fails because it's busy since mount2 is still mounted. Then it moves on to umount mount2 which succeeds but it never comes back to try mount1 again and the shutdown/reboot is hung waiting for all mounts to be unmounted.

[Alexander Sack (asac)]

i think this bug should be better now in karmic after upstart migration. Also NM does not tear down wired on shutdown anymore.

[Alexander Sack (asac)]

actually i think its fixed.