2009.0: Nautilus fails on non-root login [solved]

[man8user]

I installed Gnome for 2009.0. After a non-root login I got error message box with

 

"Nautilus cannot be used now, due to an unexpected error."

Details:

Nautilus cannot be used now, due to an unexpected error from Bonobo when attempting to locate the factory. Killing bonobo-activation-server and restarting Nautilus may help fix the problem

 

My input:

Immediately after login as a non-root user I see the Gnome 2.24 put out a message box saying something about Mandriva Online Applet. The artwork in this box resembles File Manager icons. I do have eth0 enabled but there is no physical connection to internet.

 

Last night I had the internet connected and installed XFS server (to solve the Emacs font problem I am having). I also played around with a USBcamera

and tried to configure Ekiga with my ekiga account. So today, probably the Gnome is assuming there would be internet connection and is trying to validate something about Nautilus from internet.

 

During the 10 second period while it tries to reach internet the screen shows standard icons like Computer, FileSystem, Mounted partitions, etc.

But after that the Error Message Box appears and these icons disappear. But even then the System --> Administration --> File Browser remains available for GUI view of filesystems/devs.

 

Finally, I physically connect the ethernet, log out and log back in as a non-root user but still the same problem with Nautilus.

[man8user]

This is an update.

In the process of installing libstreamXXX for wma codecs I was told to add some non-Free repos and I did that. I was in root account. After that totem was able to play WMA files and I went back working in non-root account. During the process I also did a few ifup/down eth0 from root -- not that it was necessary, but just to check if I can control the eth0 well and at will.

 

Then when I logged in the non-root account, that Bonobo activation server error message failed to appear and the Nautilus icons on desktop did not disappear anymore! Somehow, the problem went away.