File Manager Autospawns at startup + gvfsd trash uses 100% of CPU

[notjingo]

Wow this is driving me nuts. I am still unable to resolve this.

- I followed @altor's instructions to completely remove ubuntuone.
Problem persisted.

- @ravi84m. I set Thunar as the default file manager, then rebooted and reverted back to nautilus.
Problem persisted.

- @Anon Customer. I purged the elementary ppa.
Problem persisted.

Thanks for your input so far. Does anyone have any other ideas? What is even causing this?

[notjingo]

Wow this is driving me nuts. I am still unable to resolve this.

- I followed @altor's instructions to completely remove ubuntuone.
Problem persisted.

- @ravi84m. I set Thunar as the default file manager, then rebooted and reverted back to nautilus.
Problem persisted.

- @Anon Customer. I purged the elementary ppa.
Problem persisted.

Thanks for your input so far. Does anyone have any other ideas? What is even causing this?

[notjingo]

Wow this is driving me nuts. I am still unable to resolve this.

- I followed @altor's instructions to completely remove ubuntuone.
Problem persisted.

- @ravi84m. I set Thunar as the default file manager, then rebooted and reverted back to nautilus.
Problem persisted.

- @Anon Customer. I purged the elementary ppa.
Problem persisted.

Thanks for your input so far. Does anyone have any other ideas? What is even causing this?

[notjingo]

I tried every solution that was posted in this thread and still could not solve this problem.

BUT THEN...
I took a different approach. I went to System-> Preferences->Startup Applications and clicked on the "Options tab." Then, I clicked on "Remember Currently Running Applications."

PROBLEM GONE.

I had a feeling that the problem began right after I had clicked that originally a while back. What must have been going on was that I had been viewing a non auto-mounting device at the time. So I'm assuming at startup, nautilus was trying to open this device in some way but it couldn't because it wasn't mounted, causing nautilus to freak out and retry a billion times.

So ultimately for me it was a really simple solution... Let's see if it holds.

For now we can set this thread to [SOLVED].

[dmuir]

I removed python-nautilus, and the problem went away for me.
If it crops up again, run:

tail /var/log/messages

And it might give some hints as to why nautilus is crashing.

[jeeves]

I ran into the this same problem on 11.04 Natty with the classic gnome 2 desktop. What touched it off was was monkeying with gconf-editor to make the trash bin visible on the desktop.

I would repeatedly use killall nautilus to stop the runaway avalanche of spawning file browsers. Once I killed off all instances of nautilus, I attempted to launch it from the command line and got the following message:

Eel:ERROR:eel-preferences.c:117references_gconf_value_get_string: assertion failed: (value->type == GCONF_VALUE_STRING)
Aborted

So the solution for me turned out to be to simply launch gconf-editor again and go to Apps > nautilus > desktop and undo the checkmark on "trash_icon_visible"