cygwin xterm 不响应键盘

发布于 2024-07-10 11:08:05 字数 1233 浏览 18 评论 0原文

我的 cygwin xterm 没有响应键盘。

我可以运行 rxvt,但是当我启动其他 X 应用程序时,我遇到了同样的问题。

从 rxvt 命令提示符处,我得到以下信息:

$ xterm
xterm Xt error: Can't open display: :0

我的 XWin.0.log 的内容是:

$ cat XWin.0.log 
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.5.3.0 (10503000)

Contact: [email protected]

XWin was started with the following command line:

/usr/bin/XWin -multiwindow -clipboard -silent-dup-error 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1440 h 900
winInitializeDefaultScreens - Returning

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL

删除 /tmp/.X0-lock 没有帮助。

My cygwin xterm is not responding to the keyboard.

I am able to run rxvt, but when I start other X applications I have the same problem.

From the rxvt command prompt, I get the following:

$ xterm
xterm Xt error: Can't open display: :0

The contents of my XWin.0.log are:

$ cat XWin.0.log 
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.5.3.0 (10503000)

Contact: [email protected]

XWin was started with the following command line:

/usr/bin/XWin -multiwindow -clipboard -silent-dup-error 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1440 h 900
winInitializeDefaultScreens - Returning

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL
GetWindowProp - pWin or name was NULL

Removing /tmp/.X0-lock didn't help.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

反话 2024-07-17 11:08:05

请参阅

  1. 首先通过右键单击系统托盘中的 X 图标并选择退出来停止服务器。

  2. 运行位于/usr/bin 中的startxwin.bat 文件。

See this.

  1. First stop the server by right-clicking on the X icon in the system tray and choosing exit.

  2. Run the startxwin.bat file that is located in /usr/bin.

野心澎湃 2024-07-17 11:08:05

我脑子里有东西在说“关闭 Num Lock”。

我不知道为什么。

Something in the back of my mind is saying "turn off Num Lock".

I'm not sure why.

淡淡の花香 2024-07-17 11:08:05

关闭 Num Lock 解决了我的问题。 我在运行 AIX 的远程系统上打开 xterm,唯一能做任何事情的键似乎是空格键,它可以输入一个空格。 关闭 Num Lock 可以让其他键正常工作。 (AIX 版本的 emacs 没有问题。)我认为这一定是对 AIX 4.3 版本 /usr/bin/X11/xterm 中 Num Lock 键的特殊处理

根据 Cygwin X 常见问题解答:

8.14。 如果 Num-Lock 打开,为什么有些菜单不起作用?

问题在于程序将 Num-Lock 视为类似于 Control 的修饰符。 程序期望简单的点击,但收到一些奇怪的 Num-Lock-Click 组合,并且无法将其与“打开菜单”操作关联起来。

Turning off Num Lock solved my problem. I was opening an xterm on a remote system running AIX, and the only key that seemed to do anything was the space bar, which typed a space. Turning off Num Lock allowed the other keys to work. (The AIX version of emacs did not have a problem.) I assume it must be special treatment of the Num Lock key in AIX 4.3 version of /usr/bin/X11/xterm

According to the Cygwin X FAQ:

8.14. Why do some menus not work if Num-Lock is on?

The problem are programs which treat Num-Lock as modifier similar to Control. The programs expect a plain click but received some strange Num-Lock-Click combination and can't associate this with the action "open menu".

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文