GNOME Bugzilla – Bug 674659
Nautilus crashing on startup with SIGSEGV
Last modified: 2012-05-07 14:35:15 UTC
Nautilus is failing to start correctly on Arch Linux, nautilus 3.4.1, kernel 3.3.2-1-ARCH, having just upgraded the full Gnome set to 3.4.1. Nautilus manages to create the window with menus, sidebars, title bars, but no files displayed. gdb gives: Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0x7fffeb86f700 (LWP 15806)] [New Thread 0x7fffeb06e700 (LWP 15807)] [New Thread 0x7fffea86d700 (LWP 15808)] [New Thread 0x7fffe9e64700 (LWP 15809)] Initializing nautilus-dropbox 0.7.1 [New Thread 0x7fffd700e700 (LWP 15810)] (nautilus:15793): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_sort_key: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_sort_key: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_is_shadowed: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_volume: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_file_is_native: assertion `G_IS_FILE (file)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GMount' (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_icon: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_file_get_uri: assertion `G_IS_FILE (file)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_name: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_file_get_parse_name: assertion `G_IS_FILE (file)' failed (nautilus:15793): Gtk-CRITICAL **: gtk_icon_theme_lookup_by_gicon: assertion `G_IS_ICON (icon)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_default_location: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_icon: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_file_get_uri: assertion `G_IS_FILE (file)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_get_name: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_file_get_parse_name: assertion `G_IS_FILE (file)' failed (nautilus:15793): Gtk-CRITICAL **: gtk_icon_theme_lookup_by_gicon: assertion `G_IS_ICON (icon)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_can_eject: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): GLib-GIO-CRITICAL **: g_mount_can_unmount: assertion `G_IS_MOUNT (mount)' failed (nautilus:15793): Gtk-WARNING **: gtkliststore.c:1050: invalid unclassed object pointer for value type `GMount' (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:15793): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Program received signal SIGSEGV, Segmentation fault.
+ Trace 230127
Thread 140737136486144 (LWP 15807)
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Okay, started up my laptop and nautilus is working again, I have no idea what's changed since last night.
Created attachment 212688 [details] output of gdb nautilus
I've the same system: Arch 3.3.2-1 with full Gnome 3.4.1 If my NFS is mounted nautilus cause a segfault (and there only if it starts in my home folder). (I've read something that this is in relation with "cifs", but I don't know anything further or about this. May it help the developer ;)) If the NFS isn't mounted nautilus works as expected. My /etc/fstab entry: 192.168.1.111:/home/kabum/Daten /home/kabum/Daten nfs defaults 0 0 nautilus /home/kabum/Daten works perfectly. But it crashes if I want to enter the home folder. I've compiled nautilus with debuging symbols like described in https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces The output is attached. After the run there is an empty nautilus window with only the title. Thanks
(In reply to comment #4) > I've the same system: Arch 3.3.2-1 with full Gnome 3.4.1 > > If my NFS is mounted nautilus cause a segfault (and there only if it starts in > my home folder). (I've read something that this is in relation with "cifs", but > I don't know anything further or about this. May it help the developer ;)) If > the NFS isn't mounted nautilus works as expected. > > My /etc/fstab entry: > > 192.168.1.111:/home/kabum/Daten /home/kabum/Daten nfs defaults 0 0 > > nautilus /home/kabum/Daten works perfectly. But it crashes if I want to enter > the home folder. Hi, the stack trace you provided is still not enough; try to do the following - run nautilus inside gdb with the follwing environment variables set: G_DEBUG=fatal_criticals gdb nautilus - when nautilus hits the first critical and stops in the debugger, get a backtrace with 'thread apply all bt full' and paste the output here
Created attachment 212712 [details] output of gdb nautilus
Do you need any further info?
Yes; you seem to be missing debug information for the glib and gvfs. Can you install such packages and repeat the gdb procedure?
*** Bug 674896 has been marked as a duplicate of this bug. ***
Created attachment 212944 [details] gdb output I used these two packages: https://www.archlinux.org/packages/extra/x86_64/gvfs/ https://www.archlinux.org/packages/extra/x86_64/glib/ I have to launch nautilus with the path "Daten" because without nautilus doesn't even start andthe output where only some "New Thread" and "Thread exited" lines. After the start of nautilus I directly go to my home folder and so nautilus crashes. Hope that helps. :) Thanks!
-> gvfs You're still missing debug symbols for GLib. The package name is glib2 in archlinux apparently [1]. Anyway, it looks like this might be a bug in gvfs. [1] http://www.archlinux.org/packages/core/x86_64/glib2/
(In reply to comment #11) > -> gvfs > > You're still missing debug symbols for GLib. The package name is glib2 in > archlinux apparently [1]. > Anyway, it looks like this might be a bug in gvfs. First of all, it most likely not a bug in the udisks2 volume monitor because that one is running in a separate process. It could be a bug in the 'proxy' volume monitor machinery but that's unlikely since it haven't changed much lately. Hence, it's more likely that it's a reference count bug in nautilus... so reassigning back for now.
Created attachment 212999 [details] output
*** Bug 675182 has been marked as a duplicate of this bug. ***
*** Bug 675282 has been marked as a duplicate of this bug. ***
I was able to track this down to a leaked reference bug introduced in commit a60e9887eebb8973c48c0151981a26cce7cc8793 Pushed a patch to git master and gnome-3-4 to fix this now, thanks for all the help!