This morning I am getting a message on my screen that:
There was a problem registering the panel with the bonobo-activation server error code is 1
It further suggests run bonobo-slay to perhaps take care of the situation. When I run bonobo-slay it says:
bonobo-slay
Can not open directory /usr/lib/bonobo/servers No such file or directory
What do I do now? Thanks,
Jerry
On Wed, Sep 9, 2009 at 7:29 AM, Jerry Geis geisj@pagestation.com wrote:
What do I do now?
You consider providing a bit more detail as to what you were doing when you got that message, whether it happens every time, if it appears to be related to something specific (every time I start firefox, I get X), any packages you've changed from the default, etc. .
What you've given us isn't really enough information to provide any functional help.
You consider providing a bit more detail as to what you were doing when you got that message, whether it happens every time, if it appears to be related to something specific (every time I start firefox, I get X), any packages you've changed from the default, etc. .
What you've given us isn't really enough information to provide any functional help.
Jim,
Only thing I did last was a "yum update"... on centos 5 x86_64. This happens every time I reboot.
once I hit the OK button it looks like everything still comes up and runs as normal.
I was hoping that based on the output of the "bonobo-slay" someone might new what to do...
Thanks,
Jerry
Jim,
Only thing I did last was a "yum update"... on centos 5 x86_64. This happens every time I reboot.
once I hit the OK button it looks like everything still comes up and runs as normal.
I was hoping that based on the output of the "bonobo-slay" someone might new what to do...
On that output, not so much. The output directly below it is a bit more helpful. Your system seems to think that /usr/lib/bonobo/servers doesn't exist. You could check to see if it is actually there. It could also be some multi-arch related issue, since you mention x86_64 and that's the 32bit path.
However as before, you're not really telling us anything overly useful. You've not mentioned versions of software, whether this is after you log in or prior to. Which manager you're using (gdm vs kdm) or which gui where you're seeing this. You're not giving anyone enough detail to move any real direction to help you.
You've given just about enough information about your problem to get the typical helldesk response of 'Is your computer ON?'
On that output, not so much. The output directly below it is a bit more helpful. Your system seems to think that /usr/lib/bonobo/servers doesn't exist. You could check to see if it is actually there. It could also be some multi-arch related issue, since you mention x86_64 and that's the 32bit path.
However as before, you're not really telling us anything overly useful. You've not mentioned versions of software, whether this is after you log in or prior to. Which manager you're using (gdm vs kdm) or which gui where you're seeing this. You're not giving anyone enough detail to move any real direction to help you.
You've given just about enough information about your problem to get the typical helldesk response of 'Is your computer ON?'
Lets dig a little deaper...
I am using gnome and gdm.
bonobo-slay gives:
Can not open directory /usr/lib/bonobo/servers No such file or directory
[root@am2mm ~]# ls /usr/lib/bonobo ls: /usr/lib/bonobo: No such file or directory
This machine auto logs on, X windows starts and I see this error message, a few seconds later my application starts up as normal .
rpm -qa | grep bonobo libbonoboui-2.16.0-1.fc6 libbonobo-2.16.0-1.fc6 libbonoboui-2.16.0-1.fc6 libbonobo-2.16.0-1.fc6 gnome-python2-bonobo-2.16.0-1.fc6
There is a /usr/lib64/bonobo/servers directory.
Why is the 32 bit version starting (it would seem) and how do I stop it?
Thanks,
Jerry
On Wed, Sep 9, 2009 at 8:58 AM, Jerry Geis geisj@pagestation.com wrote:
This machine auto logs on, X windows starts and I see this error message, a few seconds later my application starts up as normal .
rpm -qa | grep bonobo libbonoboui-2.16.0-1.fc6 libbonobo-2.16.0-1.fc6 libbonoboui-2.16.0-1.fc6 libbonobo-2.16.0-1.fc6 gnome-python2-bonobo-2.16.0-1.fc6
There is a /usr/lib64/bonobo/servers directory.
Why is the 32 bit version starting (it would seem) and how do I stop it?
http://wiki.centos.org/TipsAndTricks/YumAndRPM
Do step 1 (or drop it into /etc/rpm/macros.local so it applies to all users)
then remove the i386 versions of those packages (they should now be visible as libbonoboui-2.16.0-1.fc6.i386 etc).
http://wiki.centos.org/TipsAndTricks/YumAndRPM
Do step 1 (or drop it into /etc/rpm/macros.local so it applies to all users)
then remove the i386 versions of those packages (they should now be visible as libbonoboui-2.16.0-1.fc6.i386 etc).
Jim,
I removed the (2) packages that were i386. I rebooted the box and the same message pops up. I logged back in and did:
rpm -qa | grep bonobo libbonobo-2.16.0-1.fc6.x86_64 libbonoboui-2.16.0-1.fc6.x86_64 gnome-python2-bonobo-2.16.0-1.fc6.x86_64
So now only the 64bit packages are present. (note: I did rpm -e --nodeps package to remove the 32 bit ones)
I then did: bonobo-slay
Can not open directory /usr/lib/bonobo/servers No such file or directory
Does it still think its 32 bit based on the directory given? What might the next step be?
Thanks,
Jerry
Jerry Geis wrote:
http://wiki.centos.org/TipsAndTricks/YumAndRPM
Do step 1 (or drop it into /etc/rpm/macros.local so it applies to all users)
then remove the i386 versions of those packages (they should now be visible as libbonoboui-2.16.0-1.fc6.i386 etc).
Jim,
I removed the (2) packages that were i386. I rebooted the box and the same message pops up. I logged back in and did:
rpm -qa | grep bonobo libbonobo-2.16.0-1.fc6.x86_64 libbonoboui-2.16.0-1.fc6.x86_64 gnome-python2-bonobo-2.16.0-1.fc6.x86_64
So now only the 64bit packages are present. (note: I did rpm -e --nodeps package to remove the 32 bit ones)
bad idea (nodeps)... you should probably reinstall them and then either leave them, or remove whatever depends on them. Otherwise chances are whatever depends on them will be broken on your system. It's not related to your current problem, but maybe to one of your next posts to the list ;-)
I then did: bonobo-slay
Can not open directory /usr/lib/bonobo/servers No such file or directory
Does it still think its 32 bit based on the directory given? What might the next step be?
/usr/bin/bonobo-slay is a perl script, clearly buggy wrt 64-bit (that path is hard-coded). I have no idea what it does, bonobo is a monkey to me, but you could try fixing that script. You might also consider filing a bug somewhere. Whether fixing the script would solve your problem is another question... But it may be worth a try.
-
Jerry Geis -
Jim Perrin -
Nicolas Thierry-Mieg