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 636194 - When wireless hard switch turned on, does not show networks in range
When wireless hard switch turned on, does not show networks in range
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-12-01 05:22 UTC by Christopher M. Penalver
Modified: 2012-07-25 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
/var/log/syslog Ubuntu 11.04 (108.64 KB, text/plain)
2011-04-30 14:24 UTC, Christopher M. Penalver
Details

Description Christopher M. Penalver 2010-12-01 05:22:26 UTC
Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/651571

Binary package hint: network-manager

1) lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

2) apt-cache policy network-manager
network-manager:
  Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
  Version table:
 *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

3) Thank you for reading this. What is expected to happen is Network Manager populates networks within range immediately when ones laptop hardswitch is turned on, whether the ethernet cord is plugged in or not.

4) What happened instead is when the hardswitch is off, ethernet plugged in, one removes the ethernet cord, then within seconds turn the hardswitch on so the wifi indicator light is on, no networks are in range, even after waiting a few minutes.
Please see screenshot.png for scenario where the ethernet cord is plugged in, wifi switch on and no wifi networks populate Network Manager. If questions exist, please ask.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Sep 29 17:11:29 2010
EcryptfsInUse: Yes
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
IpRoute:
 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.12 metric 1
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.0.1 dev eth0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: network-manager
Comment 1 Jiri Klimes 2011-01-19 12:32:12 UTC
Well, you have wireless disabled.

If you switch it on by hardware switch, rfkill list should indicate that it's not blocked.
The other thing is that in /var/lib/NetworkManager/NetworkManager.state WirelessEnabled should be true. Did you disable that by right-clicking nm-applet and unchecking "Enable Wireless"?
Comment 2 Christopher M. Penalver 2011-01-19 18:35:12 UTC
Jiri Klimes thank you for working together with me on this bug.

> Well, you have wireless disabled.
> 
> If you switch it on by hardware switch, rfkill list should indicate that it's
> not blocked.
> The other thing is that in /var/lib/NetworkManager/NetworkManager.state
> WirelessEnabled should be true. 

Agreed.

> Did you disable that by right-clicking nm-applet and unchecking "Enable Wireless"?

No, I did not hover my mouse on/near nm-applet during https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/651571/comments/5
Comment 3 Jiri Klimes 2011-01-20 08:07:52 UTC
> 
> > Did you disable that by right-clicking nm-applet and unchecking "Enable Wireless"?
> 
> No, I did not hover my mouse on/near nm-applet during
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/651571/comments/5

Okay, it could become false due to unsuccessful suspend/resume or something.
Changing /var/lib/NetworkManager/NetworkManager.state 
WirelessEnabled back to true should enable wireless again.
Comment 4 Dan Williams 2011-04-22 20:01:42 UTC
Any update on this issue Christopher?  NM 0.8.4 fixes some issues with WiFi rfkill handling and user state handling.
Comment 5 Christopher M. Penalver 2011-04-30 14:24:56 UTC
Created attachment 186940 [details]
/var/log/syslog Ubuntu 11.04
Comment 6 Christopher M. Penalver 2011-04-30 14:29:31 UTC
Dan Williams, thank you for following up. Ubuntu 11.04, NM 0.8.4 improved the situation as I am able to workaround the problem:

With wireless hardswitch turned off, ethernet cable plugged in clean boot into a Ubuntu 11.04 Live CD. Immediately took copy of /var/log/syslog (please see attached /var/log/syslog Ubuntu 11.04). Disconnected ethernet cord then turned on wireless hardswitch but no wireless networks in the area. Performed the following via the Terminal:

ubuntu@ubuntu:~/Desktop$ sudo stop network-manager 
network-manager stop/waiting
ubuntu@ubuntu:~/Desktop$ sudo start network-manager
network-manager start/running, process 5172
ubuntu@ubuntu:~/Desktop$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Could see wireless networks in range and successfully connected.

lsb_release -rd
Description:        Ubuntu 11.04
Release:        11.04

apt-cache policy network-manager
network-manager:
  Installed: 0.8.4~git.20110319t175609.d14809b-0ubuntu3
  Candidate: 0.8.4~git.20110319t175609.d14809b-0ubuntu3
  Version table:
 *** 0.8.4~git.20110319t175609.d14809b-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status
Comment 7 Pavel Simerda 2012-07-25 11:23:09 UTC
AFAIK the rfkill handling is totally different in 0.9.x and this bug report isno longer valid.