Hi ,,

I guess GUI driver is corrupted, I'm also got same error 1 yrs back in
Solaris 8.


bye

Suresh

On Jan 30, 2008 1:56 AM, Aaron Wilson <[EMAIL PROTECTED]> wrote:

> I'm having some login issues. I can't login using, CDE, JDS or Failsafe
> from the console. Also doesn't work from a Sunray session or Xnest
> session.
>
> I enter username and password and the screen goes black, I get an hour
> glass, and then it kicks me back out to the Login prompt. I can however
> ssh into this system. Authentication is using ldap, except for the root
> login. I imagine it's something to do with X and not so much an
> authentication problem, since I can ssh or su to any user without
> problems.
>
> Here is a recent tail of /var/dt/Xerrors
>
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> Warning: Null child found in argument list to unmanage
> /usr/dt/config/Xstartup: LC_ALL=C: is not an identifier
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> Warning: Null child found in argument list to unmanage
> X connection to slosunray2:50.0 broken (explicit kill or server shutdown).
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> Warning: Null child found in argument list to unmanage
> /usr/dt/config/Xstartup: LC_ALL=C: is not an identifier
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> /usr/openwin/bin/xset:  bad font path element (#44), possible causes are:
>    Directory does not exist or has wrong permissions
>    Directory missing fonts.dir
>    Incorrect font server address or syntax
> Warning: Null child found in argument list to unmanage
> X connection to slosunray2:50.0 broken (explicit kill or server shutdown).
> /usr/dt/config/Xstartup: LC_ALL=C: is not an identifier
> (EE) screenInfo.numScreens = 1
> (==) Log file: "/var/log/Xsun.0.log", Time: Tue Jan 29 10:54:27 2008
> (EE) PreInit done
> hwc: Invalid argument
> DPMSSupported: No such device
> Can't control power levels
> DPMSSupported: Invalid argument
> Frame Buffer 0 does not support DPMS
>
>
> Anyone have any ideas?
>
> Aaron
> _______________________________________________
> Solaris-Users mailing list
> [email protected]
> http://www.filibeto.org/mailman/listinfo/solaris-users
>
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users

Reply via email to