nautilus open and closes repeatedly on login

[Luke Dixon]

Binary package hint: nautilus

I have 3 screens, 2 on one card and one on the other using the nvdia driver.

As soon as i log in, "starting file manager" appear in the panel and appears and disappears repeatedly for which seems an endless cycle. The CPU shows almost 100% usage.

I have discovered that selecting to log out forces this to end. A window appears stating that a program is still running, and clicking cancel on the alert window causes the "starting file manager" bug in the panel to end.

When using the two screens on one card on their own, this issue does not occur.

Description: Ubuntu lucid (development branch)
Release: 10.04

What package information should i include?

Thanks.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 1 11:47:03 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.91-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XInternAtom () from /usr/lib/libX11.so.6
Title: nautilus crashed with signal 5 in _XError()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:11734): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-power-manager:11736): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
 (gnome-terminal:11961): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #508890, so 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. Please continue to report any other bugs you may find.