Red Hat Bugzilla – Bug 238227
Nautilus crash at login "Nautilus can't be used now, due to an unexpected error" (bonobo error)
Last modified: 2015-03-03 17:31:14 EST
Description of problem:
When logging into the GNOME based i386 Fedora 7 test 4 live cd nautilus
sometimes crashes with a vague bonobo error and the desktop is black. Running
nautilus again usually fixes this. This also happened on the test 2 live cd
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login into GNOME
Sometimes nautilus crashes and desktop is blank. no panel etc.
Fully functional desktop. No crashes.
Sorry. I did not note the specific bonobo error and the crash is not very
reproducible. I will post the error or screenshot if it happens again.
Created attachment 153786 [details]
nautilus bonobo crash error on login
The error means: we registered the shell with
bonobo_activation_register_active_server, which succeeded but then
Bonobo_ACTIVATION_FLAG_EXISTING_ONLY, NULL, NULL) fails.
This really shouldn't happen... Maybe its is a race when multiple nautilus
instances are run...
I am just doing a regular login and it crashes every single time for me now. Not
sure why multiple nautilus instances would be launched. Is there anything that I
do to help you fix this issue?
I have experienced the exact same problem on F7 final, with all updates as of
June 14 installed. I use user switching, but so far the Nautilus problem has
only shown when no more than one user has been logged in at the same time.
Created attachment 157036 [details]
.xsession-errors file showing the error
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This should be re-based to 10. I can see this in (at least) a VNC session.
Workaround, from the command line:
nautilus --no-default-window --oaf-ior-fd=<the one you see for bonobo-activation-server>
Can you elaborate on the meaning of "<the one you see for bonobo-activation-server>"
Anyway this bug happens even more often in F10. I'm noticing it on almost any machine I upgraded (about 15 up to now).
Updating version to 10, to avoid this bug getting auto-closed once F9 is no longer maintained, since people are seeing the issue in F10 too.
*** Bug 462235 has been marked as a duplicate of this bug. ***
Editing the bug title, so people can find this bug by searching for the error message.
Copying CC list from dup'd bug.
Regarding comment #10, run:
ps -ef | grep bonobo-activation-server
You'll get something like:
/usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=17
Seventeen is the magic number there...
I tried renaming the .nautilus directory to see if that would fix this error and it didn't. When I moved all the gnome directories and the .nautilus directory out of the way, logged out, and logged in again this error went away.
Hmm... Just restarted my vncserver and when the session started, no error. Also, gnome-settings-daemon started all by itself. Has something been fixed?
I had this same error to fix it I opened a terminal window logged in as root
then i reinstalled the gnome desktop package
yum reinstall gnome-desktop
Is anyone still seeing this in Fedora 10 with the latest updates, or Fedora 11? I saw this in Fedora 9, but I am not experiencing it in Fedora 11.
Fedora Bugzappers volunteer triage team
*** Bug 471366 has been marked as a duplicate of this bug. ***
Nautilus in F11 doesn't use bonobo anymore for startup, we use libunique now. Such error messages might be result of some bonobo issue, outside nautilus package.
I don't understand the needinfo here. What information do you need exactly?
(In reply to comment #21)
> I don't understand the needinfo here. What information do you need exactly?
The needinfo was just re-set from comment #18 - "Is anyone still seeing this in Fedora 10 with the latest updates?"
This bug was reported by me more than 2 and a half years back and was never responded to nor was it fixed then. I don't see a point in trying to respond to it now. The release is EOL'ed. Just close it and move on.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: