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

Bug #962174 reported by Ahmed Kamal
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
New
Undecided
Unassigned

Bug Description

was in bluetooth, clicked "sound" settings .. crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-bluetooth 3.2.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 53600264fb13d2dea4043333a4cb3f09
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Thu Mar 22 15:25:04 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705)
ProcCmdline: gnome-control-center sound
SegvAnalysis:
 Segfault happened at: 0x7f39dc39f1a6: mov 0x8(%rax),%rcx
 PC (0x7f39dc39f1a6) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-02-15 (36 days ago)
UserGroups: adm admin cdrom dialout disk fuse kvm libvirtd lpadmin plugdev sambashare vboxusers video

Revision history for this message
Ahmed Kamal (kim0) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.