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 664649 - Crash in FTP backend
Crash in FTP backend
Status: RESOLVED DUPLICATE of bug 653042
Product: gvfs
Classification: Core
Component: ftp backend
1.8.x
Other Linux
: Normal major
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-23 15:36 UTC by Milan Bouchet-Valat
Modified: 2015-02-28 21:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2011-11-23 15:36:48 UTC 
This crash has been reported twice in Fedora, once with GVfs 1.6.6 in F14, and once with 1.8.2 on F15. It seems to be quite rare, but...

It happened once when unmounting a share, and once when accessing a share that had been mounted before the computer was suspended.

See https://bugzilla.redhat.com/show_bug.cgi?id=702999.


[New Thread 2839]
[New Thread 2658]
[New Thread 2601]
[New Thread 2836]
[New Thread 2633]
[Thread debugging using libthread_db enabled]
Core was generated by `/usr/libexec/gvfsd-ftp --spawner :1.10 /org/gtk/gvfs/exec_spaw/2'.
Program terminated with signal 11, Segmentation fault.

+ Trace 229109

Thread 1 (Thread 0x7f7a88c2a700 (LWP 2839))

  • #0 g_io_stream_get_input_stream
    at giostream.c line 237
  • #1 g_vfs_ftp_dir_cache_lookup_entry
    at gvfsftpdircache.c line 165
  • #2 g_vfs_ftp_dir_cache_lookup_dir
    at gvfsftpdircache.c line 365
  • #3 do_enumerate
    at gvfsbackendftp.c line 1020
  • #4 g_vfs_job_run
    at gvfsjob.c line 198
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #6 g_thread_create_proxy
    at gthread.c line 1897
  • #7 start_thread
    at pthread_create.c line 301
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Ross Lagerwall





          2015-02-28 21:14:13 UTC
        




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