Ubuntu
network-manager package

nm-system-settings crashed with SIGSEGV in strlen() when editing usb network connection

Bug #360893 reported by Erik B. Andersen on 2009-04-14

This bug report is a duplicate of: Bug #341688: MASTER nm-system-settings crashed with SIGSEGV in strlen(). Edit Remove

18

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Binary package hint: network-manager

I connected my computer to my router via usb. It worked fine. I selected the usb connection and clicked on edit. I went to the IPv4 tab and changed the address to a static address. When I click apply it says, "Message did not receive a reply (timeout by message bus)". Then the bug reporter pops up. It seems to apply the configuration changes though. Please tell me if there is any more information you need.

Description: Ubuntu jaunty (development branch)
Release: 9.04

network-manager:
  Installed: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Version table:
*** 0.7.1~rc4.1.cf199a964-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

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

IfupdownConfig:
auto lo
iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu1
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/libc.so.6
?? () from /usr/lib/libglib-2.0.so.0
g_key_file_set_string_list ()
?? ()
g_closure_invoke ()
Title: nm-system-settings crashed with SIGSEGV in strlen()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

WpaSupplicantLog:

Tags:

Revision history for this message

Erik B. Andersen (azendale) wrote on 2009-04-14:

#1

Screenshot-7.png Edit (266.4 KiB, image/png)
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (768 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (1.1 KiB, text/plain; charset="utf-8")
NetDevice.eth2.txt Edit (1.6 KiB, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
NetDevice.pan0.txt Edit (3.3 KiB, text/plain; charset="utf-8")
NetDevice.vboxnet0.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (14.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (727 bytes, text/plain; charset="utf-8")
Registers.txt Edit (915 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Syslog.txt Edit (29.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-14: Stacktrace.txt (retraced)

#2

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

StacktraceTop:strlen () at ../sysdeps/x86_64/strlen.S:48
g_key_file_parse_string_as_value (
IA__g_key_file_set_string_list (key_file=0xa91c50,
default_wired_deleted (wired=0xaac080,
IA__g_closure_invoke (closure=0xa8c440,

Revision history for this message

Apport retracing service (apport) wrote on 2009-04-14: ThreadStacktrace.txt (retraced)

#3

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

Changed in network-manager (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Alexander Sack (asac) wrote on 2009-04-15:

#4

do you have any way to reproduce this crash? Can you provide step by step instructions?

Changed in network-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Erik B. Andersen (azendale) wrote on 2009-04-16:

#5

Well I can reliably get it to say it has crashed on my computer. Here is what I did:

1. Plug in USB cord to router. (I have an Actiontec GT701-WG)
2. Right click on network manager applet and select Edit Connections.
3. Choose the USB network connection (eth2 in my case) and click Edit.
4. Go to the IPv4 Settings Tab and set the Method to Manual.
5. Click add and enter Address, Netmask and Gateway.
6. Enter DNS servers.
7. Click apply.
8. Network Manager connection editing window stays open, but a message pops up saying, "Did not receive a reply (timeout by message bus)", an ubuntu notification says something like connection updated (which is true), and an ubuntu notification says a crash report was detected.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #341688 Remove

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.