nm-connection-editor crashed with SIGSEGV in gtk_button_set_label()

Bug #438564 reported by Ralf Hildebrandt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

I changed the settings for the wireless network and added "all users may use this connection" (or what it's called in English). After that I encountered the crash...

ProblemType: Crash
Architecture: amd64
Date: Tue Sep 29 09:10:20 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-connection-editor
IpRoute:
 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.30 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.178.1 dev wlan0 proto static
Package: network-manager-gnome 0.8~a~git.20090923t220421.1ac8ffd-0ubuntu4
ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7f313b2e8965: mov 0x58(%rax),%rdi
 PC (0x7f313b2e8965) ok
 source "0x58(%rax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_button_set_label ()
 ?? ()
 ?? ()
 ?? ()
Title: nm-connection-editor crashed with SIGSEGV in gtk_button_set_label()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #436109, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.