bluetooth-sendto crashed with SIGSEGV in g_closure_invoke()

[Philipp Meier]

Binary package hint: gnome-bluetooth

Tried to send a Picture to my Nexus S. Unfortunately after accepting the send Process on my Phone and after sending a bit of data apport tracked this error.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-bluetooth 2.91.2.is.2.32.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Wed Mar 30 22:32:46 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bluetooth-sendto
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: /usr/bin/bluetooth-sendto --dest 38:16:D1:81:39:95 file:///home/username/Bilder/Ubuntu_Matrix-HD-2.0_android.png
ProcEnviron:
 LANGUAGE=de:en
 LANG=de_CH.UTF-8
 LC_MESSAGES=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4080d7: mov 0x10(%rbx),%rdi
 PC (0x004080d7) ok
 source "0x10(%rbx)" (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/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 natty on 2011-03-25 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 device_services_changed (iface=0xc26a00, property=<value optimized out>, value=0xd5cfe0, user_data=<value optimized out>) at bluetooth-client.c:400
 marshal_dbus_message_to_g_marshaller (closure=0xc2d300, return_value=0x0, n_param_values=<value optimized out>, param_values=<value optimized out>, invocation_hint=0x7fff5ab808d0, marshal_data=0x0) at dbus-gproxy.c:1681
 g_closure_invoke (closure=0xc2d300, return_value=0x0, n_param_values=3, param_values=0xcc4de0, invocation_hint=0x7fff5ab808d0) at /build/buildd/glib2.0-2.28.4/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=798, instance=0xc26a00, emission_return=0x0, instance_and_params=0xcc4de0) at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:2983

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[Sebastien Bacher (seb128)]

see bug #805311 for example

[Timo Jyrinki (timo-jyrinki)]

This is more like duplicate of bug #834348 because it happens when sending a file. Happens on my Latitude E6410 as well. Marking as such.