Dominik Frey schrieb:
Thanks Brad! I wasn't aware of this beeing a feature.
Unfortunately, those error messages look quite confusing to the
uneducated...
The error messages are not part of the feature and shouldn't be there.
We'd need to see a bit more context (utpolicy output, larger pieces of
the messages log) to be able to tell whether the bug is just an
unwarranted error message.
But if your screen properly goes to the "Sun Ray Session Lock" dialog
and unlocking works, then the error message is probably harmless.
After having upgraded my installation to SRSS 4.2, screenlocking with
xscreensaver does not work correctly.
The DTU just looks as if it has lost connection to the SR server when hitting a key for "wakeup", reconnects
to the SR server (which takes some seconds) and then asks for the user password using the sunray dialog.
In /var/adm/messages the following can be found:
Nov 20 06:40:54 jonathan xscreensaver[6120]: [ID 508707 user.error]
pam_sunray:get_auth_perm: ut_setproperties username returned -1
SunSolve does not any advice. Any ideas? Locking the screen has worked
correctly before upgrading to SRSS4.2
- Jörg
--
Joerg Barfurth phone: +49 40 23646662 / x66662
Software Engineer mailto:[email protected]
Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/
Thin Client Software http://www.sun.com/software/sunray/
Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
