NetworkManager crashed with SIGABRT in raise()

It's the first time I see this particular crash. Do you remember what was happening at the time?

I'll process the apport hook separately, and should be able to actually fix that in the next upload.

This was the first login after a reboot, following apt-get dist-update on Natty.

Thanks, testing the upgrade here now.

FWIW, bug 654900 is about the crashes in the apport script, and it should be good (just need to test it some more here before I upload)

Are you still seeing this crash? I've been unable to reproduce it; I suggest closing the bug report until it can be pinpointed to a clear cause (or when we get a report that can be retraced, which should be much easier now that the hook is unbroken).

http://pastebin.ubuntu.com/565521/

It seems normal without looking at your config that NM sets the IP to 10.42.43.x, which is used for internet connection sharing (see the connection's settings, under IPv4 or IPv6 tab). You can disable this by running nm-connection-editor manually if you can't access nm-applet.

But now, from our discussion it seems nm-applet is running but not shows in indicator-applet? Could you verify that indicator-applet is indeed added to the panel if you're in a classic GNOME session?

I'd be curious to see if NM is running at the time too; the last logs you added don't indicate any kind of crash. I'm more and more suspecting that this particular crash shows up whenever you restart your computer, and actually caused by NM failing to assert the presence of the dbus bus on shutdown (maybe it gets stopped before NM). There is an upstream commit supposed to fix this, and I'm planning on releasing that shortly.

Hi Mathieu,

This doesn't quite match the behavior I've seen. Observable behavior is this:

When I first log in after a reboot, I see the nm applet and the little pulsing volcano lines, then it connects to my ap, does its dhcp and gives me the correct ip address. I can access my network just fine. Then after a while, the applet simply disappears and there's no other indication of a problem, except that ifconfig will show that the ip address has reverted to the 10. address.

Now the thing is that this "applet disappearing act" can happen at different times. Sometimes the applet (and proper ip address) can stay up for hours after first login after reboot. Other times, it goes away almost immediately. In all cases though I do see the notification popup that it's connected to the proper ssid. Just sometimes the applet crashes immediately and sometimes it stays up for minutes or hours. I haven't correlated the applet crash to any specific system or network activity. Usually the machine is just sitting there idle when the applet crashes.

Note that once the applet has crashed, nothing short of a reboot will revive the wireless connection.

I am in the classic (no effects) gnome session because unity and compiz have had some severe problems lately. I see some updates to compiz have landed, so I'll plug in a wired ethernet (which *always* works, even when the applet has crashed), do an update, reboot and see what that side looks like.

I'm of course happy to help debug or investigate in any way that's helpful. Feel free to ping me on irc again.

I marked your related bug for nm-applet as a duplicate of this one and added a task for network-manager-applet.

Could you attach .xession-errors to this bug report and run apport-collect 710711? If your network-manager package is up to date, the apport hook at least should be fixed and attach logs and everything needed to debug.

I rebooted to OS X and it is having trouble connecting to the wireless network, so I'm now suspecting a hardware problem on the laptop. Until I can verify that OS X 10.6.6 can connect successfully and Ubuntu cannot, I will leave this bug marked as incomplete.

Apologies for the (possible) false alarm.

I have more information. The wireless card is working just fine under both OS X and Ubuntu. However, when I attempt to enable bluetooth on Ubuntu (Natty), it crashes the wireless card and only a reboot to OS X (twice, for some reason) will re-enable the wireless card.

Oh yeah, bluetooth works fine when the laptop is booted under OS X.

I guess that's good-ish news for you :)

Please enable bluetooth and run 'rfkill list', then report back with the results on this bug.

Actually, I'm now very confused about what's going on with bluetooth under Natty.

When I click on the bluetooth icon (which btw is dimmed), it says:

Bluetooth on <- menu item disabled
Turn off Bluetooth
-----
Preferences

and when I click on Preferences, I get a window that says "Bluetooth is disabled" and a big button that says "Turn On Bluetooth". Clicking on this button just hangs the application apparently, and yep, crashes the wifi.

Without clicking the Evil Button, I get this result:

% rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

Well crap. It just happened again while the machine was idle under Natty. applet crashed, disconnected me from the wireless, and then I saw a notification pop up that says it re-connected to the ssid. However, the applet is gone and the wlan0 is reverted to the 10. private address. :(

I still have no idea why NM-applet would crash like this, or why it sets the IP to 10.42.43.0 (which is usually used for connection sharing).

I should have asked long ago, but could you please run 'apport-collect 710711' to add the information from NetworkManager on this bug? With this it should be possible to confirm the config and at least why it corrupts the IP address. Thanks.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Looks like you've got an Atheros AR5001 WLAN card, and the ath5k driver is having issues.

Your kernel log is full of the following error messages for *all* channels:

Feb 22 10:02:01 snowdog kernel: [ 824.761738] ath5k phy0: gain calibration timeout (2437MHz)

Thanks Tony, yep I see that too. Note that the apport upload was done while the wireless card was crashed (i.e. over eth0). Let me see if I can capture the data during the small window where the wlan0 is up.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Sidnei da Silva suggests that the 2.6.38-2 kernel was pretty flaky for him too, but that 2.6.38-4 is more stable. I've just upgraded, so we'll see!

The 2.6.38-4 kernel seems more -- but not completely -- stable. The wireless connection still crashed, with the 10. IP assignment. Now the nm-applet continually flashes between "ssid connection established" and "ssid disconnected", however at no time (now that it's crashed) does the correct wireless IP actually get assigned.

The problem is not in NetworkManager, NM just keeps up wired with no problem and doesn't react badly when nm-applet is not running.

Closing as Invalid, seems this was a configuration issue of some sort -- behavior was consistant with IP settings at "Shared" (which sets IP to 10.42.43.0 and does iptables magic to share Internet).

Barry, please don't hesitate to reopen this bug or file a new one if you see that nm-applet sets a connection to IPv4 "shared" with no apparent reason.

I think it would be a good idea to report wireless issues that need to be worked around with a reboot as a separate bug against the 'linux' package if you notice it again.

My bug is in 11.10. I haven't been able to connect to the wireless network at all in Oneiric, and my settings are identical to those in 11.04.

From my own experience as a user I am not so sure about this being a bug because what is really going on is that I keep losing my wi-fi connection. But this also happens to me under XP and Win8 at this same location, with the same router.