gnome-control-center crashed with SIGSEGV in g_str_hash()

Bug #854231 reported by Martin Schaaf
104
This bug affects 22 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 19 22:43:51 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: gnome-control-center --overview
ProcCwd: /home/ms
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbc11763ea0 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7fbc11763ea0) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.29.90/./glib/gstring.c:142
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x7fbc162aa700) at /build/buildd/glib2.0-2.29.90/./glib/ghash.c:360
 g_hash_table_lookup (hash_table=0x7fbc162aa700, key=0x0) at /build/buildd/glib2.0-2.29.90/./glib/ghash.c:1022
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
Title: gnome-control-center crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 19.92-0ubuntu1
 empathy 3.1.91-0ubuntu2
 gnome-bluetooth 3.1.4-0ubuntu2
 indicator-datetime 0.2.95-0ubuntu1

Revision history for this message
Martin Schaaf (mascha) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (4.5 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for x11-xkb-utils: package version 7.6+4 dbgsym version 7.6+2
outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
libgnome-menu-3-0 version 3.1.90-0ubuntu1 required, but 3.1.92-0ubuntu1 is available
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
lsb-base version 4.0-0ubuntu15 required, but 4.0-0ubuntu16 is available
libgnome-control-center1 version 1:3.1.91-0ubuntu8 required, but 1:3.1.92-0ubuntu1 is available
outdated debug symbol package for consolekit: package version 0.4.5-1 dbgsym version 0.4.4-1
outdated debug symbol package for libnih1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
libcolord1 version 0.1.11-1ubuntu2 required, but 0.1.12-1ubuntu2 is available
gnome-control-center version 1:3.1.91-0ubuntu8 required, but 1:3.1.92-0ubuntu1 is available
outdated debug symbol package for libslang2: package version 2.2.4-2ubuntu1 dbgsym version 2.2.2-4ubuntu2
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libproxy0: package version 0.3.1-2ubuntu6 dbgsym version 0.3.1-2ubuntu5
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu1 dbgsym version 3.12-1ubuntu6
gnome-settings-daemon version 3.1.91-0ubuntu5 required, but 3.1.92-0ubuntu1 is available
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libgstreamer-plugins-base0.10-0: package version 0.10.35-1 dbgsym version 0.10.32-1ubuntu5
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
nautilus-data version 1:3.1.90-0ubuntu3 required, but 1:3.1.92-0ubuntu2 is available
libglib2.0-0 version 2.29.90-0ubuntu2 required, but 2.29.92-0ubuntu1 is available
outdated debug symbol package for libck-connector0: package version 0.4.5-1 dbgsym version 0.4.4-1
initramfs-tools-bin version 0.99ubuntu4 required, but 0.99ubuntu5 is available
gnome-desktop3-data version 3.1.91-0ubuntu1 required, but 3.1.92-0ubuntu1 is available
libgnome-desktop-3-2 version 3.1.91-0ubuntu1 required, but 3.1.92-0ubuntu1 is available
plymouth version 0.8.2-2ubuntu25 required, but 0.8.2-2ubuntu26 is available
outdated debug symbol package for libxslt1.1: package version 1.1.26-7 dbgsym version 1.1.26-6build1
outdated debug symbol package for procps: package v...

Read more...

tags: removed: need-amd64-retrace
Revision history for this message
Michael DePaulo (mikedep333) wrote :

I believe I just experienced this same bug with up to date packages.
It happened when I went to open "User Accounts".
I've marked this as new.

Changed in gnome-control-center (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could be bug #841280

Revision history for this message
dysonsphere (dysonsphere23) wrote :

happened to me as well when trying to access user account settings

ubuntu 11.10
updated this morning (oct 06) just before the crash.

Revision history for this message
Michael DePaulo (mikedep333) wrote :

I've attached the gdb backtrace.

I'm not sure if I'm supposed to reopen this bug or not.

I noticed this:
um_password_dialog_new () at um-password-dialog.c:690
690 um-password-dialog.c: No such file or directory.
        in um-password-dialog.c

Changed in gnome-control-center (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

thanks michael, your stacktrace might be a different bug, could you send it using ubuntu-bug on the apport generated file?

Revision history for this message
Michael DePaulo (mikedep333) wrote :

I'll do that when I get home at around 23:00 UTC; thanks Sebastian!

Revision history for this message
Michael DePaulo (mikedep333) wrote :

I had to figure out how to use ubuntu-bug on the .crash file (because it wasn't prompting to file a bug when it crashes anymore), but I believe I followed your instructions to create bug 870435 .
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/870435

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing that bug since a new one got reported using apport

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