NetworkManager Fails to Connect After Suspend

[Jai Singh]

Binary package hint: network-manager

When resuming from suspend in Feisty, NetworkManager will often fail to connect to any networks. I select the network, the icon changes appearing like it is trying to connect, and then it fails and reverts back to the the icon with the exclamation point. To solve this I have to restart dbus:

sudo /etc/init.d/dbus restart

and the I have to start gnome-power-manager (by entering that into the command line), but that is besides the point.

- Jai

[Jai Singh (i922sparkcir)]

Upon update today, I say a message to include this hardware submission id with all bug reports.

f3c411bb2df7600377a9090861ab083d

Hope it helps.

- Jai

[Darryl Clarke (dclarke)]

I'm experiencing the same issue with an up to date feisty

as described.

[Darryl Clarke (dclarke)]

As a solution for a user (telling them to manually run those commands isn't a good option) I've made up a little script with the help of some existing ones and my co-worker.

the script:

/etc/acpi/resume.d/89-fixstuff.sh

--
#!/bin/bash
# start acpi-support to re-enable suspend and stuff
/etc/init.d/acpi-support start

# Restart dbus to fix network manager breakage.
/etc/init.d/dbus restart

# For each user that is logged in we need to restart gnome-power-manager
# this is borrowed from 90-xscreensaver.sh
for x in /tmp/.X11-unix/*; do
    displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
    getXuser;
    if [ x"$XAUTHORITY" != x"" ]; then
        export DISPLAY=":$displaynum"
        su $user -c "(/usr/bin/gnome-power-manager)"
    fi
done

--
chmod +x /etc/acpi/resume.d/89-fixstuff.sh

and all should work.

I have no idea if this is specific to certain laptops, or if it is fixed in gutsy... but the above works for me in my current situation.

[Sergius Lezhnin (s-lezhnin)]

I didn't encounter this kind of problem in Feisty, but, after upgrade to Gutsy beta, I experience that bug as well. Exactly as described above.
My hardware is Dell Inspiron 6400.