系统是RHEL AS3 U8,
另一台Windows用PUTTY + X-Win32登陆，
可以启动gnome和gedit等软件
但是使用startx命令错误：
[eda@localhost eda]$ startx
Using authority file /home/eda/.Xauthority
Writing authority file /home/eda/.Xauthority
Using authority file /home/eda/.Xauthority
Writing authority file /home/eda/.Xauthority
Fatal server error:
PAM authentication failed, cannot start X server.
Perhaps you do not have console ownership?
If you encounter a server crash, please report the problem by filing a bug
report in the XFree86.org bugzilla at and/or Red Hat
bugzilla at When filing your report, it
is very important that you explain your problem in as much detail as possible,
and include a complete description on how to reproduce the problem. After
submitting the bug report, attach the following files as uncompressed
individual file attachments using the bugzilla file attachment feature:
- Kernel log file: /var/log/messages
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
Couldnt get a file descriptor referring to the console
//---------------------------------------------------------------------------------------------------------------------------------------------------------//
RHEL AS3 上安装了EDA软件，本地可以正常启动，
用PUTTY + X-Win32可以正常启动 Cadence IC5141,
但是启动Synopsys DC失败：
[eda@localhost syn]$ design_analyzer
Xlib: connection to "localhost:10.0" refused by server
Xlib: PuTTY X11 proxy: wrong authentication protocol attempted
Error: Can't Open display
--------------------next---------------------
刚才又看到一段话，不理解是什么意思
o By default, ToolTalk tries to connect to the X display
defined by the DISPLAY environment variable to
determine what ttsession to join. The call to
XOpenDisplay (which connects to the X display) can fail
in several ways:
- If DISPLAY is set to a machine that is running
Pandora, the Silicon Graphics (SGI) login, the SGI
Xlib prints out the following warning:
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
There is currently no way to suppress this
warning. Because you probably do not want to
connect to a message server on this machine in
this case, set your DISPLAY environment variable
to the machine running the desired ttsession.
- If DISPLAY is set to a machine that is running XDM
(X Display Manager) as the login, a call to
XOpenDisplay hangs and might eventually return
with the following message:
XIO: fatal IO error 32 (Broken pipe) on X server
"(null)" after 0 requests (0 known processed)
with 0 events remaining. The connection was
probably broken by a server shutdown or KillClient.
Once again, you can set DISPLAY to avoid this
condition. If you are programming to handle this
condition, one solution for detection without
hanging is to set a timer surrounding the call to
tt_open (which calls XOpenDisplay). You can do
this by setting a signal handler for the SIGALRM
signal, and setting the alarm for how long you
will give XOpenDisplay to connect or fail.
--------------------next---------------------
阅读(1050) | 评论(0) | 转发(0) |
