After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673682 - NetworkManager-0.9.4.0 fails to dispatch "up" events for wireless connections when waking from sleep
NetworkManager-0.9.4.0 fails to dispatch "up" events for wireless connections...
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: conn-dependency
 
 
Reported: 2012-04-07 08:17 UTC by Alexandre Rostovtsev
Modified: 2014-05-05 22:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
level=INFO log (22.54 KB, text/plain)
2012-04-07 08:17 UTC, Alexandre Rostovtsev
Details

Description Alexandre Rostovtsev 2012-04-07 08:17:48 UTC
Created attachment 211531 [details]
level=INFO log

NetworkManager-0.9.2.0 does not dispatch down events when sleeping and up or hostname events after waking up for wifi connections. It *does* dispatch events correctly for wired ethernet connections, or after having previously successfully dispatched an "up" event for an ethernet connection on wakeup.

This is a regression; NetworkManager-0.9.2.0 had always dispatched events correctly for both wired and wireless connections.

To reproduce:

Create the following executable /etc/NetworkManager/dispatcher.d/00-test

#!/bin/sh
echo >> /tmp/dispatcher-test.txt
echo $(date) >> /tmp/dispatcher-test.txt
echo $@ >> /tmp/dispatcher-test.txt
nmcli nm >> /tmp/dispatcher-test.txt
nmcli dev >> /tmp/dispatcher-test.txt

Then restart NetworkManager with the ethernet cable unplugged.

Run
gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep true
gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep false

And /tmp/dispatcher-test.txt will contain

Sat Apr 7 04:02:58 EDT 2012
wlan0 up
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         disabled  
DEVICE     TYPE              STATE        
wlan0      802-11-wireless   connected    
eth0       802-3-ethernet    unavailable   

Sat Apr 7 04:05:41 EDT 2012
wlan0 down
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         asleep          enabled         enabled    enabled         disabled  
DEVICE     TYPE              STATE        
wlan0      802-11-wireless   unmanaged    
eth0       802-3-ethernet    unmanaged    

Note that there is an "up" event for NetworkManager starting, a "down" event for the call to sleep, but no "up" event for waking up from sleep.

The level=INFO NetworkManager log for the above is attached.

Note that the same sequence of actions with an ethernet cable plugged in initially will correctly dispatch an "up" event on wakeup.
Comment 1 Alexandre Rostovtsev 2012-04-07 08:23:08 UTC
(In reply to comment #0)
> NetworkManager-0.9.2.0 does not dispatch down events when sleeping and up or
> hostname events after waking up for wifi connections. It *does* dispatch events
> correctly for wired ethernet connections, or after having previously
> successfully dispatched an "up" event for an ethernet connection on wakeup.

I apologize, the above is wrong, the real description should be:

NetworkManager-0.9.4.0 does not dispatch "up" or events after waking up for wifi connections. It *does* dispatch events correctly for wired ethernet connections, or after having previously successfully dispatched an "up" event for an ethernet connection on wakeup.

I had accidentally committed the first draft of the bug description :/
Comment 2 Pavel Simerda 2013-05-06 13:34:29 UTC
Is it still the case for more recent versions?
Comment 3 Dan Williams 2014-05-05 22:26:51 UTC
Closing with insufficient info... please re-open if this is still a problem in NM 0.9.8.10 and later.