[screen]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_set_check_cancellable()

[Zak B. Elep]

Could not adjust brightness in a Lenovo Thinkpad X61 after resuming from suspend via System Settings brightness slider. Fn-Home/End keys do work though.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
Date: Sun Jun 10 01:05:04 2012
ExecutablePath: /usr/bin/gnome-control-center
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_PH:en
 LANG=en_PH.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f56f820072b <g_simple_async_result_set_check_cancellable+107>: cmp %rax,(%rdx)
 PC (0x7f56f820072b) ok
 source "%rax" ok
 destination "(%rdx)" (0x200000001) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_simple_async_result_set_check_cancellable () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_dbus_proxy_call () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libscreen.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: [screen]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_set_check_cancellable()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.2-0ubuntu1
 indicator-datetime 0.3.94-0ubuntu3

[Apport retracing service (apport)]

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 #956251, 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.