Matthias Ernst wrote:
Bob Doolittle wrote:
Matthias Ernst wrote:
That sounds like a good explanation. I have reenabled the xlock and will
wait for the next time the problem occurs and then look in more detail on
the xscreensaver process. As soon as I have more information, I will
open a service call with Sun and try to get the newest xscreensaver
patch.
I think this list membership would appreciate you sharing your
final conclusions, so folks in future could benefit from
your experience.
Of course I will, but it might take a bit of time. We have a fairly small
installation (about 24 Sunray stations) and the problem happens only sometimes
and to some people. My guess is that it might actually be connected to the
xscreensaver settings of the user. It happened about six times during the
first three weeks of January after upgrading the server to the latest Solaris
10 release but it has not happened during the last week. So I have to wait
for the next occurence.
But even if it only happens sometimes, if it happens to somebody who was
running a long Mathematica or Matlab calculation and cannot get to their
results, people are understandably not very happy.
It's inconceivable to me that, if you kill off
the xscreensaver and xlock processes, the session
would remain inaccessible. Unless the X server
itself is broken, which is highly unlikely. Now that
you know better what to look for, I strongly suspect
you can regain access to the session. Theoretically,
you may be running into the USB keyboard flakiness
we're currently tracking. If you kill off the associated
screen lockers, and still can't access the session, try
unplugging/replugging the keyboard.
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
