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

Bug #936312 reported by piotrekw1
78
This bug affects 16 people
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

after kernel actualisation

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
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 19 16:54:06 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0554f5c175 <g_type_check_instance+21>: mov (%rax),%rdi
 PC (0x7f0554f5c175) ok
 source "(%rax)" (0x0000070b) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libactivity-log-manager.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to precise on 2012-02-17 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
piotrekw1 (piotrekw1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=0x7f0558da26c0) at /build/buildd/glib2.0-2.31.16/./gobject/gtype.c:4072
 g_signal_emit_by_name (instance=0x7f0558da26c0, detailed_signal=0x7f0545a29255 "folder-added") at /build/buildd/glib2.0-2.31.16/./gobject/gsignal.c:3115
 alm_path_blacklist_on_blacklist_added (ev=<optimized out>, blacklist_id=<optimized out>, self=0x7f0558da26c0) at files-widget.c:767
 _alm_path_blacklist_on_blacklist_added_alm_blacklist_template_added (_sender=<optimized out>, blacklist_id=<optimized out>, blacklist_template=<optimized out>, self=0x7f0558da26c0) at files-widget.c:628
 g_closure_invoke (closure=0x7f0558da4ea0, return_value=0x0, n_param_values=3, param_values=0x7f050400ad90, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.16/./gobject/gclosure.c:774

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
Jeremy Bícha (jbicha)
information type: Private → Public
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.