Workaround for nautilus/panel crashes in Nevada 84, 85.
By bnitz on Mar 14, 2008
A number of people have encountered a bug which causes nautilus and panel to crash on login, preventing the desktop from being used.The symptoms are:
- Nautilus crashes immediately on login, bringing up bug-buddy dialog.
- Panel crashes immediately after the user clicks the Launch menu.
- Any application which makes use of gtk icons crashes.
The bug is only experienced on some hardware and may not occur on every install even on hardware where it fails. It is caused by a file access race condition during the post install phase. The file access conflict causes an ASSERT in the gtk-update-icon-cache which forces this application to core during install. The user is left with incomplete and corrupt icon cache which causes failures of all applications depending on the gtk icon cache.
The bug is described in more detail here: 6631419 - gtk-update-icon-cache dies on first boot after install/upgradeFortunately, there is a very simple workaround:
- Login as root
- Run the following:
for d in /usr/share/icons/\*; do [ -d $d ] && gtk-update-icon-cache --force $d; done
This bug is intermittent and is known to exist in Nevada build 84 and build 85. It may exist in earlier builds on some hardware. The GNOME community's decision to enable application cores on ASSERT may have made some of these subtle underlying problems suddenly become much more frequent and obvious. A fix for bug 6631419 is committed for Nevada build 86.
CORRECTION: There was a discussion over enabling fail on assert within the GNOME community, but no change was recently made. The behavior is that on unstable (odd numbered) versions of gnome-session, fail on assert is enabled, but on even numbered builds it isn't.