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 408553 - gnome-vfs-daemon crashed with SIGSEGV in strcmp()
gnome-vfs-daemon crashed with SIGSEGV in strcmp()
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Volume and drive handling
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2007-02-16 11:39 UTC by Sebastien Bacher
Modified: 2018-08-17 13:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2007-02-16 11:39:41 UTC 
That bug has been opened on https://launchpad.net/ubuntu/+source/gnome-vfs2/+bug/85477

"I had problem with the gnome-panel, i reloaded than gnome starts but gave a fault..before
gnome wouldn't open
...
Package: libgnomevfs2-0 1:2.17.91-0ubuntu1
..."

Debug backtrace for the crash:

+ Trace 111217

  • #0 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #1 _gnome_vfs_volume_monitor_find_mtab_volume_by_activation_uri
    at gnome-vfs-volume-monitor.c line 539
  • #2 update_fstab_drives
    at gnome-vfs-volume-monitor-daemon.c line 708
  • #3 gnome_vfs_volume_monitor_daemon_init
    at gnome-vfs-volume-monitor-daemon.c line 191
  • #4 IA__g_type_create_instance
    at gtype.c line 1569
  • #5 g_object_constructor
    at gobject.c line 1041
  • #6 IA__g_object_newv
    at gobject.c line 937
  • #7 IA__g_object_new_valist
    at gobject.c line 981
  • #8 IA__g_object_new
    at gobject.c line 795
  • #9 _gnome_vfs_get_volume_monitor_internal
    at gnome-vfs-volume-monitor.c line 315
  • #10 gnome_vfs_get_volume_monitor
    at gnome-vfs-volume-monitor.c line 342 






Comment 1


Kjartan Maraas





          2007-05-07 07:47:55 UTC
        



So, do we add a NULL check for activation_uri, or find out why we were passed a NULL activation_uri?






Comment 2


Jon





          2010-07-29 14:18:08 UTC
        



I had a similar problem in Debian 5 (Lenny) and it was preventing gnome sessions from starting at all. Also gnome applications depending on gnome-vfs-daemon wouldn't launch within a kde session. It turned out one /etc/fstab entry was causing the segfault:

UUID=A86EF81A6EF7DECE windows   ntfs    noauto,user,umask=227 0 0

I'd used the entry to mount the file system without problems despite the mount point not being a full path. Changing 'windows' to '/mnt/windows' solved the issue and gnome sessions are working again. If a null check could be added I would welcome that as the cause of the gnome session failure wasn't immediately obvious.  The original report was posted here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589088

thanks in anticipation,






Comment 3


André Klapper





          2018-08-17 13:52:38 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!