NetworkManager crashed with SIGSEGV in nl_addr_get_len()

Bug #279303 reported by Graham Inggs
26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

After upgrading from Alpha 6 to Beta, then downloading the latest updates and then restarting, NetworkManager crashed immediately after I logged in.
I am able to ping other machines on my network, but am unable to resolve DNS names.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

NonfreeKernelModules: nvidia
Package: network-manager 0.7~~svn20081004t225044-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nl_addr_get_len () from /usr/lib/libnl.so.1
 ?? () from /usr/lib/libnl.so.1
 rtnl_route_del () from /usr/lib/libnl.so.1
 nm_system_device_set_from_ip4_config ()
 nm_device_set_ip4_config ()
Title: NetworkManager crashed with SIGSEGV in nl_addr_get_len()
Uname: Linux 2.6.27-5-generic x86_64
UserGroups:

WpaSupplicantLog:

Revision history for this message
Graham Inggs (ginggs) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Alexander Sack (asac) wrote :

do you know how to reproduce? if so, please follow instructions at https://wiki.ubuntu.com/DebuggingNetworkManager#Debugging%20Crashes

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Graham Inggs (ginggs) wrote :

I'll see if I'm able to reproduce the fault. It seems my network configuration got mangled during the upgrade. Network Manager was displaying the name of my wired network connection (eth3) as "ifupdown eth2".

Revision history for this message
Rani Hod (raenye) wrote :

This just happened twice to me. I wasn't doing anything particular when the "report crash" pop-up came up.

I was connected to a WPA-protected AP.
iwconfig still showed me as connected, but DNS and HTTP didn't work.

Workaround:
sudo /etc/init.d/NetworkManager restart

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

Other bug subscribers

Remote bug watches

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