network-manager panel icon does not show connected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
After a very long wait, the network-manager finally found the wireless site it connects to often. The spinner never spun during connecting. The notification system popped up a notification that the connection was established but the icon had never changed appearance once during the process. The was directly following a cold boot.
This is not repeatable and normally the icon spins while connecting then shows signal strength once connected.
This is the release version network-manager included with a fresh install of Karmic.
ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Nov 2 13:56:36 2009
DistroRelease: Ubuntu 9.10
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IpRoute:
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.175 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.0.1 dev wlan0 proto static
NonfreeKernelMo
Package: network-manager 0.8~a~git.
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:1950): Eel-CRITICAL **: eel_preferences
(Do:1984): Wnck-CRITICAL **: wnck_set_
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 471688 and any other logs that are relevant for this particular issue.