Ubuntu
network-manager package

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)	Fix Released	High	Unassigned
	Lucid	Fix Released	High	Unassigned
	Natty	Invalid	High	Unassigned
	Oneiric	Fix Released	High	Unassigned
	Precise	Fix Released	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:

Tags:

Revision history for this message

Yuri Nikiforov (nikiforov2000) wrote on 2009-03-12:

#1

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (736 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (1.0 KiB, text/plain; charset="utf-8")
NetDevice.eth1.txt Edit (1.0 KiB, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (3.1 KiB, text/plain; charset="utf-8")
NetDevice.pan0.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (9.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (723 bytes, text/plain; charset="utf-8")
Registers.txt Edit (467 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Syslog.txt Edit (153.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-12: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (7.5 KiB, text/plain)

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,

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-12: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (7.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-12: Stack trace with source code

#4

StacktraceSource.txt Edit (1.8 KiB, text/plain)

Changed in network-manager:
importance:	Undecided → Medium

Revision history for this message

Alexander Sack (asac) wrote on 2009-03-30: Re: nm-system-settings crashed with SIGSEGV in strlen()

#5

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

Revision history for this message

Lorenzo (lorped) wrote on 2009-03-31: Re: [Bug 341688] Re: nm-system-settings crashed with SIGSEGV in strlen()

#6

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

auto lo
iface lo inet loopback

thaks in advance
Lorenzo

Revision history for this message

Rolf Leggewie (r0lf) wrote on 2010-09-13:

#7

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

Ubuntu QA Website (ubuntuqa) on 2010-09-13

tags:

added: iso-testing

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2012-04-25:

#8

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

Revision history for this message

dino99 (9d9) wrote on 2013-05-10:

#9

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

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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