[info]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Bug #951570 reported by Frans Slothouber
80
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Rolf Leggewie

Bug Description

I got this while trying to reproduce another bug.
TO reproduce. Quickly open and close the icons in 'System Settings'.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.91-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 10 16:01:52 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x7f57af2d5470: movq $0x0,0x38(%rax)
 PC (0x7f57af2d5470) ok
 source "$0x0" ok
 destination "0x38(%rax)" (0xaaaaaaaaaaaaaae2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libinfo.so
 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
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: [info]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to precise on 2012-03-08 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.3-0ubuntu1
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu3
 indicator-datetime 0.3.91-0ubuntu1

Revision history for this message
Frans Slothouber (rfsber) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 query_done (file=0x7f57e25ef740, res=0x7f57e31d6640, self=0x7f57e291ac90) at cc-info-panel.c:597
 g_simple_async_result_complete (simple=0x7f57e31d6640) at /build/buildd/glib2.0-2.31.20/./gio/gsimpleasyncresult.c:744
 complete_in_idle_cb_for_thread (_data=0x7f57e2f2f0e0) at /build/buildd/glib2.0-2.31.20/./gio/gsimpleasyncresult.c:812
 g_main_dispatch (context=0x7f57e23ff640) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:2510
 g_main_context_dispatch (context=0x7f57e23ff640) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:3047

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
summary: - [info]: gnome-control-center crashed with SIGSEGV in
- g_simple_async_result_complete()
+ [info]: gnome-control-center crashed with SIGSEGV in query_done()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: [info]: gnome-control-center crashed with SIGSEGV in query_done()

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
tags: added: quantal running-unity
Revision history for this message
Rolf Leggewie (r0lf) wrote :

still an issue in 2018?

Changed in gnome-control-center (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: Confirmed → Incomplete
summary: - [info]: gnome-control-center crashed with SIGSEGV in query_done()
+ [info]: gnome-control-center crashed with SIGSEGV in
+ g_main_context_dispatch
summary: [info]: gnome-control-center crashed with SIGSEGV in
- g_main_context_dispatch
+ g_main_context_dispatch()
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug has no recent activity/report and there has been no reply to the comment, closing

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Invalid
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.