Hi all,
On Mon, Dec 29, 2008 at 9:06 AM, Andreas Höschler
<[email protected]> wrote:
Dec 29 18:00:53 ultra20-nge0 dtlogin[2101]: [ID 118685 user.info]
pam_sunray_amgh::[DPY=2] AMGH_SUMMARY: token=pseudo.0003babbaa64,
username=ahoesch, AMGH_Done?=NO(Local Session), Details=AMGH is not
configured., AMGH_Target=*NONE*
Dec 29 18:00:55 ultra20-nge0 utauthd: [ID 794400 user.info]
SessionManager0
NOTICE: EMPTY: ACTIVE session
Dec 29 18:00:56 ultra20-nge0 kiosk:utkioskconfig:refresh[2680]: [ID
702911
user.info] Disabled Kiosk Mode for display ':2'
Dec 29 18:00:56 ultra20-nge0 dtlogin[2579]: [ID 118685 user.info]
pam_sunray_amgh::[DPY=2] AMGH_SUMMARY: token=pseudo.0003babbaa64,
username=,
AMGH_Done?=NO(Local Session), Details=AMGH is not configured.,
AMGH_Target=*NONE*
The X server is exiting. That might be because of a problem in the X
server, or it might be because the desktop session itself has failed.
If the X server is terminating because of an initialization problem or
crashing because of a bug then it might leave some messages in
/var/dt/Xerrors. You might also look in the user's ~/.dt/startlog and
errorlog files in case the desktop session has left messages there.
What happens if you log in to the failsafe session and then run the
WindowMaker session startup script?
What happens if you try to log in to the WindowMaker session on
the server's console or from a remote X (XDMCP) connection?
/opt/csw/bin/pkg-get -i libxcb
did do the trick!!
Thanks,
Andreas
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
