GNOME Bugzilla – Bug 571611
nautilus crashed with SIGSEGV in fm_directory_view_update_menus()
Last modified: 2012-12-19 01:44:16 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/328966 "This crash happened after 2nd reboot after some updates. It had to do with a couple of dir's not being in place, I had a private folder set up and linked .gnome .gnome2 and some other dirs to it, but since the last reboot it seems to be broken" But these unaccessible dir's seemded to cause nautilus to fail causing me to be able do nothing after login after deleting my symlinks to all private folders and restarting x and loging in again nautilus and the gnome menu's are working again." ".
+ Trace 212539
Thread 1 (process 4493)
*** Bug 593122 has been marked as a duplicate of this bug. ***
*** Bug 596873 has been marked as a duplicate of this bug. ***
*** Bug 606157 has been marked as a duplicate of this bug. ***
last dupe in 2.28.x
*** Bug 625799 has been marked as a duplicate of this bug. ***
*** Bug 648999 has been marked as a duplicate of this bug. ***
I can still confirm this bug in 2.32.2.1 and due to the amount of duplicates I would say this bug is confirmed. steps to reproduce: (re)move your .gnome2 (and gnome2_private) folder create a symlink to an nonexistent file named .gnome2 (and .gnome2_private): ln -s nosuchdir .gnome2 try to log in to gnome
Created attachment 188588 [details] nautilus backtrace added backtace with debug symbols for nautilus 2.32.2.1
*** Bug 656417 has been marked as a duplicate of this bug. ***
^^ last dup are in 2.32.x ^^
Anyone still seeing this?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!