wifi turned off after standby
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My notebook is a Acer Travelmate 8372.
After returning from standby and sometimes when booting following behavior occurs:
The hardware wifi led is on. The network manager shows no connection (and there is no connection). After pressing the hardware wifi switch ones the wifi led turns off, nothing happens on th network manager. After pressing the hardware wifi switch a second time the wifi led turns on and the network manager connects to the wifi.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.1
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
CRDA:
country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
Date: Thu Oct 11 07:55:12 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
default via 192.129.10.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.129.10.0/23 dev wlan0 proto kernel scope link src 192.129.11.95 metric 2
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
FAU-STAFF 2055d443-
Kabelnetzwerkv
annettetobi f932c94c-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled enabled enabled disabled
Status changed to 'Confirmed' because the bug affects multiple users.