MASTER nm-system-settings crashed with SIGSEGV in strlen()

Bug #341688 reported by Yuri Nikiforov on 2009-03-12
174
This bug affects 26 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
High
Unassigned
Lucid
High
Unassigned
Natty
High
Unassigned
Oneiric
High
Unassigned
Precise
High
Unassigned

Bug Description

Binary package hint: network-manager

crashed when i connected mobile phone

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/nm-system-settings
Gconf:

NonfreeKernelModules: nvidia
Package: network-manager 0.7.1~rc3-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
ProcEnviron:

Signal: 11
SourcePackage: network-manager
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libglib-2.0.so.0
 g_key_file_set_string_list () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_cclosure_marshal_VOID__POINTER ()
Title: nm-system-settings crashed with SIGSEGV in strlen()
Uname: Linux 2.6.28-9-generic i686
UserGroups:

WpaSupplicantLog:

Yuri Nikiforov (nikiforov2000) wrote :

StacktraceTop:strlen () at ../sysdeps/i386/i486/strlen.S:69
g_key_file_parse_string_as_value (key_file=0xe8,
IA__g_key_file_set_string_list (key_file=0x9278d40,
default_wired_deleted (wired=0x9288720, mac=0x9279380,
IA__g_cclosure_marshal_VOID__POINTER (closure=0x929e880,

Changed in network-manager:
importance: Undecided → Medium

what is in your /etc/network/interfaces?

summary: - nm-system-settings crashed with SIGSEGV in strlen()
+ MASTER nm-system-settings crashed with SIGSEGV in strlen()
Changed in network-manager (Ubuntu):
importance: Medium → High
status: New → Triaged

Alexander Sack ha scritto:
> what is in your /etc/network/interfaces?
>

auto lo
iface lo inet loopback

thaks in advance
Lorenzo

Rolf Leggewie (r0lf) wrote :

a common occurrence and trigger seems to be people editing network connections.

tags: added: iso-testing

I think this has been largely fixed since Oneiric. Anyone having this issue regularly could confirm whether it can be reproduced and on what release?

Tentatively I'm closing this as Fix Released for Oneiric and Precise, and leaving Lucid & Natty as Incomplete until it can be confirmed whether this happens in either of those releases.

If it can be reproduced on Oneiric or Precise, please feel free to set it back to New for that release.

Changed in network-manager (Ubuntu Precise):
status: Triaged → Fix Released
Changed in network-manager (Ubuntu Natty):
importance: Undecided → High
Changed in network-manager (Ubuntu Lucid):
importance: Undecided → High
Changed in network-manager (Ubuntu Oneiric):
status: New → Fix Released
Changed in network-manager (Ubuntu Lucid):
status: New → Incomplete
Changed in network-manager (Ubuntu Natty):
status: New → Incomplete
Changed in network-manager (Ubuntu Oneiric):
importance: Undecided → High
dino99 (9d9) wrote :

eol reached https://wiki.ubuntu.com/Releases

Lucid does not seems to be affected since a long time.

Changed in network-manager (Ubuntu Natty):
status: Incomplete → Invalid
Changed in network-manager (Ubuntu Lucid):
status: Incomplete → Fix Released
To post a comment you must log in.