gvfsd-obexftp crashed with SIGSEGV

[Vicente Ruiz]

Binary package hint: gvfs

It crashed when trying to send a file to a cell phone.

ProblemType: Crash
Architecture: amd64
Date: Thu Apr 17 16:49:36 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.2.3-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libglib-2.0.so.0
Title: gvfsd-obexftp crashed with SIGSEGV
Uname: Linux 2.6.24-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:_dbus_pending_call_get_connection_and_lock (pending=0x63efa0) at dbus-pending-call.c:309
reply_handler_timeout (data=0x0) at dbus-connection.c:3098
timeout_handler_dispatch (data=<value optimized out>) at dbus-gmain.c:343
g_timeout_dispatch (source=0x63ee00, callback=0x7fafb88da610 <timeout_handler_dispatch>,
IA__g_main_context_dispatch (context=0x638390) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009

[Sebastien Bacher (seb128)]

do you still get the issue using the current version?

[Vicente Ruiz (uve)]

No, I don't. Gvfs works fine with 0.99.4 version.

[Sebastien Bacher (seb128)]

thank you for the update, closing the bug, feel free to reopen if you get the issue again though

[Christopher (soft-kristal)]

Happened in 12.10 3.5.0-16 with the latest bluez updates 20:45 EST. Bluetooth has been an issue for quite a while on my 32 bit partition but works well on the same laptop, same OS on the 64 bit partition.

[Karma Dorje (taaroa)]

I've filed another bug with apport and all my files are attached there: bug 1086802, just in case they're not duplicates.

[Christopher (soft-kristal)]

I confirm the issue has not be resolved. Just tried again with the same result.

[Carterclan (carterclan)]

Still exists in an up-to date 13.04

[Paulo Novais (valeptb)]

Confirmed on 13.04
3.8.0-13-generic #23-Ubuntu SMP Mon Mar 18 18:09:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
This bug happens since version 11:10
Will we ever going to be solved?

[dino99 (9d9)]

That version has died long ago; no more supported