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

Bug #1195472 reported by Barra
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager-control-center 0.9.4-0ubuntu6.1
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
Date: Thu Jun 27 23:11:30 2013
Disassembly: => 0x10: Cannot access memory at address 0x10
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-06-27 (0 days ago)
InstallationMedia:

MarkForUpload: True
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x10: Cannot access memory at address 0x10
 PC (0x00000010) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 ?? ()
 gee_array_list_construct () from /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2
 gee_array_list_new () from /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2
 alm_history_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 gee_array_list_construct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Barra (barra78) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 gee_array_list_construct (object_type=<optimized out>, g_type=g_type@entry=64, g_dup_func=g_dup_func@entry=0x7fd559ea3000 <g_strdup>, g_destroy_func=g_destroy_func@entry=0x7fd559e8bc40 <g_free>, equal_func=equal_func@entry=0x0, equal_func_target=equal_func_target@entry=0x7fd55c750a50, equal_func_target_destroy_notify=equal_func_target_destroy_notify@entry=0x10) at arraylist.c:555
 gee_array_list_new (g_type=64, g_dup_func=0x7fd559ea3000 <g_strdup>, g_destroy_func=0x7fd559e8bc40 <g_free>, equal_func=0x0, equal_func_target=0x7fd55c750a50, equal_func_target_destroy_notify=0x10) at arraylist.c:581
 alm_history_widget_construct (object_type=<optimized out>) at history-widget.c:302
 alm_history_widget_new () at history-widget.c:326

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 activity-log-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in activity-log-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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