Hi,
Apologies if this somewhat off-topic, but hopefully one of you have run
into this problem on your Sun Rays. Otherwise, feel free to ignore me. :)
on our Sun Rays we use Sun's Gnome on Solaris 10/SPARC, and we have an
unusual situation. When a given user attaches to most of the Sun Rays
servers their login happens normally, but if there sessions starts on a
particular server ("medusa"), I get a string of
bonobo-activation-server errors and the login stalls. gconfd and
gnome-session are running, but metacity and nautilus are never called;
and there things will sit forever (or at least five hours; the longest
we let it sit).
Any idea where to start to track this down?
an example rom /var/opt/SUNWut/log/messages
I'm afraid the messages in that log excerpt are not really an indication
of a particular problem. The GConf startup messages are normal, and the
bonobo related warning (at least the one in that log) is something which
occurs every so often even on properly working machines without any
adverse effects (I'm not sure what its root cause is, though). If there
really are bonobo related errors, I would suggest having a look at the
contents of /var/tmp, specifically the orbit-<user> subdirectories, as
there could be directories/files there which require some cleanup (such
leftover files are usually the cause of applet startup errors on login,
for instance).
Incidentally, metacity and nautilus are started by gnome-session, so
it's likely that either gnome-session itself is stuck on some operation,
or the startup of metacity is. I hope this helps,
Cyrille
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
