After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655147 - gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try()
gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try()
Status: RESOLVED DUPLICATE of bug 669211
Product: gvfs
Classification: Core
Component: ftp backend
1.9.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-07-22 20:05 UTC by Pedro Villavicencio
Modified: 2012-02-07 14:29 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2


Attachments
backtrace with gvfs-dbg (10.98 KB, text/plain)
2011-09-02 18:04 UTC, sam_
Details

Description Pedro Villavicencio 2011-07-22 20:05:56 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:

".

Thread 1 (Thread 27917)

  • #0 ??
  • #1 try
    at gvfsjobunmount.c line 222
  • #2 g_vfs_job_try
    at gvfsjob.c line 216
  • #3 g_vfs_daemon_queue_job
    at gvfsdaemon.c line 462
  • #4 job_source_new_job_callback
    at gvfsdaemon.c line 322
  • #5 g_cclosure_marshal_VOID__OBJECT
    at /build/buildd/glib2.0-2.29.10/./gobject/gmarshal.c line 644
  • #6 g_closure_invoke
    at /build/buildd/glib2.0-2.29.10/./gobject/gclosure.c line 773
  • #7 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 3256
  • #8 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 2987
  • #9 g_signal_emit
    at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 3044
  • #10 g_vfs_job_source_new_job
    at gvfsjobsource.c line 100
  • #11 backend_dbus_handler
    at gvfsbackend.c line 666
  • #12 daemon_message_func
    at gvfsdaemon.c line 990
  • #13 dbus_connection_dispatch
    at ../../dbus/dbus-connection.c line 4601
  • #14 message_queue_dispatch
    at dbus-gmain.c line 127
  • #15 g_main_dispatch
    at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 2473
  • #16 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3046
  • #17 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3124
  • #18 g_main_loop_run
    at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3332
  • #19 daemon_main
    at daemon-main.c line 295
  • #20 main
    at daemon-main-generic.c line 39

Comment 1 sam_ 2011-08-25 16:53:49 UTC
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()
Comment 2 Tomas Bzatek 2011-08-29 14:47:09 UTC
(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.
Comment 3 sam_ 2011-09-02 18:04:42 UTC
Created attachment 195515 [details]
backtrace with gvfs-dbg
Comment 4 sam_ 2011-09-02 18:09:24 UTC
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
Comment 5 michael_beck22 2011-09-28 06:56:42 UTC
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.
Comment 6 Sebastien Bacher 2011-10-10 13:22:47 UTC
There is a debug stacktrace on
https://launchpadlibrarian.net/75425009/ThreadStacktrace.txt

That seems to a frequent issue
Comment 7 Tomas Bzatek 2011-10-10 13:42:07 UTC
This seems to me like a dupe of bug 654999 - can you please confirm?
Comment 8 Dmitry Shachnev 2011-12-29 07:10:51 UTC
@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.
Comment 9 Gabriel Bauman 2012-01-26 23:16:33 UTC
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.
Comment 10 Tomas Bzatek 2012-02-07 14:29:21 UTC

*** This bug has been marked as a duplicate of bug 669211 ***