bluetooth-sendto crashed with SIGSEGV in g_closure_invoke()

[Mario Vukelic]

Laptop and phone are paired. I go to the bluetooth indicator and choose Send Files To Device. A file chooser appears and I use it. A dialog comes up that scans devices and shows my phone. I select it and click Send. Then the Apport dialog appears.

This is reproducible for me.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 2 20:28:41 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bluetooth-sendto
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110422)
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-08-18 (45 days ago)
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev powerdev sambashare tape video

[Apport retracing service (apport)]

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.