nm-indicator shows no network devices

Bug #865982 reported by Ralf Hildebrandt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

All over a sudden, the nework Manager indicator doesn't show any network connections at all.
At the same time the network DOES work.

Here at work I'm using a simple wired connection with DHCP.

$ lspci |grep -i net
00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)

$ dmesg |grep eth
[ 1.914270] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:19:99:58:52:af
[ 1.914273] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 1.914317] e1000e 0000:00:19.0: eth0: MAC: 8, PHY: 8, PBA No: FFFFFF-0FF
[ 18.100448] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.144891] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 21.145240] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 31.416013] eth0: no IPv6 routers present

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Oct 4 10:08:02 2011
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IpRoute:
 default via 141.42.231.1 dev eth0 proto static
 141.42.231.0/24 dev eth0 proto kernel scope link src 141.42.231.227 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 virbr0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager
UpgradeStatus: Upgraded to oneiric on 2011-09-07 (26 days ago)
ftp_proxy: ftp://proxy-cvk-1.charite.de:8080/
http_proxy: http://proxy-cvk-1.charite.de:8080/
no_proxy: charite.de

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I'm also seeing this issue with wired connection. But in my case I don't have any network connection when it happens. Today there was an update with some network components, and I haven't seen this issue since then, but it does not happen too often, so I will keep watching.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

If you kill nm-applet and restart it, can you then see the devices? I can't reproduce this bug yet, so let's try to find a particular case which would trigger it to show.

Also, please see if you can add debugging logs for NetworkManager; see http://live.gnome.org/NetworkManager/Debugging

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

In my case restarting the network-manager service reestablished networking, but as I said I haven't seen again this issue since yesterdays's updates.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

After a restart, all is working again.

Revision history for this message
Yann Dìnendal (yannbreliere) wrote :

I can also confirm it is now fixed, after a reboot.

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.