[keyboard]: gnome-control-center crashed with SIGSEGV in g_strdup()

Bug #1232566 reported by Anna Glasgall
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I opened gnome-control-center on the Saucy final beta and it crashed with the above error. Backtrace and other apport data attached.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu39
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sat Sep 28 17:24:25 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-01-03 (268 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: gnome-control-center keyboard
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb65ee5d5f1 <__strlen_sse2_pminub+17>: movdqu (%rdi),%xmm1
 PC (0x7fb65ee5d5f1) ok
 source "(%rdi)" (0xffffffff0000000a) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
Title: [keyboard]: gnome-control-center crashed with SIGSEGV in g_strdup()
UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare sbuild src sudo
usr_lib_gnome-control-center:
 activity-log-manager 0.9.7-0ubuntu4
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-datetime 13.10.0+13.10.20130924.2-0ubuntu1
 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1

Revision history for this message
Anna Glasgall (aglasgall) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_strdup (str=0xffffffff0000000a <Address 0xffffffff0000000a out of bounds>) at /build/buildd/glib2.0-2.38.0/./glib/gstrfuncs.c:363
 value_collect_string (value=0x7fff90d23b00, n_collect_values=<optimized out>, collect_values=<optimized out>, collect_flags=<optimized out>) at /build/buildd/glib2.0-2.38.0/./gobject/gvaluetypes.c:293
 g_object_set_valist (object=object@entry=0x35b6a80, first_property_name=first_property_name@entry=0x7fb62c2ca37b "editable", var_args=var_args@entry=0x7fff90d23bc8) at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c:2116
 g_object_set (_object=_object@entry=0x35b6a80, first_property_name=first_property_name@entry=0x7fb62c2ca37b "editable") at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c:2232
 description_set_func (tree_column=<optimized out>, cell=0x35b6a80, model=<optimized out>, iter=<optimized out>, data=<optimized out>) at keyboard-shortcuts.c:773

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.