startx - no keyboard or mouse focus with single xterm, repeatable error - WORKAROUND
I've found a better workaround for this problem which works without needing to calculate the correct placement of a remedial xterm. Install the xsetroot package and run the following once the X server has started up: # Traditional X11 X-shaped cursor xsetroot -cursor_name X_cursor or # Normal left-pointing arrow cursor xsetroot -cursor_name left_ptr Setting the cursor in this way fixes both the keyboard focus and missing pointer problems. Also - can anyone tell me how to respond correctly to messages in a digest or from the mailing list archive? I've just pasted in the subject heading for this email and Scott's original email below (minus the email addresses), but I'm guessing this email won't show up in the right thread location in the overal email structure of the archive. Regards, Patrick From: Scott Merrilees To: Cc: Date: Thu, 14 Jun 2012 16:05:22 +1000 Subject: Re: startx - no keyboard or mouse focus with single xterm, repeatable error I upgraded yesterday, and am similarly afflicted Thanks Patrick for a workaround, +200+200 works for me. Mario's suggestion of startxwin doesn't solve the problem because startxwin doesn't allow single root window mode. Another minimal way to demonstrate the problem: DISPLAY=:0; export DISPLAY XWin twm notice that twm doesn't have focus, and pressing button1 on the root window doesn't show a menu. Howewver if you then force twm to ask where to place a window by doing: xclock then once the window has been placed I can see the button1 menu, and subsequent xterms etc work properly. When I tried fvwm as an alternative window manager, it worked ok. -- Scott Merrilees -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Problem with basic startx and xterm - no cursor or focus
Hi list, A slightly more pared-down version of a question I've posed previously. From a new Cygwin install on Windows 7 running 1024x768 resolution, compare the result of the following two commands run from a Cygwin terminal: startx /usr/bin/xterm -- -logfile broken.log startx /usr/bin/xterm -geometry 80x50+494+51 -- -logfile works.log The first command produces a single unmanaged xterm. No X11 cursor is visible and the xterm is unable to receive input focus. It is not possible to anticipate where the cursor ought to be and give the xterm focus. Unusable. The second command produces a single unmanaged xterm. The X11 cursor is visible and the xterm is able to receive input focus. Works as expected. This seems to be a fairly fundamental problem, and the placement of the xterm determines whether the entire X.org session is usable or not. Does anyone know anything about this problem? Regards, Patrick broken.log Description: Binary data works.log Description: Binary data cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
startx - no keyboard or mouse focus with single xterm, repeatable error
I've observed a problem whereby a single-screen X11 session started with startx or Xwin prevents a single xterm from being started in a usable state (no keyboard or mouse focus), but the problem goes away if the xterm is placed in a *particular area on the screen*. It's a new fresh Cygwin install. Here's the command I'm using: startx /usr/bin/xterm This opens a single-window X11 server populated with one xterm. Within the X11 server window, the cursor is not visible and neither mouse focus or keyboard focus is available. Even with twm running, the situation is the same: startx /usr/bin/xterm -e twm Tested on: Windows XP SP3 32-bit (running under VirtualBox on a Linux host, 1024x768 resolution, 32bpp and 16bpp) Windows Server 2008 R2 64-bit (running under VMware ESX 3.x via an RDP remote desktop session, 1132x778 resolution, 16bpp). Here is the strange thing. On both installations I can get everything working fine by running the xterm like this: startx /usr/bin/xterm -g 40x40-xxx+51 with xxx set to 257 or more, up to an upper bound of 508, after which it stops working again. This range seems to depend on the horizontal resolution of the X11 server window, the example above using 1024x768 32bpp, and basic testing seems to suggest that xxx needs to be just over 25% of the horizontal resolution. The vertical resolution of the X11 server window doesn't seem to have a bearing on the issue. So - it seems that the problem can be side-stepped by popping up an xterm in the area of the screen just beyond the 25% mark on the horizontal access, and then immediately closing it again, after which everything is fine. The fact that it's such a repeatable error is interesting! Any insights appreciated. Regards, Patrick XWin.0.log Description: Binary data cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Updated: startx - no keyboard or mouse focus with single xterm, repeatable error
In my previous email, I mis-typed the xterm geometry which might have caused confusion. There was a minus where there should have been a plus. Corrected version below. I've observed a problem whereby a single-screen X11 session started with startx or Xwin prevents a single xterm from being started in a usable state (no keyboard or mouse focus), but the problem goes away if the xterm is placed in a *particular area on the screen*. It's a new fresh Cygwin install. Here's the command I'm using: startx /usr/bin/xterm This opens a single-window X11 server populated with one xterm. Within the X11 server window, the cursor is not visible and neither mouse focus or keyboard focus is available. Even with twm running, the situation is the same: startx /usr/bin/xterm -e twm Tested on: Windows XP SP3 32-bit (running under VirtualBox on a Linux host, 1024x768 resolution, 32bpp and 16bpp) Windows Server 2008 R2 64-bit (running under VMware ESX 3.x via an RDP remote desktop session, 1132x778 resolution, 16bpp). Here is the strange thing. On both installations I can get everything working fine by running the xterm like this: startx /usr/bin/xterm -g 40x40+xxx+51 with xxx set to 257 or more, up to an upper bound of 508, after which it stops working again. This range seems to depend on the horizontal resolution of the X11 server window, the example above using 1024x768 32bpp, and basic testing seems to suggest that xxx needs to be just over 25% of the horizontal resolution. The vertical resolution of the X11 server window doesn't seem to have a bearing on the issue. So - it seems that the problem can be side-stepped by popping up an xterm in the area of the screen just beyond the 25% mark on the horizontal access, and then immediately closing it again, after which everything is fine. The fact that it's such a repeatable error is interesting! Any insights appreciated. Regards, Patrick XWin.0.log Description: Binary data cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
