Ubuntu Networking :: Hang On Reboot When Connected To NFS/ldap Server Via Wireless

School with linux running on students' laptops, connecting via wlan to a Debian NFS and LDAP server. Every student logs on his/her profile residing on the NFS server.The clients are set up with autofs. Earlier, I had set up the wireless network in /etc/network/interfaces, but this time I decided to configure network manager so as to bring up both wireless and wired network before logon. This setup has been working on for the last fire or five years with only minor changes. Also worked with Karmic Koala, but still with the interfaces file instead of networkmanager. The Vostro is also new here, we've previously used mostly Dell Latitude D505s.

So here is what works:

1: Clients can log on to LDAP and NFS servers both wired and wirelessly. Everything is smooth.

2: While on LAN, shutdown and restart works flawlessly (and quick as a breeze, I'm really impressed by startup/restart/shutdown times, under 25 secs!).

3: Shutdown and restart also works wirelessly when doing it either from a local account or from the GDM chooser.

What doesn't work, however, is shutting down or restarting directly from a networked account connected while only being connected over the wireless network. This is what's being displayed on the terminal after it has tried tho shut down for a while:

Code:

The system is going down for halt NOW!

acpid: exiting
init: cron main process (1011) killed by TERM signal.
init: tty1 main process (1365) killed by TERM signal.

[code]...

If I try ctrl-alt-del at this stage, it says:

"init: rc main process (3030) killed by TERM signal"

"Checking for running unattended-upgrades: "

And then it will hang again, until I hold the powerbutton for some seconds. The unattended-upgrades part is what seems to be the culprit. I suspect it is about the wireless network not being connected any longer or something like that, but I'm not sure about how to go about debugging shutdown scripts here. I'd be grateful for pointers. I will try and see how it goes with the old interfaces file setup, but I'd rather make nm work.