bluetooth-sendto crashed with SIGSEGV in g_closure_invoke()

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

Bug Description

Happened when I tried to send a file (11 MiB PDF) to my Nokia N900.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.1.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sat Sep 24 19:03:57 2011
ExecutablePath: /usr/bin/bluetooth-sendto
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: bluetooth-sendto
SegvAnalysis:
 Segfault happened at: 0x40948c: mov 0x10(%rax),%rdi
 PC (0x0040948c) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: bluetooth-sendto crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-09-14 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Helge Jung (youngage) 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 #853756, 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
tags: removed: need-amd64-retrace
Revision history for this message
Helge Jung (youngage) wrote :

Just curious: why has this bug been automatically been made public but the duplicate is still private? I don't think there's private information in this report, but I think it is a mistake that the "Apport retracing service (apport)" has removed the "private" flag.

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.