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 576731 - gvfsd-trash crashed with SIGSEGV in g_simple_async_result_complete()
gvfsd-trash crashed with SIGSEGV in g_simple_async_result_complete()
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: trash backend
1.8.x
Other Linux
: High critical
: ---
Assigned To: Allison Karlitskaya (desrt)
gvfs-maint
: 651748 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-03-25 14:43 UTC by Pedro Villavicencio
Modified: 2013-11-04 08:47 UTC
See Also:
GNOME target: ---
GNOME version: 3.3/3.4



Description Pedro Villavicencio 2009-03-25 14:43:03 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/345754

"When i empty the trash it crashed."

".

Thread 1 (process 3923)

  • #0 g_vfs_job_emit_finished
    at gvfsjob.c line 323
  • #1 send_reply_cb
    at gvfschannel.c line 590
  • #2 IA__g_simple_async_result_complete
    at /build/buildd/glib2.0-2.20.0/gio/gsimpleasyncresult.c line 567
  • #3 complete_in_idle_cb
    at /build/buildd/glib2.0-2.20.0/gio/gsimpleasyncresult.c line 577
  • #4 g_idle_dispatch
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 3922
  • #5 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 1814
  • #6 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 2448
  • #7 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 2656
  • #8 daemon_main
    at daemon-main.c line 294
  • #9 main
    at daemon-main-generic.c line 39

Comment 1 Sebastien Bacher 2011-03-17 12:58:52 UTC
seems to still be an issue and not distro specific, see https://bugzilla.redhat.com/show_bug.cgi?id=612698
Comment 2 Pedro Villavicencio 2011-05-25 14:07:51 UTC
is there any required info in order to fix this bug? it is still an issue with 2.32.
Comment 3 Bastien Nocera 2012-01-12 17:27:05 UTC
This still happens with the current git master of gvfs.

To reproduce:
- Get a Totem with that patch:
http://git.gnome.org/browse/totem/commit/?id=8ef36a2c74f1b9e614b7f94b8a53d4190c3bbebd
(not required, but it makes reproducing the bug a doodle)
- Make sure your copy of GStreamer ships with a giosrc plugin:
giosrc
- Start playing a video file from the trash, and seek around it in Totem

  • #0 g_vfs_job_emit_finished
    at gvfsjob.c line 323
  • #1 send_reply_cb
    at gvfschannel.c line 613
  • #2 g_simple_async_result_complete
    at gsimpleasyncresult.c line 744
  • #3 complete_in_idle_cb
    at gsimpleasyncresult.c line 756
  • #4 g_idle_dispatch
    at gmain.c line 4632
  • #5 g_main_dispatch
    at gmain.c line 2513
  • #6 g_main_context_dispatch
    at gmain.c line 3050
  • #7 g_main_context_iterate
    at gmain.c line 3121
  • #8 g_main_loop_run
    at gmain.c line 3315
  • #9 daemon_main
    at daemon-main.c line 300
  • #10 main
    at daemon-main-generic.c line 39

Comment 4 Michael Terry 2012-04-11 16:53:22 UTC
*** Bug 651748 has been marked as a duplicate of this bug. ***
Comment 5 Michael Terry 2012-04-11 18:45:46 UTC
So a naive solution is to just guard the crashing line with "if (job)".  But in
looking at the code, I'm curious why the write async calls don't have
cancellables or data structures like the read async calls do.  And how likely
it is that we'd have multiple write calls extant?  (g_vfs_channel_send_reply
doesn't guard against being called multiple times, and it seems plausible to me
that it would be, but I don't grok the gvfs code paths)
Comment 6 Ross Lagerwall 2013-11-04 08:47:29 UTC
This is not reproducible on current git master so it must have been fixed up in the meantime.