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. -- [Intrepid] Shutdown is blocked since last update of network manager. https://bugs.launchpad.net/bugs/286308 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
