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

Bug #1248675 reported by Matteo Settenvini
100
This bug affects 17 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Just disabling a device's color profile management in the Color panel.
That device is my laptop's LCD screen.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.8.5-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
Date: Wed Nov 6 19:52:01 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2010-12-27 (1045 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7fedfb08e78e: mov 0x8(%rbp),%edx
 PC (0x7fedfb08e78e) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? ()
 ?? ()
 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_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to saucy on 2013-10-26 (10 days ago)
UserGroups: adm lpadmin sambashare sudo
usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1

Revision history for this message
Matteo Settenvini (tchernobog) wrote :
information type: Private → Public
Ubuntu GNOME (ug-bot)
tags: removed: need-amd64-retrace
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.