Ubuntu
gvfs package

gvfsd-obexftp segmentation fault

Bug #196771 reported by Saivann Carignan
10
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Recent update of gvfs add support for OBEX in nautilus. However, I just tried to access my sony ericson z520a cell phone that worked correctly with previous gnome-obexftp package and got that error after I typed this in nautilus : obex://[00:16:B8:3A:7A:DC]/

Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Please select another viewer and try again.

dmesg also shows this :
gvfsd-obexftp[6535]: segfault at 0 rip 7f8becb5d7f6 rsp 424e9890 error 4

If someone know how I can do a relevant backtrace / valgrind for this process, I can provide more debugging informations.

Linux zxz-desktop 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux

See original description
Saivann Carignan (oxmosys)
description: updated
description: updated
Revision history for this message
Matti Lindell (mlind) wrote :

Upstream trunk is currently very active regarding to gfvs backends, obexftp as well. gvfsd-obexftp segfaults for me too with current Ubuntu svn snapshot, but running svn snapshot from yesterday has fixed the segfaults I had.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
don hardaway (don-hardaway) wrote :

I can not still use my bluetooth mouse after the latest updates in Hardy. When is this going to be fixed--with the beta coming out it should be ready.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.