dbus sleep/wake problem

[Dawid Wróbel <dawid klej net>]

Hi,
	It seems that nm 0.6.5 has a problem with waking up from sleep
mode. What I did was:

dbus-send --system
--dest=org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.sleep

and then:
dbus-send --system
--dest=org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.wake 

I can see in the syslog that it does wake up but doesn't connect again
to eth0, as it was connected before suspending. Nothing more
happens after the last line of this log excerpt:

May  2 18:38:15 kromka NetworkManager: <info>  Going to sleep.
May  2 18:38:15 kromka dhclient: There is already a pid file /var/run/dhclient-eth0.pid with pid 19337
May  2 18:38:15 kromka dhclient: killed old client process, removed PID file
May  2 18:38:15 kromka bridge-eth0: disabling the bridge
May  2 18:38:15 kromka bridge-eth0: down
May  2 18:38:15 kromka sudo:     root : TTY=unknown ; PWD=/ ; USER=cromo ; COMMAND=/usr/bin/claws-mail --offline
May  2 18:38:15 kromka dhclient: wifi0: unknown hardware address type 801
May  2 18:38:15 kromka dhclient: can't create /var/lib/dhclient/dhclient-eth0.leases: No such file or directory
May  2 18:38:15 kromka dhclient: wifi0: unknown hardware address type 801
May  2 18:38:20 kromka NetworkManager: <info>  Waking up from sleep.
May  2 18:38:20 kromka NetworkManager: <info>  Deactivating device ath0.
May  2 18:38:20 kromka NetworkManager: <info>  Deactivating device eth0.
May  2 18:38:20 kromka NetworkManager: <info>  ath0: Device is fully-supported using driver 'ath_pci'.
May  2 18:38:20 kromka NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
May  2 18:38:20 kromka NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
May  2 18:38:20 kromka NetworkManager: <info>  Now managing wireless (802.11) device 'ath0'.
May  2 18:38:20 kromka NetworkManager: <info>  Deactivating device ath0.
May  2 18:38:20 kromka bridge-eth0: enabling the bridge
May  2 18:38:20 kromka bridge-eth0: up
May  2 18:38:20 kromka NetworkManager: <info>  eth0: Device is fully-supported using driver 'tg3'.
May  2 18:38:20 kromka NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start
May  2 18:38:20 kromka NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing.
May  2 18:38:20 kromka NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'.
May  2 18:38:20 kromka NetworkManager: <info>  Deactivating device eth0.
May  2 18:38:22 kromka tg3: eth0: Link is up at 100 Mbps, full duplex.
May  2 18:38:22 kromka tg3: eth0: Flow control is on for TX and on for RX.
May  2 18:38:22 kromka NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.

After removing the cable and plugging again:
May  2 18:44:12 kromka tg3: eth0: Link is down.
May  2 18:44:17 kromka tg3: eth0: Link is up at 100 Mbps, full duplex.
May  2 18:44:17 kromka tg3: eth0: Flow control is on for TX and on for RX.
May  2 18:44:17 kromka NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.

And nothing more. I have to manually click on the eth0 interface name
from the list (in knetworkmanager) to force it to query dhcp server
and connect. 
It simply seems that autoconnecting after sleep/wake is broken.

-- 
Best regards
  Dawid Wróbel