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

Bug #1220338 reported by Shaharil Ahmad
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash upon opening bluetooth option.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Wed Sep 4 00:50:50 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-07-12 (53 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f86ad97126c <g_type_check_instance_cast+28>: mov (%rax),%rdi
 PC (0x7f86ad97126c) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to saucy on 2013-08-24 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers video

Revision history for this message
Shaharil Ahmad (shaharil-ahmad) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1200922, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.