Ubuntu
activity-log-manager package

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

Bug #940865 reported by ABorland on 2012-02-25

14

This bug affects 2 people

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

Bug Description

Something wrong

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: activity-log-manager-control-center 0.9.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Wed Feb 22 08:58:47 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
ProcCmdline: gnome-control-center
SegvAnalysis:
Segfault happened at: 0x7fabd5a8a8f0 <g_str_hash>: movzbl (%rdi),%edx
PC (0x7fabd5a8a8f0) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/libgee.so.2
?? () from /usr/lib/libgee.so.2
alm_files_widget_construct () from /usr/lib/control-center-1/panels/libactivity-log-manager.so
alm_activity_log_manager_construct () from /usr/lib/control-center-1/panels/libactivity-log-manager.so
Title: gnome-control-center crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

ABorland (avostrikov) wrote on 2012-02-25:

#1

Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (848 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (126 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (98.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (773 bytes, text/plain; charset="utf-8")
Registers.txt Edit (839 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (7.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-25:

#2

StacktraceTop:
g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.18/./glib/ghash.c:1730
gee_hash_map_lookup_node (self=0x7fabd98ca4d0, key=0x0) at hashmap.c:951
gee_hash_map_real_set (base=0x7fabd98ca4d0, key=0x0, value=0x1) at hashmap.c:1109
alm_files_widget_add_folder_to_view (self=0x7fabd5ab4070, folder=0x7fabd5a9fcf0 "H\205\377t\vH\213\005TM*") at files-widget.c:2272
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-25: Stacktrace.txt

#3

Stacktrace.txt Edit (2.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-25: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (11.4 KiB, text/plain)

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-04-02:

#5

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

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

Revision history for this message

Rick Spencer (rick-rickspencer3) wrote on 2012-04-02:

#6

Repro steps
1. open a terminal
2. type "sudo gnome-control-center"
3. click privacy settings

result: crash
expected: runs with root privledges

Jeremy Bícha (jbicha) on 2013-06-09

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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