[background]: gnome-control-center crashed with SIGSEGV in file_info_async_ready()

Bug #911475 reported by Ian Nicholson
102
This bug affects 14 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Invalid
Medium
gnome-control-center (Ubuntu)
Fix Released
Medium
Unassigned
gnome-control-center-unity (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Occurred after a reboot. The clock in the upper right hand corner of my screen does not appear.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Jan 3 15:40:47 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f22645f16ac <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f22645f16ac) ok
 source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libbackground.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to precise on 2012-01-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 21.2-0ubuntu2
 gnome-bluetooth 3.2.1-1ubuntu3

Revision history for this message
Ian Nicholson (imnichol) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x7f2267aa4f00, iface_type=139785747295344) at /build/buildd/glib2.0-2.31.6/./gobject/gtype.c:3998
 file_info_async_ready (source=0x7f224000d8d0, res=0x7f2267da4400, user_data=0x7f2267aa4f00) at bg-pictures-source.c:337
 next_async_callback_wrapper (source_object=0x7f224000d8d0, res=0x7f2267da4400, user_data=0x7f2267aa4f00) at /build/buildd/glib2.0-2.31.6/./gio/gfileenumerator.c:298
 g_simple_async_result_complete (simple=0x7f2267da4400) at /build/buildd/glib2.0-2.31.6/./gio/gsimpleasyncresult.c:744
 complete_in_idle_cb_for_thread (_data=0x7f2267ce7190) at /build/buildd/glib2.0-2.31.6/./gio/gsimpleasyncresult.c:812

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 gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Ian Nicholson (imnichol) wrote :

It appears that either during the upgrade or during the crash, indicator-datetime and indicator-power were both uninstalled. They reappeared once I reinstalled them via apt-get. I'm not sure if this is related to gnome-control-center at all.

summary: - gnome-control-center crashed with SIGSEGV in
- g_type_check_instance_cast()
+ gnome-control-center crashed with SIGSEGV in file_info_async_ready()
Changed in gnome-control-center (Ubuntu):
status: Confirmed → Triaged
Changed in gnome-control-center:
importance: Unknown → Medium
status: Unknown → Confirmed
tags: added: background
summary: - gnome-control-center crashed with SIGSEGV in file_info_async_ready()
+ [background]: gnome-control-center crashed with SIGSEGV in
+ file_info_async_ready()
tags: added: quantal
Revision history for this message
Jhosman Lizarazo (jhosman) wrote :
Changed in gnome-control-center:
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-control-center (Ubuntu):
status: Triaged → Fix Committed
Changed in gnome-control-center-unity (Ubuntu):
importance: Undecided → Low
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-control-center-unity - 1.3daily13.06.12-0ubuntu1

---------------
gnome-control-center-unity (1.3daily13.06.12-0ubuntu1) saucy; urgency=low

  [ Sebastien Bacher ]
  * Fix handling of cancellation in async calls (lp: #911475) That's
    basically a backport of https://git.gnome.org/browse/gnome-control-
    center/commit/?id=f9c0732a6c4d1d01e23d35e385e44caee93c5f29. (LP:
    #911475)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 25
 -- Ubuntu daily release <email address hidden> Wed, 12 Jun 2013 00:02:33 +0000

Changed in gnome-control-center-unity (Ubuntu):
status: In Progress → Fix Released
Changed in gnome-control-center (Ubuntu):
status: Fix Committed → Fix Released
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.