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

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

Bug Description

ubuntu 13.10
3.11.0.6

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
Uname: Linux 3.11.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Sep 10 20:06:42 2013
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1378742723
InstallationDate: Installed on 2013-01-09 (243 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcCwd: /home/patricia
SegvAnalysis:
 Segfault happened at: 0xa64634ef: mov 0x0(%ebp),%eax
 PC (0xa64634ef) ok
 source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: Upgraded to saucy on 2013-02-15 (207 days ago)
UserGroups: audio fuse lp netdev plugdev sudo

Revision history for this message
fripounet (orgy) 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 #1223506, 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-i386-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.