After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 47113 - ORBit-WARNING POA gconfd-1 nautilus
ORBit-WARNING POA gconfd-1 nautilus
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: [obsolete] Builds
0.x.x [obsolete]
Other Linux
: Normal normal
: ---
Assigned To: Ramiro Estrugo
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-02-27 19:09 UTC by strawman
Modified: 2007-09-08 11:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
last install log (5.60 KB, text/plain)
2001-09-10 01:03 UTC, strawman
Details

Description strawman 2001-09-10 01:03:31 UTC
The following is printed to ~/.gnomerc-errors endlessly when starting nautilus
from the entry in the panel menu (/usr/bin/run-nautilus) or when just saying
'nautilus' in an xterm.

ORBit-WARNING **: No POA found for operation notify [-1073744712]

also, gconfd-1/nautilus start using cpu time continually, making me want to
'killall -v -9 nautilus'

regards
straw


* REPRODUCIBLE: Always

* STEPS TO REPRODUCE:

run nautilus from menu entry or gnome-console


* ACTUAL RESULTS: 

 gconfd-1 and nautilus begin using cpu time more than expected?



------- Additional Comments From darin@bentspoon.com 2001-02-27 14:12:17 ----

This sounds like a version mismatch problem with ORBit. I seem to recognize the 
symptoms as such. Maybe Josh can look into it.

If (when :-) it does turn out to be a version mismatch of some kind, we should figure 
out what build fix to make to prevent this from happening in the future.



------- Additional Comments From darin@bentspoon.com 2001-02-27 14:56:00 ----

Maybe it's an installer problem? I am very confused about this.



------- Additional Comments From josh@eazel.com 2001-02-27 15:31:48 ----

Eek.  I've not ever seen this.  The normal thing I would say is, "What version
of OAF/ORBit/Bonobo do you have and where did you get them?"  The main one there
would be ORBit, of course.

Does the gconf thing sound related or could it just be a coincidence?

Josh



------- Additional Comments From robey-bugs@lag.net 2001-02-27 15:36:58 ----

if the 1.0 installer installed the wrong version of ORBit, we'd be interested in
an attached /tmp/eazel-install.log file. but only if
1. it was the 1.0 installer
2. it was pointing at hourly:8888
(any other combination is known bad.)




------- Additional Comments From strawman@nbnet.nb.ca 2001-02-27 16:01:14 ----

Created an attachment (id=1260)
last install log




------- Additional Comments From strawman@nbnet.nb.ca 2001-02-27 16:05:41 ----

i'm using the pr3 installer, as the installer from the hourlies won't play nice.
the versions of OAF/ORBit/Bonobo on my box today are all from hourly.eazel.com,
port 8888. distro is rh6.2.




------- Additional Comments From eli@eazel.com 2001-02-27 16:07:56 ----

Straw, the PR3 installer is no longer supported for anything other than
installing PR3.

If the 1.0 installer is failing for you (following instructions on page, and
with caveat e-mailed to nautilus-list a few minutes ago), please file a separate
bug. 

Thanks!



------- Additional Comments From don@eazel.com 2001-02-27 19:07:33 ----

OK, since the PR3 installer was used here, I'm marking this as INVALID.




------- Additional Comments From strawman@nbnet.nb.ca 2001-02-27 20:12:23 ----

oops.. Maybe i goofed here. The behavior i originally described, i would think,
still applies. I'm assuming my OAF/ORBit/Bonobo packages would be the same
regardless of the installer. Here's a list of the *Eazel* rpms on my harddrive:

[strawman@ip010163007098 strawman]$ rpm -qa | grep Eazel
nautilus-installer-0.8.3.0.200102271558-EazelSourceSnapshot
nautilus-suggested-0.8.3.0.200102271558-EazelSourceSnapshot
nautilus-extras-0.8.3.0.200102271558-EazelSourceSnapshot
nautilus-mozilla-0.8.3.0.200102271558-EazelSourceSnapshot
ammonite-0.8.7.0.200102271558-EazelSourceSnapshot
oaf-0.6.5.0.200102271558-EazelSourceSnapshot
ORBit-0.5.7.0.200102271558-EazelSourceSnapshot
GConf-0.50.0.200102271558-EazelSourceSnapshot
medusa-0.3.3.0.200102271558-EazelSourceSnapshot
ORBit-devel-0.5.7.0.200102271558-EazelSourceSnapshot
nautilus-trilobite-0.8.3.0.200102271558-EazelSourceSnapshot
control-center-1.2.3.0.200102271558-EazelSourceSnapshot
bonobo-0.37.0.200102271558-EazelSourceSnapshot
gnome-vfs-0.6.2.0.0.200102271558-EazelSourceSnapshot
nautilus-0.8.3.0.200102271558-EazelSourceSnapshot

or am i missing something?




------- Additional Comments From strawman@nbnet.nb.ca 2001-03-02 00:19:50 ----

ok, the pr3 installer is out of the picture now and i'm still seeing orbit
report the following:

ORBit-WARNING **: No POA found for operation notify [-1073744712]

in the same fashion i originally described

regards
Niko




------- Additional Comments From josh@eazel.com 2001-03-02 02:05:46 ----

Don, I can't reproduce this, and I've not seen it on any other system. 

Can we get this off my radar?

Josh



------- Additional Comments From don@eazel.com 2001-03-02 11:45:54 ----

Yep.  Off to 1.2.




------- Additional Comments From strawman@nbnet.nb.ca 2001-03-02 19:54:17 ----

understood. i'll continue to try to find the source of it on my own time. I've
learned a bit about CORBA so far. :) i'm running a fairly 'customized' rh 6.2
(several packages built from source rpms), which may explain why you've been
unable to reproduce the warning.



------- Additional Comments From mjs@noisehavoc.org 2001-03-11 12:16:52 ----

LATER is not a resolution.




------- Additional Comments From strawman@nbnet.nb.ca 2001-04-27 14:31:42 ----

I've seen a few people report seeing what i've described here, while i've been
using the 'Ximian Support Client'(monkeychat). I've also noticed nautilus seems
to be trying to access my cdrom as the orbit warning is printing to the console
i ran startx from, or to ~/.gnomerc-errors when using gdm. Constant cpu/hd
(moreso hd) activity seems to be the problem, causing overall sluggish-ness.
I've also seen:

ORBit-WARNING **: No POA found for operation ping

and

ORBit-WARNING **: No POA found for operation create_object

at times, when seeing the original orbit warning.

straw





------- Additional Comments From ramiro@fateware.com 2001-04-27 15:37:35 ----

According to strawman, he can still reproduce this bug.

Im ralking it for myself.




------- Additional Comments From strawman@nbnet.nb.ca 2001-04-27 16:28:14 ----

If i turn off the desktop, and run nautilus from the gnome menu, i see somewhat
different behavior. I'm able to start nautilus once at X start with no orbit
warnings or sluggish-ness. Once i close any windows, it refuses to start. If i
then kill off nautilus and start it from the menu it will start, logging these
orbit warnings when i close the window in either case:

ORBit-WARNING **: No POA found for operation notify [-1073744852]

and

ORBit-WARNING **: No POA found for operation create_object [-1073745744]

straw




------- Additional Comments From strawman@nbnet.nb.ca 2001-04-27 16:38:54 ----

i should add that the create_object warning is only printed once, after many
notify warnings.



------- Additional Comments From strawman@nbnet.nb.ca 2001-05-06 22:36:55 ----

try as i might, i can no longer reproproduce this with 1.0.3! btw, 1.0.3 is real
sweet. thank you for all the hard work!



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:03 -------
Comment 1 John Fleck 2002-01-05 04:10:17 UTC
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 David Fallon 2002-03-01 00:52:05 UTC
Setting as fixed as per original bug submitter's comment.
Comment 3 Marc-Andre Lureau 2007-09-08 11:22:20 UTC
*** Bug 474800 has been marked as a duplicate of this bug. ***