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

Bug #1200922 reported by Tony Themelis
304
This bug affects 58 people
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Testing Mir.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Jul 13 09:01:51 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-07-13 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd2f6079fec <g_type_check_instance_cast+28>: mov (%rax),%rdi
 PC (0x7fd2f6079fec) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Tony Themelis (tony-athemelis) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x7fd2f8b727a0, iface_type=140544096999088) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:4008
 on_properties_changed (interface=0x7fd2f8fd8cd0, changed_properties=<optimized out>, invalidated_properties=<optimized out>, user_data=0x7fd2f8b727a0) at diagnostics-widget.c:149
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff872a0320, fn=0x7fd2cfe36850 <on_properties_changed>, rvalue=0x7fff872a0290, avalue=avalue@entry=0x7fff872a0230) at ../src/x86/ffi64.c:522
 g_cclosure_marshal_generic (closure=0x7fd2f8f595e0, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454

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
Jeremy Bícha (jbicha)
information type: Private → Public
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
Revision history for this message
Manish Sinha (मनीष सिन्हा) (manishsinha) wrote :

Evan, can you look into this. Looks like some issue with signals in diagnostic widget

on_properties_changed (interface=0x7fd2f8fd8cd0, changed_properties=<optimized out>, invalidated_properties=<optimized out>, user_data=0x7fd2f8b727a0) at diagnostics-widget.c:149

Revision history for this message
Randy Allen (rcallen7957) wrote :

Fresh install. No added software. Fully updated. Had just unlocked diagnostics for reports to be sent.

Unbutu 13.10
Memory 7.8 GiB
Processor Intel Core i7 CPU Q 820 @ 1.73 GHz x 8
Graphics Gallium 0.4 on NVAS
OS type 64-bit
Disk 150.3 GB

Hope this helps.

tags: added: bugpattern-needed
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.