GNOME Bugzilla – Bug 655147
gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try()
Last modified: 2012-02-07 14:29:21 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/811049 the user didnt provide any steps to reproduce the issue but th backtrace looks good: ".
+ Trace 227852
Thread 1 (Thread 27917)
I'm able to reproduce the bug when unmounting an audio cd in Nautilus. (my dupe bug 828383 on lp) StacktraceTop: ?? () g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so 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 Title: gvfsd-cdda crashed with SIGSEGV in g_vfs_job_try()
(In reply to comment #0) > the user didnt provide any steps to reproduce the issue but th backtrace looks > good: I don't see anything specific from the backtrace provided, only a general job going by and the missing symbol in key call. (In reply to comment #1) > I'm able to reproduce the bug when unmounting an audio cd in Nautilus. > (my dupe bug 828383 on lp) Can you post a full link here please? > StacktraceTop: > ?? () > g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so > g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so > 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 > Title: gvfsd-cdda crashed with SIGSEGV in g_vfs_job_try() Also in this case, the "??" symbol is unresolved, please install proper debug packages and catch the trace again.
Created attachment 195515 [details] backtrace with gvfs-dbg
Sorry, previous comment wasn't applied after adding attachment. Obviously unable to install proper debug symbols. Installed first gvfs-backend-dbgsym where gdb said no symbols found. Then tried gvfs-dbg, which removed -dbgsym, again no symbols found. Direct link to my dupe. https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/828383
Hi, I think I produced the same error. The crash happened in the context of banshee. My music is stored in a network location. If I open banshee in another network, banshee tries to open the (old) network drive which does not exist in the current context and crashes. If I open at home, banshee works. I hope I added my findings to the right bug since I had several crashes. When sending the error report the system claimed, that the specific (banshee) crash was already posted and showed this post.
There is a debug stacktrace on https://launchpadlibrarian.net/75425009/ThreadStacktrace.txt That seems to a frequent issue
This seems to me like a dupe of bug 654999 - can you please confirm?
@Tomas: it still happens with gvfs 1.10.0 (so it's not a dupe), when unmounting/ejecting gvfs filesystems via Nautilus. I can provide a debug stacktrace if needed.
There's a Fedora bug report (with 100 comments) regarding what looks like this issue. If the Fedora report is the same issue as this one, surely this bug should be marked CONFIRMED? https://bugzilla.redhat.com/show_bug.cgi?id=744564 I see this crash daily.
*** This bug has been marked as a duplicate of bug 669211 ***