KNetworkManager doesn't initially connect to wired network

Bug #123914 reported by Mitch Golden
34
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Fix Released
High
Anthony Mercatante

Bug Description

Binary package hint: knetworkmanager

I just found this in Gutsy Alpha 2. Networkmanager / KNetworkmanger worked fine in Feisty and even Gutsy alpha 1. Gutsy alpha 2 has KNetworkManager 0.2 so it may have something to do with that.

When I log in to the system, I have no connection, and the icon shows disconnected. I need to manually select the wired network for it to connect, and then it works.

It may be the same as this bug, but that one is closed so I am resubmitting this:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/105234

I have an old Sony Vaio PCG-XG19, and I have a Xircom cardbus PCMCIA card for a network connection.

Revision history for this message
Mitch Golden (mgolden) wrote :

I should point out that I am using DHCP not a static internet address, and because of this I have no connection prior to manually connecting using KNetworkmanager.

Revision history for this message
Mitch Golden (mgolden) wrote :

I have also noticed that if I start with the network cable unplugged and then plug it in, KNetworkmanager doesn't connect either. The only way I see a connection is if I manually connect.

Revision history for this message
Mitch Golden (mgolden) wrote :

When I try the same gutsy alpha 2 CD in my other laptop, a Dell Inspiron 6400 with built in ethernet, it *does* connect on login. So this problem appears confined to my old Sony Vaio with the PCMCIA ethernet card.

Revision history for this message
Mitch Golden (mgolden) wrote :

Actually, I take that back. While it did connect initially, it doesn't always connect or disconnect when I remove the ethernet cable.

Revision history for this message
Christian Schürer-Waldheim (quincunx) wrote :

I can confirm this bug

Gutsy on a Dell Latitude D620 - but I don't think this is in any way hardware-related.

Changed in knetworkmanager:
status: New → Confirmed
Changed in knetworkmanager:
importance: Undecided → High
assignee: nobody → tonio
Revision history for this message
Márcio Santos (marcio.santos) wrote :

I can confirm the bug.
nm-applet 0.6.5 on Gnome

Gutsy on unbranded PC with e100 network driver.

On session login NM won't detect network and signals that there is no connection and no cable connected. The only way to make it work is to disable networking with the applet and enabling it afterwards.
After enabling it detects cable, requests IP from DHCP Server and everything works ok.

Revision history for this message
Christian Schürer-Waldheim (quincunx) wrote :

In current gutsy, problem doesn't show up any more - so I suppose this report can be declared as being fixed. Thanks to the one who fixed it!

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

seeing this fixed here too.

Changed in knetworkmanager:
status: Confirmed → Fix Released
Revision history for this message
Mitch Golden (mgolden) wrote : Re: [Bug 123914] Re: KNetworkManager doesn't initially connect to wired network

I see it *partially* fixed. I just installed and tried Gutsy Alpha 3 and
find that it does connect if you're plugged in when you log in. However,
it is still not responding to pluging in or unplugging the network cable.
Is anyone else seeing this?

Revision history for this message
Mitch Golden (mgolden) wrote :

I am still seeing the same thing on alpha 4. There is no response to plugging in or unplugging the wired network.

Revision history for this message
Mitch Golden (mgolden) wrote :

I just noticed an additional, probably related thing: it doesn't reconnect to the Wired Network after a suspend or hibernate.

Revision history for this message
Ferdinand (ferdinand-hertog) wrote :

I have this same problem with Ubuntu Gutsy Gibbon 7.10 beta with a Gigabyte P35 DS4 with rtl8111/8168B Gbit network card. But my network never works. Even when I give it a static ip. I used the livecd.

Revision history for this message
Gulars (spam-elvenhome) wrote :

I'm still seeing a related issue on a Lenovo ThinkPad T60 (ethernet chipset 82573L). When I boot the laptop (running kubuntu gutsy) with the network cable disconnected, knetworkmanager doesn't register the interface at all. I tried the suggestion above, to enter offline mode and going online again, without any success. I also tried restarting networking in general but that didn't work either.

Any resolution to this?

Revision history for this message
Mitch Golden (mgolden) wrote :

In the released version of Gutsy, I see the problem on my old Sony Vaio PCG-XG19 with the Xircom cardbus PCMCIA card. It doesn't connect on login, though does just fine if I tell it to do so manually. However, it does not respond to the cable being unplugged.

Revision history for this message
Gulars (spam-elvenhome) wrote :

Another thing is that when reconnecting to secured networks, it will either give me the password-box, prefilled with the password, and the connect button disabled (have to add, and then remove a characted for it to get enabled, so one can connect), or it just asks for the password again, with the entry field empty.

Revision history for this message
Mitch Golden (mgolden) wrote :

This bug is still present for me on Hardy Alpha 1. As I said above, I have an old Sony Vaio PCG-XG19 with a Xircom cardbus PCMCIA card. NetworkManager/KnetworkManager doesn't connect to the wireless network at logon, but will connect if I manually do it. I won't disconnect if I unplug the cable.

Revision history for this message
Mitch Golden (mgolden) wrote :

I think I have an idea some of what is going on.

The old card I am using shows up in KNetworkManager as not supporting Carrier Detect. Somehow the older versions detected that the card was there and tried it. The new version sees the wired network, and though it *can* connect to it, it doesn't initially do it. If I use a network card that does support Carrier Detect, it does properly connect.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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