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 410560 - gnome-vfs-daemon crashed with SIGSEGV in _gnome_vfs_handle_do_close()
gnome-vfs-daemon crashed with SIGSEGV in _gnome_vfs_handle_do_close()
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Other
2.20.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
gnome[unmaintained]
: 507739 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-21 21:58 UTC by Sebastien Bacher
Modified: 2018-08-17 13:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sebastien Bacher 2007-02-21 21:58:28 UTC
That bug has been opened on https://launchpad.net/bugs/86767

"I was using a smb shared folder... I don't know why but sometimes (usually when the net is slow) the pc give me this problem.. the directory close unexpectly and the crash report show this window..
[edit]
Ok it happened again, i was seeing a movie on a sbm shared folder, totem gave me the message "Network resource unavailable" after 1 - 2 minutes of the movie, i closed totem and... well i'm here!
Could it be a problem with totem and smb? I remeber that also the first time I was seeing a short movie on the smb folder..
...
Package: libgnomevfs2-0 1:2.17.91-0ubuntu1
..."

Debug backtrace for the crash:

Program terminated with signal 11, Segmentation fault.

Thread 1 (process 7481)

  • #0 _gnome_vfs_handle_do_close
    at gnome-vfs-handle.c line 117
  • #1 gnome_vfs_close_cancellable
    at gnome-vfs-cancellable-ops.c line 108
  • #2 gnome_vfs_close
    at gnome-vfs-ops.c line 194
  • #3 file_handle_free
    at daemon-connection.c line 477
  • #4 g_hash_node_destroy
    at ghash.c line 768
  • #5 g_hash_table_foreach_remove_or_steal
    at ghash.c line 622
  • #6 connection_thread_func
    at daemon-connection.c line 252
  • #7 g_thread_create_proxy
    at gthread.c line 591
  • #8 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #9 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Sebastien Bacher 2007-03-28 09:13:33 UTC
The Ubuntu bug has already 10 dups of the crash
Comment 2 Cristian Aravena Romero 2007-05-29 00:07:28 UTC
This bug has 25 duplicates in Ubuntu.
Comment 3 Sebastien Bacher 2007-09-27 14:15:28 UTC
GNOME 2.20 duplicate on https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/144999
Comment 4 Christian Kirbach 2008-01-06 22:31:41 UTC
*** Bug 507739 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2008-01-06 22:33:41 UTC
Last duplicate has a good trace, too

Confirming report

NOt sure if this will be fixed since we'll move away from gnome-vfs to gio and friends
Comment 6 Cristian Aravena Romero 2008-01-06 23:10:36 UTC
Christia Kirbach: gio work in gnome-2.21.x and 2.22.x? or gio work in 2.23/2.24?
Comment 7 André Klapper 2018-08-17 13:51:14 UTC
gnome-vfs got deprecated in 2008.

gnome-vfs is not under active development anymore and had its last code changes
in 2011. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gnome-vfs/commits/master

gio (in glib) and gvfs are its successors. See https://developer.gnome.org/gio/stable/ch33.html and https://people.gnome.org/~gicmo/gio-migration-guide/ for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of glib/gio/gvfs. Thanks!