Network manager says disconnected but is connected and working

[denzilla74]

Binary package hint: network-manager

Since a recent update today sometime, network manager says I'm disconnected, but I have full access to the net and the connection is working fine. I can unplug/plug the cable and it will reconnect and show the correct status, until I restart.

[Bradley Nampel (bnampel)]

I can confirm this behavior.on a fully up-to-date Feisty install.

[James Hall (james-hall-01)]

Thanks for your bug report. This particular bug has already been reported and is a duplicate of bug 82927 and is being marked as such. Please feel free to report any other bugs you may find.

[Brian Murray (brian-murray)]

I don't believe there is sufficient evidence to indicate that this is a duplicate of bug 82927 and I am unmarking it as a duplicate.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full output of 'lspci -vv' and '/var/log/daemon.log' when you are experiencing the problem? Thanks in advance.

[Bart Verstraete (bartverstraete)]

Got the same thing, my regular network don't shows up, it says that I am disconnected. But it still works. And my Access points shows up but they got a signal strength of 0 and are grey.
My daemon.log is attached.

[Bart Verstraete (bartverstraete)]

My lspci -vv

[Dan Bishop (danbishop)]

I can also confirm this, the network manager applet now says "No network devices have been found"

[Dan Bishop (danbishop)]

My daemon.log

[Guido Conaldi (guido-conaldi)]

Can confirm on my Feisty 32bit up-to-date. It started misbehaving yesterday.

[Andrew (at-macmillan)]

I am having the same problem after an update done today.

[Harryc (harryc56)]

Same problem on a fully up top date Feisty install.

[Felix Heinonen (fheinonen)]

Same problem here.

[wlx (wangliangxu)]

same problem here.

[Matthew Nuzum (newz)]

Just updated today (April 11) and this problem started happening. Attached is lspci -vv. Daemon log will be attached next.

[Mackenzie Morgan (maco.m)]

lspci

[Mackenzie Morgan (maco.m)]

Mine connects on wireless, claims to be disconnected, and works just fine. It still shows the lists of networks and all. And wireless still works fine. It just says my wired connection is disconnected while it's fully functional (like now). When the sky2 driver goes *death* (because it's a yicky driver), NM doesn't switch to "disconnected" so I'll be looking at it going "it says I'm connected why isn't $WEBSITE loading?" though now I've come to realize that that means my driver crapped out as usual and just unload/reload the module. When I unload, it, *then* it says I'm disconnected and goes and grabs a [man-in-the-middle attack ad-hoc with the same SSID as the school one] wireless network.

[Mackenzie Morgan (maco.m)]

Ah! I meant "mine connects on wired" on boot and claims to be disconnected. Sorry, like I said, wireless works fine (or at least it wasn't telling me I'm disconnected from wireless this morning when I updated it).

[Rob Dian (robdian)]

Same here. Showing as "no network connection" but everything works fine.

[Rob Dian (robdian)]

lspci

[Daniel Botelho (botelho-daniel)]

Hello! I've the same problem.. Today I'v updated the network-manger from the "Update Manger" and know it's not working properly.
Well actually it's working, but after I've done the update now it says "No network connection"(when move mouse over it) and if I right click in it, it says "No Network devices found".
If I execute the command "ifconfig" on the console it's working nicely and I can still use the internet, but basically I can't use the GUI.

[mountain (nik-kufstein)]

Same problem, but also when i disable the wireless network the whole system hangs and stops responding.

output off my daemon.log

Apr 11 18:55:50 TUX NetworkManager: <information>^IDeactivating device rausb0.

So it is disabling the wireless but the system hangs and isnt responding.

I noticed this behaviour on older versions off the network manager also.
Older versions deactivated my lo interface the 127.0.0.1 localhost, but this version crashes the system.

[Mackenzie Morgan (maco.m)]

Others are having it say no network devices found when they right click. While mine is saying it's disconnected when it's actually connected and working, it does drop down the "enable wired / enable wireless" thing when I right click.

[lizardmenke (lizardmenke)]

Same here :after yesterday's update NM says it's not connected but everything works fine (wired connection)

[yostral (y-o)]

Same problem here too.
On startup it says non connection, but the connection is ok. I have to select a connection (wired or wifi) to have the "normal" behaviour back.

[Soul-Sing (soulzing)]

 https://bugs.launchpad.net/ubuntu/+bug/105434

[denzilla74 (denzilla74-deactivatedaccount)]

Just got a network manager update and problem remains. Here are the logs you requested:

[xtknight (xt-knight)]

This seems to fix it. Not sure if it's a hack or not but even if it is I can't see the side effects.

[Wenzhuo Zhang (wenzhuo)]

I am afraid 0.6.4-6ubuntu6 does not fix the problem on my laptop. I have restarted Gnome.

[Christoph Donges (cdonges)]

Same issue for me too. Shows I am disconnected with a wired connection even though I am.

[os2mac (os2mac)]

I have reported a similar bug to Knetworkmanager for kubuntu Bug #105352. Mine is a wireless connection.

[James (chiisu81)]

Same as Wenzhuo Zhang stated, latest update still shows this problem

[os2mac (os2mac)]

are we sure this is a network-manager thing and not a GUI thing.. My bug appears in Knetworkmanager but if I run Kwifimanager it works just fine.

[Dee (dee24)]

Oh, I'm getting the same issue here... hmm, I wonder what the root of this problem could be.

[Chris Malton (chrism-cjsoftuk)]

Just updated to 0.6.4-ubuntu5, same problem exists!

The funny thing is, I have a network connection monitor applet showing I am connected!

[Wenzhuo Zhang (wenzhuo)]

Obviously, it's a regression introduced in 0.6.4-6ubuntu5. If I downgrade to 0.6.4-6ubuntu4, the applet works very well.

# sudo dpkg -i --force-downgrade /var/cache/apt/archives/network-manager-gnome_0.6.4-6ubuntu4_i386.deb /var/cache/apt/archives/network-manager_0.6.4-6ubuntu4_i386.deb

[brazz (brazz-ardent)]

OK, I have the same bug since yesterday (after I upgrade Feisty).

[Wenzhuo Zhang (wenzhuo)]

Another problem with 0.6.4-6ubuntu6: if I right click the applet icon and de-select "Enable Wireless", the applet silently quits.

[Dan Bishop (danbishop)]

Is this really only medium importance, it's a pretty major bug which obviously affects an awful lot of people, look how many comments have been posted in the last 24 hours alone!

[Soul-Sing (soulzing)]

Dan Bishop wrote:
> Is this really only medium importance, it's a pretty major bug which
> obviously affects an awful lot of people, look how many comments have
> been posted in the last 24 hours alone!
>
it does effects a lot of people. but is doesn't disable the internet
connection.

[Grzegorz Galezowski (spectral)]

In my case commenting out all of the lines in /etc/network/interfaces helped. I entered the static ip data through network-admin again and it seems to work quite well (but it seemed not to work with wired connection until I turned my wifi on and off). I attached my interfaces file (with some minor changes to wifi network name and key). I dtill don't know which line could be the problem for gnome network manager applet...

[Mackenzie Morgan (maco.m)]

If you can still connect, and everything, and the bug is just "it should show the other picture," it's not very major.

[Daniel Botelho (botelho-daniel)]

I've made the upgrade but the problem persists :\

[brazz (brazz-ardent)]

Oh, this is my new constatation: if I right click on the Manager icon and deselect cable network, the network is then disable, after I reselect cable network, then the network is enable but also the red indicator disappear and all work fine !
(sorry for my bad english language...)

[Chris Malton (chrism-cjsoftuk)]

After using the following instructions I have an even weirder situation. Icon shows disconnected, right click -> Connection information is available!

Here are the instructions I followed (From 105243):

I had the same problem and this is how I fixed it:

* shutdown NetworkManager, e.g. with 'sudo kill -2'.

* backup your /etc/network/interfaces:

sudo mv /etc/network/interfaces /etc/network/interfaces_bak

* restart NetworkManager:

sudo /usr/sbin/NetworkManager --pid-file
/var/run/NetworkManager/NetworkManager.pid

Apparently NetworkManager is a little flaky with certain entries in the
interfaces file.

[os2mac (os2mac)]

I followed CJ's instructions and this corrected my problem also.

[Felix Heinonen (fheinonen)]

Except these instructions make things even worse after reboot.
"Sorry, but my solution won't work after a reboot. Even worse is that
Network Manager creates a new interfaces file without the loopback
interface, which will causes severe trouble.

Please make sure that these lines are present in your interface file:

auto lo
iface lo inet loopback

I guess something really broke with the updated packages..."

[Wenzhuo Zhang (wenzhuo)]

After commenting out the static parameters (address, network and gateway) of the primary network interface stanza in my http://librarian.launchpad.net/7259051/interfaces, 0.6.4-ubuntu6 works again, and it no longer quits silently when disabling wireless.

[gmlion (gm-l)]

I've ever had this problem since old version of Feisty, but it happens when I use a static configuration for my wireless connection. But is it supposed to work?

[Robert Rittenhouse (rrittenhouse)]

I am running a fully updated feisty system and I have the same problems as described. I have the red X on the network manager icon upon boot and I just left click on it and select wired again and let it reconnect again just so the icon wont show as disconnected.

If you still need the output for daemon.log here it is.

[ElVirolo (elvirolo-gmail)]

Same problem here.

[ubu-for (ubu-for)]

Quote: "Could you please add the full output of 'lspci -vv' and '/var/log/daemon.log' when you are experiencing the problem?"

[Scott James Remnant (Canonical) (canonical-scott)]

Please try the source package at the following URL, it should solve this problem:

    http://people.ubuntu.com/~scott/packages/

If you've never built a package from source before, grab those three files into an empty directory, and use the following commands:

    $ sudo apt-get build-dep network-manager
    $ sudo apt-get install fakeroot
    $ dpkg-source -x network-manager_0.6.4-6ubuntu7.dsc
    $ cd network-manager-0.6.4
    $ dpkg-buildpackage -rfakeroot -b -uc -us
    $ cd ..
    $ sudo dpkg -i *.deb

Then restart your computer.

[Matthew Nuzum (newz)]

today without installing any updates (yet), my network manager appears to be working normally.

[Peter Garrett (peter-garrett)]

On Thu, 12 Apr 2007 17:29:40 -0000
Scott James Remnant <email address hidden> wrote:

> Please try the source package at the following URL, it should solve this
> problem:
>
> http://people.ubuntu.com/~scott/packages/

this appears to have solved the problem here.

note that this machine has only eth0 ( wired) - but was exhibiting this
behaviour before I compiled and installed the packages as instructed

Thanks Scott - will now try the same on my iBook with bcm43xx wireless :)

[Peter Garrett (peter-garrett)]

Compiles and works like a charm on my iBook G4 as well :)) Also seems to associate better/faster, and responds better to disconnection/wired/wireless connection changes!

Nice work :)

lspci :

0000:00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP
0000:00:10.0 VGA compatible controller: ATI Technologies Inc M9+ 5C63 [Radeon Mo
bility 9200 (AGP)] (rev 01)
0001:10:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 PCI
0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless
 LAN Controller (rev 03)
0001:10:17.0 Class ff00: Apple Computer Inc. KeyLargo/Intrepid Mac I/O
0001:10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
0001:10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
0001:10:1a.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB
0001:10:1b.0 USB Controller: NEC Corporation USB (rev 43)
0001:10:1b.1 USB Controller: NEC Corporation USB (rev 43)
0001:10:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
0002:20:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 Internal PCI
0002:20:0d.0 Class ff00: Apple Computer Inc. UniNorth/Intrepid ATA/100
0002:20:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev
81)
0002:20:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM)
(rev 80)

[Marco Rodrigues (gothicx)]

Scott.. with your patch it now works fine =)

[Hundycougar (jdolence-coopervision)]

This patch fixed it for me even without a reboot so thankyou

On Thu, 2007-04-12 at 15:56 -0400, Marco Rodrigues wrote:

> ** Changed in: network-manager (Ubuntu)
> Assignee: (unassigned) => Scott James Remnant
>
> ** Changed in: network-manager (Ubuntu)
> Status: Confirmed => In Progress
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

[Chris Malton (chrism-cjsoftuk)]

Unfortunately I now have a new issue.

It now is exactly the opposite problem to this bug, my network-manager won't show DISCONNECTED.

If I unplug my eth2, nm-applet shows the connection as still established (I do have vmware installed if it makes any difference).

However, the Network Monitor applet for GNOME works fine.

I also use static IP configuration.

[Francesco Innocenti (frainnoc)]

I have the same problem after several update in feisty Kubuntu 7.04

[Hundycougar (jdolence-coopervision)]

After the patch my system works fine connected or disco ed
--------------------------
Sent from my BlackBerry Wireless Handheld

----- Original Message -----
From: <email address hidden> <email address hidden>
To: James Dolence
Sent: Thu Apr 12 16:16:46 2007
Subject: [Bug 105234] Re: Network manager says disconnected but is connectedand working

Unfortunately I now have a new issue.

It now is exactly the opposite problem to this bug, my network-manager
won't show DISCONNECTED.

If I unplug my eth2, nm-applet shows the connection as still established
(I do have vmware installed if it makes any difference).

However, the Network Monitor applet for GNOME works fine.

I also use static IP configuration.

--
Network manager says disconnected but is connected and working
https://bugs.launchpad.net/bugs/105234
You received this bug notification because you are a direct subscriber
of a duplicate bug.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

[sojourner (itsmealso2)]

Same here, mine started 2 days ago , I have a wired connection only on this box , I also have had everything except lo commented out for some time , I checked they are still commented out. network manager shows disconnected in the top bar but right click>connection information shows correct ,and I am actualy connected. also since this started, update manager when it runs automaticly after AM bootup, closes my network connection as soon as it has down loaded the info and I have to restart the connection to download the actual updates this does not happen when I manualy run UM or synaptic .

[sojourner (itsmealso2)]

applied patch it seems to have fixed things.

[os2mac (os2mac)]

same here... applied patch cleared up the problem.

[Wenzhuo Zhang (wenzhuo)]

My previous comment <https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/105234/comments/53> is wrong. network-manager-0.6.4-ubuntu6 works OK only after freshly upgraded from 0.6.4-ubuntu4. But, after restarting Gnome, network-manager-0.6.4-ubuntu6 still shows no network connection, even with the unnecessary static parameters commented out in /etc/network/interfaces.

Tried network-manager-0.6.4-ubuntu7. Tests include restarting Gnome and computer, switching between wired and wireless network. Everything seems to work fine now.

[Harryc (harryc56)]

Applied patch and Network Manager works fine. Thanks Scott.

[Tollef Fog Heen (tfheen)]

RC for feisty.

[Daniel Botelho (botelho-daniel)]

I've used that path and is working correctly now.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/105234/comments/59

[Raphael (rasch-mytum)]

Tried the new version and have still the same problems running Kubuntu on a
Thinkpad T60 using KNetworkManager.

Version 0.6.4-6ubuntu4 worked fine, when attached to the wired network, the
corresponding icon was shown, when atached to WLAN, the connectivity level
was shown. After updating to 0.6.4-6ubuntu5 only the 'not-connected' icon is
showing and in the menu of the applet is an entry saying 'no network device found'
(or similar; it is in German). With the new source I have the same behavior.

After looking in the source for version 0.6.4-6ubuntu4 and 0.6.4-6ubuntu7
maybe the problem is in function nm_system_device_get_disabled() in
src/backends/NetworkManagerDebian.c . In version 0.6.4-6ubuntu4 the last
check ('If the interface has no options other than just "inet dhcp" it's
probably ok to fiddle with it.') was disabled. In the current version the
check is done. When a manual configuration was done, there are other options
in /etc/network/interface which sets the device on the blacklist.

I have no experience how the network interface settings stuff works internal
(I am just a user of the GUI controling programs/applets) but version
0.6.4-6ubuntu4 worked for me most of the time (when switching from WLAN to
LAN I had to re-load the manual settings because the DNS entries where not
updated). so I do not know if now the "bug" is on my side how I am managing
my network connections.

[Scott James Remnant (Canonical) (canonical-scott)]

If you have manually configured networking, you should find that the tooltip for the icon says "Manual network connection", and if you click on it, the only menu option is to configure that manual networking.

[Scott James Remnant (Canonical) (canonical-scott)]

Fixed packages have been uploaded

[birdflesh (birdflesh)]

I confirm what Raphael says. 0.6.4-6ubuntu7 doesn't fix the problem with KNetworkManager on kubuntu

[VF (vfiend)]

Works for me on GNOME. Maybe you two should file a seperate Kubuntu/KDE/KNetworkManager-related bug.

[marcobra (Marco Braida) (marcobra)]

With today 20070413 the problem update seems fixed.

[ulrich (ulrich)]

i had not experienced this bug until todays update.
now network-manager shows no connection even if there is one.

[James (jasch1)]

I have Feisty Beta full updated running on two computers. Both of them had the
problem with the panel icon showing no network connection when there was a connection.
I just updated both of the systems with some "network manager" stuff along with some
other upgrades. Now the problem on both computers seems to be fixed with the latest
updates. (The latest upgrades shown by Synaptic)

[douglas ewing (ewingdouglas)]

Thanx James, but..
I've done the same via Synaptic update, but no joy!

On 13/04/07, James <email address hidden> wrote:
>
> I have Feisty Beta full updated running on two computers. Both of them had
> the
> problem with the panel icon showing no network connection when there was a
> connection.
> I just updated both of the systems with some "network manager" stuff along
> with some
> other upgrades. Now the problem on both computers seems to be fixed with
> the latest
> updates. (The latest upgrades shown by Synaptic)
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Regards

Douglas

[yeti (utu)]

It might help if folks would indicate whether wired or wireless,
if they think this problem is fixed.

I'm *wireless*, and it's *not* fixed for me.
Im using 7.04 upgraded thru 2.6.20-15.24, including the latest NM upgrade.

My network functions just fine, but
I get no status information at all from NM.

How is it that this thread has the heading *Fix Released*, anyway?

[Conn O Griofa (psyke83)]

Hi,

Using Feisty with latest updates.

System 1: Desktop with wired connection via DHCP - works fine after newest update (shows as connected), previously gave notification that there was no network connection, but network functioned properly.

SYstem 2: Laptop with wireless connection (ipw2100) to WPA2-PSK/AES network - works fine after newest update, previously it showed the network connection correctly upon login and assocation, but when logging out and back in/restarting X, nm-applet would report no connection, despite connection working fine.

So, it's fixed on my systems for wired and wireless connections.

[PresuntoRJ (fabio-tleitao)]

Grate.

It worked both at my Dell Optiplex and a Compaq Armada Laptop, solving the
icons and messages problem, both in English and in Portuguese.

Will that be the next binary distributed as upgrade? I have other machines
with the same behavior but since its not that critical, I was willing to
wait a bit longer for the proper path upgrades.

On 4/12/07, Peter Garrett <email address hidden> wrote:
>
> On Thu, 12 Apr 2007 17:29:40 -0000
> Scott James Remnant <email address hidden> wrote:
>
> > Please try the source package at the following URL, it should solve this
> > problem:
> >
> > http://people.ubuntu.com/~scott/packages/
>
> this appears to have solved the problem here.
>
> note that this machine has only eth0 ( wired) - but was exhibiting this
> behaviour before I compiled and installed the packages as instructed
>
> Thanks Scott - will now try the same on my iBook with bcm43xx wireless
> :)
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--

Fábio Leitão, RCDD

[Peter Garrett (peter-garrett)]

 On Sat, 14 Apr 2007 02:32:22 -0000
 yeti wrote:

> My network functions just fine, but
> I get no status information at all from NM.

Meaning what? That your wireless and/or wired works fine, but the
nm-applet icon says there is no connection, or that you are using static
configuration and the applet reports nothing, or.... ??

[yeti (utu)]

Peter Garrett
Meaning applet reports nothing.
Applet allows me to see configuration details only.

[brazz (brazz-ardent)]

OK, great!
with the latest Feisty upgrade all work fine now!
many thanks

[douglas ewing (ewingdouglas)]

Hi PresuntoRJ - just got new upodates this morning 14/4/07 & it works! Thanx
for contacting so quickly.
Regards

On 14/04/07, PresuntoRJ <email address hidden> wrote:
>
> Grate.
>
> It worked both at my Dell Optiplex and a Compaq Armada Laptop, solving the
> icons and messages problem, both in English and in Portuguese.
>
> Will that be the next binary distributed as upgrade? I have other machines
> with the same behavior but since its not that critical, I was willing to
> wait a bit longer for the proper path upgrades.
>
> On 4/12/07, Peter Garrett <email address hidden> wrote:
> >
> > On Thu, 12 Apr 2007 17:29:40 -0000
> > Scott James Remnant <email address hidden> wrote:
> >
> > > Please try the source package at the following URL, it should solve
> this
> > > problem:
> > >
> > > http://people.ubuntu.com/~scott/packages/
> >
> > this appears to have solved the problem here.
> >
> > note that this machine has only eth0 ( wired) - but was exhibiting this
> > behaviour before I compiled and installed the packages as instructed
> >
> > Thanks Scott - will now try the same on my iBook with bcm43xx wireless
> > :)
> >
> > --
> > Network manager says disconnected but is connected and working
> > https://bugs.launchpad.net/bugs/105234
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
>
> --
>
> Fábio Leitão, RCDD
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Regards

Douglas

[douglas ewing (ewingdouglas)]

 Hi all - this mornings (14/4/07) updates appear to have sorted my/this
problem. Thanx all.
Regards

On 14/04/07, yeti wrote:
>
> It might help if folks would indicate whether wired or wireless,
> if they think this problem is fixed.
>
> I'm *wireless*, and it's *not* fixed for me.
> Im using 7.04 upgraded thru 2.6.20-15.24, including the latest NM upgrade.
>
> My network functions just fine, but
> I get no status information at all from NM.
>
> How is it that this thread has the heading *Fix Released*, anyway?
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Regards

Douglas

[ulrich (ulrich)]

as of today [ So 15. Apr 13:26:17 CEST 2007 ] and version 0.6.4-6ubuntu7 nm now shows correct state.
this is for a system with wired eth0 and dhcp.

[Ian Ohr (munk3h)]

I see this as fixed today on a system with wired eth0 and statically assigned IP.

[Neville Makopo (kompressor)]

I can confirm this is fixed today on a system with wired eth0 and dynamically assigned IP.

[Raphael (rasch-mytum)]

It now works also on Kubuntu using KNetworkManager without any problems.

[Ammar Aijazi (a-aijazi+launchpad)]

I just ran an update today, April 16th, in Kubuntu after about two weeks. It upgraded my network-manager from 0.6.4-6ubuntu4 to 0.6.4-6ubuntu7. This caused knetworkmanager to break, and only display the option of "Manual Configuration" (didn't seem to detect my wireless or wired connections). The problem persisted even after logging out and restarting. To fix it, I first ran:

sudo dpkg -i --force-downgrade /var/cache/apt/archives/network-manager_4-6ubuntu4_i386.deb

Restarting knetworkmanager at this point made it work just like it used to. I then did "sudo apt-get install network-manager", which upgraded it back to 0.6.4-6ubuntu7 --- however, it seems to work now. I don't know why it broke in the middle, but I can now also confirm that it's working with Kubuntu.

[Alex Fiestas (afiestas)]

I use a full update fesity (kubuntu) and i can't use wireless connection with static configuration, if i comment /etc/network/interfaces entrys for my wireless card it work.

If i use static connection knetworkmanager don't show any network.

thx.

[Martin Pitt (pitti)]

Alex, right, that's the way it is supposed to be. The lack of displaying of any information is bug 106508 (and a few others).

[James (chiisu81)]

It seems to work for everyone now, can this bug be closed or marked "Fix Released"?

[Geoff Jacobsen (geoffj)]

I have had no further problems. Please close.

On Tue, 2007-06-26 at 00:20 +0000, jclemon wrote:
> It seems to work for everyone now, can this bug be closed or marked "Fix
> Released"?
>

[Wladston Viana (wladston)]

No further problems, clear to close :)

[Shirish Agarwal (shirishag75)]

The updates worked for me too, although now on gutsy where things work greate atm.

[Mikael (fitmik)]

i have no more this probleme since the official releaese of ubuntu

2007/6/26, jclemon <email address hidden>:
>
> It seems to work for everyone now, can this bug be closed or marked "Fix
> Released"?
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Mikael FITOUSSI

[Soul-Sing (soulzing)]

that network-manager (baltix) status new, is this bug uptodate? or fixed with the other network-manager fix-released?

[PresuntoRJ (fabio-tleitao)]

solved both manually and by regular updates.

the bug does not seem to propagate to newer versions.

2007/6/26, leoquant <email address hidden>:
>
> that network-manager (baltix) status new, is this bug uptodate? or fixed
> with the other network-manager fix-released?
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--

Fábio Leitão, RCDD

[douglas ewing (ewingdouglas)]

I concur with all above

On 27/06/07, PresuntoRJ <email address hidden> wrote:
>
> solved both manually and by regular updates.
>
> the bug does not seem to propagate to newer versions.
>
>
> 2007/6/26, leoquant <email address hidden>:
> >
> > that network-manager (baltix) status new, is this bug uptodate? or fixed
> > with the other network-manager fix-released?
> >
> > --
> > Network manager says disconnected but is connected and working
> > https://bugs.launchpad.net/bugs/105234
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
>
> --
>
> Fábio Leitão, RCDD
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Regards

Douglas

[Alexander Sack (asac)]

i guess baltix target was an accident ... invalid.

[Mikael (fitmik)]

THIS BUG HAS BEEN FIXED A LONG TIME AGO NOW.

end of discussion.

2007/6/27, Alexander Sack <email address hidden>:
>
> i guess baltix target was an accident ... invalid.
>
> ** Changed in: network-manager (Baltix)
> Status: New => Invalid
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Mikael FITOUSSI

[Sebastien Wains (sebastienw-deactivatedaccount)]

I installed Gutsy this morning and have the problem (the system is up to date).

I'm on a wired connection, using DHCP (fixed IP bound to MAC address).

$ lsb_release -src
7.10
gutsy

$ uname -a
Linux m201 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux

$ dpkg -l network-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Nom Version Description
+++-======================-======================-============================================================
ii network-manager 0.6.5-0ubuntu9 network management framework daemon

[Brian Murray (brian-murray)]

Sebastien it would be helpful if you could open a new bug report about your specific issue and included the full output of 'sudo lspci -vvn', 'dmesg', '/var/log/daemon.log', 'sudo ethtool eth0' (where eth0 is the wired interface), and '/etc/network/interfaces'. Feel free to assign the bug report to me. Thanks in advance.

[Luka Renko (lure)]

Similar issue in bug 126494

[Sebastien Wains (sebastienw-deactivatedaccount)]

Requested info attached in bug report 126494

[PresuntoRJ (fabio-tleitao)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Fabio

Learn more:
https://www.linkedin.com/e/isd/411796717/qYmszuv5/

------------------------------------------

What is LinkedIn and why should you join?
http://learn.linkedin.com/what-is-linkedin/

------
(c) 2008, LinkedIn Corporation

[John Vivirito (gnomefreak)]

This is seen in Jaunty I will post additional information. reassigned to nobody in case Scott doesnt feel like working on it.

[John Vivirito (gnomefreak)]

here is a screenshot

[John Vivirito (gnomefreak)]

Output from sudo lspci -vvn and dmesg

[John Vivirito (gnomefreak)]

Here is /etc/network/interfaces

[John Vivirito (gnomefreak)]

Here is /var/log/daemon.log

[Nicola Ferralis (feranick)]

Confirmed in Intrepid:

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

[Nicola Ferralis (feranick)]

Changing to Confirmed since this bug has been confirmed for Intrepid and Jaunty.

[Alexander Sack (asac)]

this isnt critical. its a problem displaying connect status if you have unmanaged devices. I agree however, that the applet can be confusing, hence medium

[Andrea Marin (amarin)]

Hi all,

i have the same problem in my new fresh upgrade from 8.04 to 8.10
I have upgrade not from a CD, but online with update manager new release.

How can i help to resolve this?

Thanks for all your job.

[Daniele (daniele-levorato)]

Me too. Just upgraded from 7.10 to 8.04 and from 8.04 to 8.10.
Wired connection not detected. The applet says something (in italian) like it's an unmanaged device.
But connection is still working as it was configured in 7.10 ...

[ubu-for (ubu-for)]

I have the same problem with Jaunty Beta!

[Ebrahim (emakda)]

I am having the same problem after an update done today. Network Applet shows disconnected:(.

[Ari (ari-reads)]

I've been experiencing this problem for many months in my two ubuntu desktops. In the beginning I had unmanaged devices in /etc/network/interfaces; however I deleted all the manually configured stuff there, and networkmanager applet is still broken. I have wireless, and it doesn't show up.

I'm wondering if there a way to safely "reset" /etc/network/interfaces (or whatever config files the applet is looking at)

[Christoph Donges (cdonges)]

unsubscribe

On Wed, Apr 1, 2009 at 2:01 PM, Ari <email address hidden> wrote:

> I've been experiencing this problem for many months in my two ubuntu
> desktops. In the beginning I had unmanaged devices in
> /etc/network/interfaces; however I deleted all the manually configured
> stuff there, and networkmanager applet is still broken. I have wireless,
> and it doesn't show up.
>
> I'm wondering if there a way to safely "reset" /etc/network/interfaces
> (or whatever config files the applet is looking at)
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[zeddock (zeddock)]

Problem is appearing in Jaunty too.
zeddock

On Wed, Apr 1, 2009 at 12:12 AM, Christoph Donges <email address hidden> wrote:

> unsubscribe
>
> On Wed, Apr 1, 2009 at 2:01 PM, Ari <email address hidden> wrote:
>
> > I've been experiencing this problem for many months in my two ubuntu
> > desktops. In the beginning I had unmanaged devices in
> > /etc/network/interfaces; however I deleted all the manually configured
> > stuff there, and networkmanager applet is still broken. I have wireless,
> > and it doesn't show up.
> >
> > I'm wondering if there a way to safely "reset" /etc/network/interfaces
> > (or whatever config files the applet is looking at)
> >
> > --
> > Network manager says disconnected but is connected and working
> > https://bugs.launchpad.net/bugs/105234
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Mikael (fitmik)]

Im still having this problem in 9.04 too. And on 2 different computers: one based on the nforce4 chip and another "new" asus p5qpro.
Both use pppoe to connect to the internet.
Weird to see that has not been fixed. I have this bug since 2 years now!
Its not really important (only cosmetic) but its something (the disconnect icon) that you see 24/7 when you use your computer!

[Detlef Lechner (detlef-lechner)]

I have got the same error after dist-upgrading from 8.04.2 via 8.10 to 9.04.

[Detlef Lechner (detlef-lechner)]

My nm-applet icon is shown with a red square having a diagonal cross in it. Hovering over it the tooltip "No network connection" appears. After issuing the command 'sudo dhclient eth0' I have LAN access via eth0 but the nm-applet's look remains the same.
(If I de-assert System >Preferences > Network Manager and reboot, there will appear no nm-applet. But if I issue the command 'sudo dhclient eth0' I will have LAN access via eth0.)
Right-click in the nm-applet > Edit Connections... > Network Connections > Wired allows me to add an entry 'eth0' with the parameters 'MAC address=00:04:0E:6A:0C:C6' MTU=automatic, Address=164.168.178.24, Netmask=255.255.255.0 Gateway=0.0.0.0, 'DNS Servers=192.168.178.1' but this entry shows always a 'never' state report.

[sciuro (sciurognathi)]

Network Manager functionality is changed!
Read about it in /usr/share/doc/network-manager/README.Debian.

In short, if interface is (properly or not) configured in /etc/network/interfaces file, Network Manager will not manage it. If there are no other interfaces for NM to manage, NM thinks that there are no network connections.
You may try to comment out any configuration of eth0 in interfaces file, so network manager picks it up for management.

There is also solution to put NM in managed mode as mentioned in README.Debian.

[jerryb (gerald-britton)]

If what you say is true, then there is indeed no bug in Network
Manager. Rather, there is a serious design flaw. In no circumstance
should NM report that there are no active network connections when
indeed said connections are active and healty.

On Sun, Jun 7, 2009 at 6:17 AM, sciuro<email address hidden> wrote:
> Network Manager functionality is changed!
> Read about it in /usr/share/doc/network-manager/README.Debian.
>
> In short, if interface is (properly or not) configured in /etc/network/interfaces file, Network Manager will not manage it. If there are no other interfaces for NM to manage, NM thinks that there are no network connections.
> You may try to comment out any configuration of eth0 in interfaces file, so network manager picks it up for management.
>
> There is also solution to put NM in managed mode as mentioned in
> README.Debian.
>
> ** Changed in: network-manager-applet (Ubuntu)
>       Status: Triaged => Invalid
>
> ** Changed in: network-manager-applet (Ubuntu)
>     Assignee: (unassigned) => sciuro (sciurognathi)
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Gerald Britton

[jerryb (gerald-britton)]

The fact that NM is changed is interesting. The experience that it now reports no active network connections when indeed such connections exist and are active, means that the change is very much for the worse and reflects a serious design flaw.

I know that it is popular to wave the "functioning as designed!" flag, but when the design is so obviously incorrect, that is mere sophistry.

Fix it!

[memartin (memartin)]

I find it a disgrace that the bug is around for years now and is still present in Lucid beta.

When I plug my network in, the icon changes to the "working" state, hover says something like connecting. It sets up the connection (local DHCP) to work perfectly, yet the icon shows the plug and socket as separate (unplugged), while the hover says "connected". See the attached image. I second the opinion that there must be flaw hidden in that picture.

BTW: Interface eth0 is NOT at all configured in /etc/network/interfaces.

Thanks for having another look at it.

[Nizar Kerkeni (nizarus)]

@memartin : according to the screen shot your are using kubuntu, right ?

[Christoph Donges (cdonges)]

unsubscribe

On Sat, Apr 17, 2010 at 4:30 AM, Nizar Kerkeni <email address hidden> wrote:
> @memartin : according to the screen shot your are using kubuntu, right ?
>
> --
> Network manager says disconnected but is connected and working
> https://bugs.launchpad.net/bugs/105234
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[memartin (memartin)]

@nizar: Yes, that's right. Sorry for not making that clear in the post. I'm using Kubuntu Lucid beta on an IBM Thinkpad T42.
I've seen a few posts regarding Kubuntu here and thought it would be safe to share my voice. Of course, if the bug was in the NM Plasma-applet, this would be the wrong place to complain...

[Brian Murray (brian-murray)]

network-manager-applet displays the connectivity state of network-manager's managed interfaces not every interface. So the title "network manager says disconnected but is connected and working" is actually misleading. The interface is connected and working but not from network-manager's point of view since it is not managing the interface.

Additionally, in Lucid now network-manager applet displays nothing now for non-managed interfaces so is less misleading. You can check to see whether or not an interface is managed by network-manager by using the command line too nm-tool. You'll see "State: unmanaged" for unmanaged interfaces.

[memartin (memartin)]

@Brian: Here's my output of nm-too (as user)l:

----
NetworkManager Tool

State: connected

** (process:4950): WARNING **: <WARN> get_one_connection(): error: invalid connection: 'NMSettingGsm' / '(null)' invalid: 3

** (process:4950): WARNING **: <WARN> get_one_connection(): error: invalid connection: 'NMSettingWireless' / 'mac-address' invalid: 1

- Device: eth0 [Auto eth0] ----------------------------------------------------
  Type: Wired
  Driver: e1000
  State: connected
  Default: yes
  HW Address: 00:11:25:80:CE:04

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

  Wired Properties
    Carrier: on

  IPv4 Settings:
    Address: 10.1.44.69
    Prefix: 24 (255.255.255.0)
    Gateway: 10.1.44.254

    DNS: 10.1.44.254

- Device: eth1 -----------------------------------------------------------------
  Type: 802.11 WiFi
  Driver: airo
  State: disconnected
  Default: no
  HW Address: 00:0E:9B:8C:B5:91

  Capabilities:

  Wireless Properties
    WEP Encryption: yes

  Wireless Access Points
   <snipped>

----

While nm-tool reports the wired LAN as connected, the plasma applet shows no change to what I reported previously. The icon shows disconnected state, mouse hover over the icon says "connected". This is with Kubuntu Lucid beta with all recent upgrades.

I understand that from your point of view everything is "working as expected". Yet, what I (and supposedly other users) see in their GUI is flawed.

Is there a possibility for you to push the bug to a more appropriate project where you would assume the error to come from? Or I'd gladly contribute to a bug elsewhere if someone could help me find it.

TIA, Martin

[FiReSTaRT (dlyh)]

Just to make a note that it's still happening with stable Lucid64. Worked fine for a while, but now it's broken. Sometimes, rebooting helps, but these days even that's not a guaranteed fix.

[Brian Murray (brian-murray)]

@memartin your bug, which should be a new one by the way, either needs to be reported about plasma-widget-networkmanagement or network-manager-kde depending on which one you have installed.