nm-applet thinks it's connected to the wired network, when it's connected to the wireless network

[Martijn vdS]

I've jsut upgraded my gutsy machine, and after a reboot nm-applet told me it was connected to the wired network. This is a bit strange, as the machine doesn't even have a wired network connection.

The wireless connection did work.

After disabling all networking, re-enabling it and manually selecting my wireless network, it gets reported properly.

One of the weird things was that both the "Wired network" and my wireless network had a selected radio button in the nm-applet menu.

[nanotube (nanotube)]

I had the same thing happen to me on my feisty box a couple of times. It seemed to be happening after a few suspend/resume cycles. restarting all nm-related services and restarting them fixed the problem....

[Sam Peterson (peabodyenator)]

I can confirm this as well. I experienced it several times in Gutsy. The work around for me was to disable roaming for my wired network. That was an okay solution for me because I use wireless almost exclusively for connecting to the Internet.

[Martijn vdS (martijn)]

I've never had this since my intial report.

[Anthony Borrow (arborrow)]

I am running Ubuntu 8.04 on a Dell XPS M1330. After suspend I have restart all the networking stuff (rmmod iwl3945, modprobe, and do a networking restart via a dbus/resume.d/ script. In any case, it re-establishes the wireless connection just fine but the nm-applet does not show that it is connected because it switches from looking at wlan0 to eth0. If I kill the nm-applet and restart it then it finds wlan0 just fine. Any suggestions as to the root cause or what I can do to not have to kill the nm-applet? Thanks - Anthony

[Anthony Borrow (arborrow)]

p.s. I would be happy to do any testing or share configuration information - just let me know what you would like to see.

[Alexander Sack (asac)]

This should be fixed since nm 0.7. If you still see this please reopen.

[Jānis Kangarooo (kangarooo)]

if its fixed then no need to put as invalid

[monochromec (monochromec)]

This bug (or a similar one) surfaced in version 1.1.93-1ubuntu1 once again. Work-around: restart nm-applet after resume as within user desktop session.

[monochromec (monochromec)]

PS: nm-applet shows the following error message: "(nm-applet:563): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed"