bluetooth-applet crashed with SIGSEGV in g_closure_invoke()

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

Bug Description

Crashed after attempt to browse files on the Android smartphone

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6
Uname: Linux 3.0.0-13-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CheckboxSubmission: 32b2b5d4dec078676ee5a1a9cbe277bc
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Sun Nov 6 22:14:50 2011
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: bluetooth-applet
SegvAnalysis:
 Segfault happened at: 0xb77efa4e: cmpl $0x1,0x40(%eax)
 PC (0xb77efa4e) ok
 source "$0x1" ok
 destination "0x40(%eax)" (0x00000040) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.8
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
discont (discont) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #859321, 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-i386-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.