gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
activity-log-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
SYSTEM INFORMATION
Running Ubuntu Linux, the Ubuntu 13.10 (saucy) release.
GNOME: 3.8.3 (Ubuntu 2013-07-22)
Kernel version: 3.11.0-4-generic (#9-Ubuntu SMP Mon Aug 26 15:22:48 UTC 2013)
GCC: 4.8 (i686-linux-gnu)
Xorg: 1.14.2.901 (1.14.3 RC 1) (29 August 2013 12:04:55PM) (29 August 2013 12:04:55PM)
Hostname: patricia-desktop
Uptime: 0 days 0 h 9 min
NVIDIA GRAPHIC CARD INFORMATION
Model name: unknown
Card Type: unknown
Video RAM: unknown
GPU Frequency: unknown
Driver version: NVIDIA UNIX x86 Kernel Module 319.32 Wed Jun 19 15:20:44 PDT 2013
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-
ProcVersionSign
Uname: Linux 3.11.0-4-generic i686
NonfreeKernelMo
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Aug 30 07:39:33 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-01-09 (232 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
MarkForUpload: True
ProcCmdline: gnome-control-
SegvAnalysis:
Segfault happened at: 0xa64884ef: mov 0x0(%ebp),%eax
PC (0xa64884ef) 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-
StacktraceTop:
?? () from /usr/lib/
ffi_call_SYSV () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: gnome-control-
UpgradeStatus: Upgraded to saucy on 2013-02-15 (196 days ago)
UserGroups: fuse lp netdev plugdev sudo
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 #1198681, 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.