nm and 'rfkill event' report opposite connect states

Bug #1097573 reported by Doug Parker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) Release info

Description: Ubuntu 12.04.1 LTS
Release: 12.04

2) Version info

  network-manager-gnome:
  Installed: 0.9.4.1-0ubuntu2
  Candidate: 0.9.4.1-0ubuntu2
  Version table:
 *** 0.9.4.1-0ubuntu2 0
        500 http://ports.ubuntu.com/ubuntu-ports/ precise/main powerpc Packages
        100 /var/lib/dpkg/status

3) What I expected to happen

When the Network pane in the system setting showed it was ON, I expected rfkill to report soft 1, and when it was off rfkill would report 0.

4) What happened instead

     sudo rfkill event

displays

     1357708427.073598: idx 0 type 1 op 0 soft 0 hard 0
     1357708427.073749: idx 1 type 2 op 0 soft 0 hard 0

while the network pane in the system settings shows Wireless is set to ON. In the network icon on the menu bar, top right, wireless status is listed as "Wireless Networks device not ready."

In the network pane, when the ON/OFF toggle is set to OFF, sudo rfkill event then displays

     1357708691.237341: idx 0 type 1 op 2 soft 1 hard 0

In the network pane, when the ON/OFF toggle is set to ON, sudo rfkill event then displays

     1357708721.286917: idx 0 type 1 op 2 soft 0 hard 0

Assuming 0=OFF and 1=ON, rfkill and nm are reporting opposite network connection states.

In all cases, the network icon pulldown menu at the top right reported "Wireless Networks device not ready."

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager-gnome 0.9.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-35.55-powerpc64-smp 3.2.34
Uname: Linux 3.2.0-35-powerpc64-smp ppc64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: powerpc
Date: Wed Jan 9 00:04:22 2013
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release powerpc (20120423)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.107 metric 1
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 thin black cable 6bc8fd44-c80c-4713-bf02-89b1bcfbeb9f 802-3-ethernet 1357707656 Wed 09 Jan 2013 12:00:56 AM EST yes no /org/freedesktop/NetworkManager/Settings/1
 LittleMad 216ec57b-f9eb-4d7d-9c0c-5e1c1fb9677c 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/1
 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Doug Parker (ispinn) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.