Can't start session [2]
Can't start session
Saturday, October 28, 2006 6:36 AM - Juan
I'm trying to connect to my Solaris session, but it's not possible. Here is what I obtain from /var/dt/Xerrors
root@Server # cat Xerrors
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:30 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:31 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:32 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:33 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
Fri Oct 27 16:13:34 2006
error (pid 6571): Server for display :0 can't be started.
Couldn't open display connection
When I open Xbrowser, the server isn't active.
I can connect the server using telnet, then I run 'dtlogin -daemon' and it activates the server on the Xbrowser (for a short time, perhaps less than one minute) but double-clicking on it just doesn't work.
Thanks in advance for the help
root@Server # cat Xerrors
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:30 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:31 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:32 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
KIOCTYPE: Invalid argument
ddxSUNWmouse: ioctl failed on /dev/mouse
VUIDGFORMAT: Invalid argument
Fatal server error:
failed to initialize core devices
Fri Oct 27 16:13:33 2006
error (pid 6571): Server for display :0 terminated unexpectedly 1
Fri Oct 27 16:13:34 2006
error (pid 6571): Server for display :0 can't be started.
Couldn't open display connection
When I open Xbrowser, the server isn't active.
I can connect the server using telnet, then I run 'dtlogin -daemon' and it activates the server on the Xbrowser (for a short time, perhaps less than one minute) but double-clicking on it just doesn't work.
Thanks in advance for the help
Re: Can't start session
Monday, October 30, 2006 4:56 PM - Andy
It looks like your server is not capable of running the graphical programs, hence it is making errors when dtlogin is trying to run Xserver on console. However, you can still use CDE remotely. Here is how:
*Follow this instruction iff you are not using the graphical UI on console.
First, configure your dtlogin to accept the remote connections only (x server will not run on console). To do this, comment out the following line in /usr/dt/config/Xservers by putting # in front like this:
# 0 Local local_uid@console root /usr/X11/bin/Xserver :0 -nobanner
Then, restart dtlogin.
Hope this works for u.
*Follow this instruction iff you are not using the graphical UI on console.
First, configure your dtlogin to accept the remote connections only (x server will not run on console). To do this, comment out the following line in /usr/dt/config/Xservers by putting # in front like this:
# 0 Local local_uid@console root /usr/X11/bin/Xserver :0 -nobanner
Then, restart dtlogin.
Hope this works for u.
Re: Can't start session
Thursday, December 11, 2008 8:27 PM - comrade256
my solution is.. reinstall the OS.. this not a good solution, but it is working..
thanks
thanks
Previous views: 471