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 587946 - Connections not found but eth0 connects
Connections not found but eth0 connects
Status: RESOLVED DUPLICATE of bug 589003
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.7.x
Other All
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-07-07 06:57 UTC by Raza Abbas
Modified: 2010-01-30 22:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raza Abbas 2009-07-07 06:57:54 UTC
Please describe the problem:
None of the connections are ever found but somehow eth0 connects. You cant see any information about the connection at all. It works but it acts like there is no connection. This is what i got when i ran nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            sky2
  State:             unmanaged
  Default:           no
  HW Address:        00:00:00:00:00:00

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties

Its saying its disconnected, but its not. 

(I am running Debian Sid)

Steps to reproduce:
I am not sure, it was like this when i upgraded to 0.7.1.


Actual results:
n/a

Expected results:
n/a

Does this happen every time?
Yes, I tried to restarting it but nothing happens. 

Other information:
This people seem to have the same bug as me...
http://linux.derkeiler.com/Mailing-Lists/Debian/2008-03/msg01863.html
Comment 1 Dan Williams 2010-01-30 22:46:11 UTC
NM reports eth0 as "unmanaged"; see the details in this bug for more infromation.  Short version: remove anything to do with eth0 from /etc/network/interfaces, and NM will managed the device.

*** This bug has been marked as a duplicate of bug 589003 ***