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 560334 - nm-applet show no wireless networks
nm-applet show no wireless networks
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.7.x
Other All
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-11-11 13:10 UTC by Richard Hering
Modified: 2008-11-13 21:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Richard Hering 2008-11-11 13:10:16 UTC
Please describe the problem:
nm-applet show no wireless networks, networkmanager+nm-applet 0.6.6 are working fine, iwlist scan show me wireless networks too.

06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Richard Hering 2008-11-11 13:26:05 UTC
NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
NetworkManager: <info>  eth0: driver is '8139too'.
NetworkManager: <info>  Found new Ethernet device 'eth0'.
NetworkManager: <info>  (eth0): exported as /org/freedesktop/Hal/devices/net_00_0a_e4_a7_f9_e6
NetworkManager: <info>  eth1: driver is 'ipw2200'.
NetworkManager: <info>  eth1: driver supports SSID scans (scan_capa 0x21).
NetworkManager: <info>  Found new 802.11 WiFi device 'eth1'.
NetworkManager: <info>  (eth1): exported as /org/freedesktop/Hal/devices/net_00_12_f0_15_d0_0c
NetworkManager: <info>  Trying to start the supplicant...
NetworkManager: <info>  Trying to start the system settings daemon...
NetworkManager: <info>  (eth0): device state change: 1 -> 2
NetworkManager: <info>  (eth0): bringing up device.
NetworkManager: <info>  (eth0): preparing device.
NetworkManager: <info>  (eth0): deactivating device (reason: 2).
NetworkManager: <info>  (eth1): device state change: 1 -> 2
NetworkManager: <info>  (eth1): bringing up device.
NetworkManager: <info>  (eth1): preparing device.
NetworkManager: <info>  (eth1): deactivating device (reason: 2).
NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Comment 2 Richard Hering 2008-11-12 12:10:45 UTC
lshal says:

udi = '/org/freedesktop/Hal/devices/net_00_12_f0_15_d0_0c'
  info.capabilities = {'net', 'net.80211'} (string list)
  info.category = 'net.80211'  (string)
  info.parent = '/org/freedesktop/Hal/devices/pci_8086_4220'  (string)
  info.product = 'WLAN Interface'  (string)
  info.subsystem = 'net'  (string)
  info.udi = '/org/freedesktop/Hal/devices/net_00_12_f0_15_d0_0c'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'net'  (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1e.0/0000:06:05.0/net/eth1'  (string)
  net.80211.mac_address = 81337372684  (0x12f015d00c)  (uint64)
  net.address = '00:12:f0:15:d0:0c'  (string)
  net.arp_proto_hw_id = 1  (0x1)  (int)
  net.interface = 'eth1'  (string)
  net.linux.ifindex = 3  (0x3)  (int)
  net.originating_device = '/org/freedesktop/Hal/devices/pci_8086_4220'  (string)
Comment 3 Dan Williams 2008-11-12 15:29:27 UTC
What version of wpa_supplicant is running, and when this problem occurs, can you do:

ps aux | grep "wpa_supplicant"

for me?  Need to see if the supplicant's dbus interface is enabled.  Thanks!
Comment 4 Richard Hering 2008-11-12 16:17:41 UTC
Running is net-wireless/wpa_supplicant-0.6.4  USE="dbus readline ssl -debug -gnutls -gsm -madwifi -ps3 -qt3 -qt4"

ps aux | grep "wpa_supplicant" show nothing



# cat /etc/dbus-1/system.d/wpa_supplicant.conf
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy user="root">
                <allow own="fi.epitest.hostap.WPASupplicant"/>

                <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
                <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
        </policy>
        <policy context="default">
                <deny own="fi.epitest.hostap.WPASupplicant"/>
                <deny send_destination="fi.epitest.hostap.WPASupplicant"/>
                <deny send_interface="fi.epitest.hostap.WPASupplicant"/>
        </policy>
</busconfig>
Comment 5 Dan Williams 2008-11-12 18:02:55 UTC
Is the 'ps aux' doesn't show up, then wpa_supplicant isnt' actually running.  What do you have for this file:

/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

it should have something like this:

[D-BUS Service]
Name=fi.epitest.hostap.WPASupplicant
Exec=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
User=root


without that file, wpa_supplicant won't be auto-started by NM.  Your distro should have already configured this for you.
Comment 6 Richard Hering 2008-11-12 19:01:47 UTC
-rw-r--r-- 1 root root 92 12. Nov 19:58 /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

[D-BUS Service]
Name=fi.epitest.hostap.WPASupplicant
Exec=/sbin/wpa_supplicant -u
User=root

With your version of this file wpa_supplicant didn't start too.
Comment 7 Dan Williams 2008-11-13 14:58:43 UTC
Can you manually run the supplicant with "/sbin/wpa_supplicant -dddt -u"?  Does it fail to launch?
Comment 8 Robert Piasek 2008-11-13 15:02:16 UTC
Please correct me if I'm wrong, but

NetworkManager: supplicant_interface_acquire

would suggest that NM lunched supplicant, but from (some) reason it died.

Have you tried manually running supplicant ?
Comment 9 Richard Hering 2008-11-13 17:35:36 UTC
I'm currently running wpa_supplicant manually to use NetworkManager:

/sbin/wpa_supplicant -dddt -u says
http://rafb.net/p/Cu7PL299.html
Comment 10 Dan Williams 2008-11-13 21:33:56 UTC
So if running it manually works, but auto-activating doesn't work, then you'll need to figure out with your distro's dbus and wpa_supplicant package maintainers why it's not able to be auto-activated by NM, or why the supplicant is quitting after being activated by NM.