Nautilus did not open for /home folders & files; Document Viewer opened instead

[Garry Leach]

Binary package hint: nautilus

1. Ubuntu 10.10 (fresh install)
2. Nautilus 2.32.0; Evince Document Viewer 2.32.0

3. I clicked on Places, then Home Folder.
I expected this to open my home folders & files.

4. Instead, Document Viewer opened.
It displayed the messages: Unable to open document. Can't open directory

This problem started in late January 2011.

This problem happens only with /home files (home, desktop, music, etc.). Files under / (computer, file system, etc.) are displayed correctly.

My hard drive is split into several partitions:
sda1: 20GB, mount point /, operating system
sda3: 2GB, swap
sda4 & 5:149GB, mounted at /home
I somehow managed (through no action that I was aware of) to also get 2 sets of free space during the partitioning process, one of 12GB & one of 17GB.

If I open an application (e.g. Open Office, Firefox), then select open, Nautilus opens correctly.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
Architecture: i386
Date: Sat Feb 5 06:07:00 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: evince
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1577): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1572): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #667071, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

You can find a workaround in comment 10 or the description of bug #667071.