GNOME Bugzilla – Bug 675282
Nautilus often crashes with segmentation fault when opening some directories
Last modified: 2012-05-04 18:40:33 UTC
OVERVIEW: Nautilus crashes with a segmentation fault since upgrading from 3.2.1-1 to 3.4.1-1 (I'm using Arch Linux). The crash happens when trying to open certain directories. For me and most users who have commented on this, it happens when opening a local Dropbox folder or a remote (Samba) folder. Some users have reported it happening with remote NFS folders, a few have reported it happening when opening their home directory. It is not 100% reproducible. Opening my Dropbox folder makes it crash always. Opening remote Samba directories makes it crash most of the time, but not always. STEPS TO REPRODUCE: 1) Open Nautilus 2) Double-click on the local Dropbox folder or on a remote Samba directory ACTUAL RESULTS: Nautilus crashes. EXPECTED RESULTS: Nautilus should show the contents of the directory. BUILD&PLATFORM: Nautilus 3.4.1-1 from the "extra" Arch Linux repository. ADDITIONAL BUILDS AND PLATFORMS: The crash didn't happen with version 3.2.1-1. ADDITIONAL INFORMATION: Gdb trace when Nautilus crashes opening a local Dropbox directory: http://pastebin.com/Eea2avs9 Gdb trace when Nautilus crashes opening a remote Samba directory: http://pastebin.com/CU8KewDF Originally reported in the arch bugtracker: https://bugs.archlinux.org/task/29584 I'm running Nautilus with the XFCE desktop environment (no Gnome Shell etc running). Thunar (the XFCE file manager) doesn't crash with the same user actions. Some users have reported that deleting one or both of these directories solved the problem for them: ~/.config/dconf ~/.gtk-bookmarks I haven't tried deleting those directories myself in case devs want to investigate my current environment.
Removing ~/.config/dconf and ~/.gtk-bookmarks doesn't "solve" this for me. Also on Arch Linux, using Gnome (Nautilus 3.4.1-1). Following message in the sys log (or some variant of this every few minutes as I move around my fs): nautilus[4332]: segfault at b009b70 ip 00007f46a35f7d33 sp 00007fff034e7a60 error 4 in libgobject-2.0.so.0.3200.1[7f46a35c6000+4c000]
Each crash should be reported as separate bug.
Should I open two new bugs reports? Should I leave this one open or closed?
No, it's the same bug, which is a duplicate of 674659. *** This bug has been marked as a duplicate of bug 674659 ***