Red Hat Bugzilla – Bug 462235
Nautilus crash @ startup "Nautilus can't be used now, due to an unexpected error"
Last modified: 2015-03-03 17:33:12 EST
Description of problem:
Immediately after login, nautilus crashes(?) and displays a dialog box with no title, and the following text:
Nautilus can't be used now,
due to an unexpected error.
Clicking the "Show more details" button displays this additional text:
Nautilus can't 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
Clicking the OK button restarts Nautilus, thus making the desktop icons appear for the first time this login session. Also, an unexpected nautilus file browsing window appears displaying the user's home directory. This window was not open at last logout.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in (or perhaps unlock after hibernate)
* This happens at initial login, not unlock after hibernate.
* It isn't "always", instead it's "often".
* I believe this is a regressions that appeared as part of the updates since the F9 security outage; i.e. the last week or so. I don't recall seeing this before then. That said, hibernate worked before then, so perhaps I wasn't logging in from scratch so much.
In the past couple of days I've seen this on two systems running Rawhide. The only other message shown when starting nautilus from the terminal is:
** (nautilus:4020): WARNING **: Unable to add monitor: Not supported
Yes, this still continually happens to my wife on F9.
I'm seeing this behaviour on a system I upgraded from F8 to F9 with the Unity respin 20081004 DVD. As Stephen noted, it doesn't happen every time I log in, but it's pretty close to every time.
This bug happens even more often in F10. I'm noticing it on almost any machine I upgraded (about 15 up to now).
bug 462235 and this should be merged.
Sorry. I meant bug 238227
Marking duplicate of 238227.
*** This bug has been marked as a duplicate of bug 238227 ***