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 657323 - gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
gvfs-fuse-daemon crashed with SIGSEGV in g_type_create_instance()
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: fuse
1.9.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-08-25 11:50 UTC by Pedro Villavicencio
Modified: 2018-09-21 17:10 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-08-25 11:50:58 UTC
this report has been filed here:

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

"silent crash logged after a cold boot"

backtrace:

.

Thread 1 (Thread 0xb715bb70 (LWP 2099))

  • #0 _g_daemon_vfs_get_async_bus
    at gdaemonvfs.c line 1515
  • #1 g_daemon_volume_monitor_init
    at gdaemonvolumemonitor.c line 206
  • #2 g_type_create_instance
    at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c line 1885
  • #3 g_object_constructor
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1629
  • #4 g_object_newv
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1412
  • #5 g_object_new
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1322
  • #6 ??
  • #7 fuse_fs_init
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #8 ??
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #9 ??
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #10 ??
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #11 fuse_session_process
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #12 ??
    from /tmp/tmp4J2ftD/lib/libfuse.so.2
  • #13 start_thread
    at pthread_create.c line 304
  • #14 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130
Backtrace stopped: Not enough registers or memory available to unwind further
Comment 1 Michael Terry 2011-08-25 19:41:57 UTC
FYI, this was with GIO_USE_VFS=1 which probably explains why gvfs was not correctly initialized.
Comment 2 Michael Terry 2011-08-25 19:42:15 UTC
I'm sorry, I meant GIO_USE_VFS=local.
Comment 3 Ross Lagerwall 2014-04-06 09:44:41 UTC
Confirmed:
$ GIO_USE_VFS=local /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
Segmentation fault (core dumped)
Comment 4 GNOME Infrastructure Team 2018-09-21 17:10:07 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/169.