Hide Forgot
Description of problem: After doing a large update on a RHEL6.2 Beta and rebooting into the new kernel, nautilus crashes when starting Gnome and the Gnome Window List applet start showing increasingly more nautilus icons. However no desktop background or icons, and no windows are visible. What happened is that nautilus is crashing very quickly and respawning, completely soaking one core. The ~/.xession-errors contain hundreds of: Initializing nautilus-open-terminal extension Initializing nautilus-gdu extension ** ERROR:nautilus-desktop-directory.c:162:directory_ready_callback: assertion failed: (g_list_find (merged_callback->non_ready_directories, directory) != NULL) Initializing nautilus-open-terminal extension Initializing nautilus-gdu extension ** ERROR:nautilus-desktop-directory.c:162:directory_ready_callback: assertion failed: (g_list_find (merged_callback->non_ready_directories, directory) != NULL) When looking at the process-list I can see abrtd being hammered with requests. Starting nautilus on the command line (and in strace/ltrace) shows a segfault, while not providing any immediate cause for it. (Scanning of directories was done, crash happened inside GTK+ library-calls) The problem appears with nautilus-2.28.4-18.el6.x86_64 (and nautilus-extensions), reinstalling nautilus-2.28.4-15.el6.x86_64.rpm fixes the problem for me.
This issue still exists in RHEL6.2. I discovered that this problem is related to the nautilus setting /apps/nautilus/preferences/desktop_is_home_dir If this is enabled and the system boots into Gnome, nautilus starts crashing and respawning ad infinitum... All my desktop systems use the home-directory as the Desktop. So they all experience this.
Could you please grab a backtrace of the crashing process?
Confirming, this triggers the problem: (In reply to comment #2) > I discovered that this problem is related to the nautilus setting > /apps/nautilus/preferences/desktop_is_home_dir
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: A queued directory load operation has not been cancelled after directory refresh Consequence: Crash occurred on startup Fix: Pending operations that are not valid are now correctly cancelled Result: No crash on startup
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0914.html