NetworkManager crashed with SIGSEGV in nl_addr_get_prefixlen()

Bug #279652 reported by Lei Shi
8
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: network-manager

I started ubuntu 8.10, did nothing ...and then the bug appears and the bug crash reporter asked to to report it.
Byt the way, the Internet is still usable.

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

IfupdownConfig:
 auto lo
 iface lo inet loopback
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_prefixlen () from /usr/lib/libnl.so.1
 ?? () from /usr/lib/libnl.so.1
 rtnl_route_add () 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_prefixlen()
Uname: Linux 2.6.27-5-generic i686
UserGroups:

WpaSupplicantLog:

Tags: apport-crash
Revision history for this message
Lei Shi (robustness) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:build_route_msg (tmpl=0x95aff20, cmd=24, flags=1024)
rtnl_route_add (handle=0x95a12a0, route=0x95aff20, flags=0)
nm_system_device_set_from_ip4_config (
nm_device_set_ip4_config (self=0x95a5860, config=0x95a8560,
dhcp_state_changed (dhcp_manager=0x959c020,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in network-manager:
importance: Undecided → Medium
Revision history for this message
LostinSpacetime (lostinspacetime) wrote :

Same here.. Ubuntu 8.10, fresh install. NetworkManager crashed at bootup and in order to have internet acces I had to start in manually (sudo NetworkManager). It happens pretty often, about every 2nd time. It might be possible, that the problem appeared after the last kernel update.

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.