Re: Problem with Cygwin/X from remote Linux
On 03/10/2014 05:19, Chris Carlson wrote: I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. [...] I thought the two logs that you requested were a bit large for this e-mail, so I put them on my web site. You can access them as: Thanks. So, this is the set visuals that the X server supports. GL_VERSION: 3.1.0 - Build 8.15.10.2455 GL_VENDOR: Intel GL_RENDERER:Intel(R) HD Graphics Family [...] pxf vis fb render Ste aux accumMSdrawable Group/ idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat - 1 51 42 TrueColor32 0 y . . . 8 8 8 8 0 0 0 0 0 0 000 y . y . . 2 2 52 43 TrueColor32 0 y . y xchg . 8 8 8 8 0 0 0 16 16 16 1600 y . y . . 2 3 53 44 TrueColor32 0 y . . . 8 8 8 8 24 8 0 0 0 0 000 y . y . . 2 4 21 45 TrueColor32 0 y . y xchg . 8 8 8 8 24 8 0 16 16 16 1600 y . y . . 2 5 54 46 TrueColor32 0 y . . . 8 8 8 8 16 0 0 0 0 0 000 y . y . . 2 6 55 47 TrueColor32 0 y . y xchg . 8 8 8 8 16 0 0 16 16 16 1600 y . y . . 2 7 56 48 TrueColor32 0 y . y copy . 8 8 8 8 0 0 0 16 16 16 1600 y . y . . 2 8 57 49 TrueColor32 0 y . y copy . 8 8 8 8 16 0 0 16 16 16 1600 y . y . . 2 9 41 4a TrueColor32 0 y . y copy . 8 8 8 8 24 8 0 16 16 16 1600 y . y . . 2 10 58 4b TrueColor32 0 y . . . 8 8 8 8 0 0 0 0 0 0 014 y . y . . 2 11 59 4c TrueColor32 0 y . y xchg . 8 8 8 8 0 0 0 16 16 16 1614 y . y . . 2 12 5a 4d TrueColor32 0 y . . . 8 8 8 8 16 0 0 0 0 0 014 y . y . . 2 13 5b 4e TrueColor32 0 y . y xchg . 8 8 8 8 16 0 0 16 16 16 1614 y . y . . 2 14 5c 4f TrueColor32 0 y . . . 8 8 8 8 24 8 0 0 0 0 014 y . y . . 2 15 5d 50 TrueColor32 0 y . y xchg . 8 8 8 8 24 8 0 16 16 16 1614 y . y . . 2 The mesa software renderer on the remote host constructs the set of visuals the client gets offered by picking the visuals from the server's set of visuals which match one of it's visuals OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) OpenGL version string: 2.1 Mesa 8.0.4 [...] visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat 0x051 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x053 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None Unfortunately this set is small, and indeed doesn't contain any double-buffered visuals. Workarounds are to use either start Cygwin X server with -nowgl (so it too uses the software renderer and will offer a set of visual which is probably exactly the same), or to run the client with the LIBGL_ALWAYS_INDIRECT env var set (so that indirect rendering is used and the remote client has access to the actual set of visuals the server supports) I think the real fix to this is to fix the remote libGL, either so it matches visuals less precisely, or so it offers more visuals which can match, but this is not simple. Believe it or not, I just so happen to have an XWin.0.log from my old, old, old version of Cygwin. It was: Package: version 1.15.1-2 built 2014-05-06 Now I can reproduce this, it seems that this can be an unfortunate side-effect of the Improve visual matching with a remote libGL by not reporting pbuffer size limits change in 1.15.1-3 [1], which was intended to have the opposite effect, if previously no visuals at all were matching, so the software renderer was disabled, and we were falling back to indirect rendering. [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-06/msg2.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem with Cygwin/X from remote Linux
On 02/10/2014 04:53, Chris Carlson wrote: I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. [...] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. Thanks for reporting this problem. Unfortunately, I can't reproduce it. Please can you attach the output of 'X -multiwindow -logverbose 3', so I can see what visuals the server thinks should be available, and the output of running 'glxinfo' on your remote system. Can you give the version of Fedora you are using, and the version of the libGL package you have? I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? No, this is not intentional. I guess this is an unintended consequence of a change. It would be useful in tracking down that change if you could identify the last X server release which worked correctly. The release announce mails are a hopefully accurate summary of intended changes (e.g [1]) [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-09/msg4.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem with Cygwin/X from remote Linux
Hello, Jon. The version of Fedora I'm running is: Linux rolf 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I thought the two logs that you requested were a bit large for this e-mail, so I put them on my web site. You can access them as: http://beachware.org/Cygwin/glxinfo.cygwin http://beachware.org/Cygwin/X.log Believe it or not, I just so happen to have an XWin.0.log from my old, old, old version of Cygwin. It was: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 grover 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601](Win64) Package: version 1.15.1-2 built 2014-05-06 XWin was started with the following command line: X :0 -multiwindow Let me know if there's anything else I can provide. Chris Carlson On 10/2/2014 5:05 AM, Jon TURNEY wrote: On 02/10/2014 04:53, Chris Carlson wrote: I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. [...] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. Thanks for reporting this problem. Unfortunately, I can't reproduce it. Please can you attach the output of 'X -multiwindow -logverbose 3', so I can see what visuals the server thinks should be available, and the output of running 'glxinfo' on your remote system. Can you give the version of Fedora you are using, and the version of the libGL package you have? I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? No, this is not intentional. I guess this is an unintended consequence of a change. It would be useful in tracking down that change if you could identify the last X server release which worked correctly. The release announce mails are a hopefully accurate summary of intended changes (e.g [1]) [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-09/msg4.html -- 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 Cygwin/X from remote Linux
I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. Every now and then, I will upgrade Cygwin_64 just to get the latest changes. I hope that the few issues I have will be cleared up. I believe the one issue I have with Thunderbird may be Thunderbird, not Cygwin/X. Anyway, over the past weekend, I upgraded again. The upgrade seemed to go well. No surprises until... One of the things I've been doing is learning OpenGL. I'm converting a sample program that I acquired while working at SGI to OpenGL (it was written in gl, the original SGI graphics language). For the past few months, all of my OpenGL programs have worked fine over the network. Suddenly, with the latest version of Cygwin/X, it doesn't. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? Thanks, Chris Carlson -- 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/
Re: Problem starting the X server
On 26/09/2014 03:52, Joel Ledain wrote: I just installed the Cygwin packages on top of a Windows 7. The machine is Gateway NV55S28u. Install went fine. Rebooted the machine and tried the bash window, this works fine. Then tried to start the X server, and here I have a problem. I thing my problem is related to the keyboard binding/support/missing packages... I tried to use the command setxkbmap, but without the X server running I am not getting anything beside cannot open display. For the Windows control panel - devices - keyboard, I see a standard PS2 keyboard. I have the xkeyboard-config package installed. I am attaching the log of my troubles. (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm (EE) XKB: Failed to load keymap. Loading default keymap instead. (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate core devices. (EE) Server terminated with error (1). Closing log file. You should check that xkeyboard-config and xkbcomp are installed correctly, that xkbcomp can be run, and that you don't have any software which is known to interfere with cygwin installed, as described at [1]. You might also check if the TEMP or TMP environment variables are set, and if so, contain the unix-style pathname of a directory which both exists and is writeable. If that doesn't help, perhaps could you try the snapshot [2], which is built with additional debug logging enabled. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-failed-to-compile-keymap [2] ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20140926-git-6f318e09efcfdbe9.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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 starting the X server
Hello good guys, I just installed the Cygwin packages on top of a Windows 7. The machine is Gateway NV55S28u. Install went fine. Rebooted the machine and tried the bash window, this works fine. Then tried to start the X server, and here I have a problem. I thing my problem is related to the keyboard binding/support/missing packages... I tried to use the command setxkbmap, but without the X server running I am not getting anything beside cannot open display. For the Windows control panel - devices - keyboard, I see a standard PS2 keyboard. I have the xkeyboard-config package installed. I am attaching the log of my troubles. Thanks in advance for your great help. Joel LEDAIN Script started on Thu, Sep 25, 2014 5:59:11 PM $ echo $XAPPLRESDIR $XCMSDB $XNLSPATH $XKEYSYMDB $DISPLAY $ cygcheck -c xkeyboard-config Cygwin Package Information Package VersionStatus xkeyboard-config 2.12-1 OK $ which xkbcomp /usr/bin/xkbcomp $ ls -l /usr/bin/xkbcomp -rwxr-xr-x 1 joel None 189971 Apr 8 2013 /usr/bin/xkbcomp $ /usr/bin/xkbcomp Error:No input file specified $ cygcheck /usr/bin/xkbcomp C:\cygwin64\bin\xkbcomp.exe C:\cygwin64\bin\cygwin1.dll C:\Windows\system32\KERNEL32.dll C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll C:\Windows\system32\ntdll.dll C:\Windows\system32\KERNELBASE.dll C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll C:\cygwin64\bin\cygX11-6.dll C:\cygwin64\bin\cygxcb-1.dll C:\cygwin64\bin\cygXau-6.dll C:\cygwin64\bin\cygXdmcp-6.dll C:\cygwin64\bin\cygxkbfile-1.dll $ startxwin Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.0.0 OS: CYGWIN_NT-6.1 Joel_laptop 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.0-2 built 2014-09-16 XWin was started with the following command line: X :0 -multiwindow (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/joel/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0015 winSetEngine - Multi Window or Rootless = ShadowGDI winScreenInit - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1366 height: 768 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' GL_VERSION: 4.1.11159 Compatibility Profile Context GL_VENDOR: ATI Technologies Inc. GL_RENDERER:AMD Radeon(TM) HD 6520G (II) AIGLX: enabled GLX_SGI_make_current_read (II) AIGLX: enabled GLX_MESA_copy_sub_buffer (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control (II) AIGLX: enabled GLX_SGIX_pbuffer (II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample (II) 107 pixel formats reported by wglGetPixelFormatAttribivARB (II) AIGLX: Set GLX version to 1.4 (II) 30 fbConfigs (II) ignored pixel formats: 0 not OpenGL, 12 RBGA float, 30 RGBA unsigned float, 0 unknown pixel type, 35 unaccelerated (II) GLX: Initialized Win32 native WGL GL provider for screen 0 (EE) Couldn't open compiled keymap
Re: keyboard problem with mwm and window done with Motif
On 01/08/2014 15:00, Isabelle EDOUARD wrote: I run with command line on my Windows 7 Xwin.exe in rootless mode. After I run the window manager: mwm.exe and finally I launch an application in a Red-Hat Server which use window done in Motif and Qt. With Qt windows the Keypad of my Keyboard works well (All the keyboard is OK) in a xterm too but with Motif windows is different: All seems to be well except 0. When I want to make 0 with the keypad, nothing appear, it's Ok with 1,2,3,4 etc ... but not with 0. Have I forgotten to configure a file or file(s) have bad configuration? Thanks for your help. Thanks for reporting this problem. I can't immediately reproduce it, so perhaps you can help me with a bit more information Can you attach your /var/log/xwin/XWin.0.log so I can see precisely what keyboard layout you are using? Can you tell me what particular motif application and version of Red-Hat server you are connecting to? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
keyboard problem with mwm and window done with Motif
Hello, I run with command line on my Windows 7 Xwin.exe in rootless mode. After I run the window manager: mwm.exe and finally I launch an application in a Red-Hat Server which use window done in Motif and Qt. With Qt windows the Keypad of my Keyboard works well (All the keyboard is OK) in a xterm too but with Motif windows is different: All seems to be well except 0. When I want to make 0 with the keypad, nothing appear, it's Ok with 1,2,3,4 etc ... but not with 0. Have I forgotten to configure a file or file(s) have bad configuration? Thanks for your help. Regards, Isabelle -- 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 evaluating window resize hints under 64 bit
The current cygwin x server 1.15.1-2 under 64-bit cygwin seems to have a problem correctly evaluating the window resize
hints.
In hw/xwin/winmultiwindowwndproc.c the function ValidateSizing calls winMultiWindowGetWMNormalHints and gets wrong
values in sizeHints.width_inc and sizeHints.height_inc.
In function winMultiWindowGetWMNormalHints in file hw/xwin/winmultiwindowclass.c you can see that a memcpy occurs from
prop-data with sizeof(WinXSizeHints).
As it turns out, everything is correct if you modify the typedef of WinXSizeHints in hw/xwin/winmultiwindowclass.h so
that long type becomes int:
--- a/cygwin/hw/xwin/winmultiwindowclass.h
+++ b/cygwin/hw/xwin/winmultiwindowclass.h
@@ -63,7 +63,7 @@ typedef struct {
* used with WM_NORMAL_HINTS.
*/
typedef struct {
-long flags; /* marks which fields in this structure are
defined */
+int flags; /* marks which fields in this structure are
defined */
int x, y; /* obsolete for new window mgrs, but clients */
int width, height; /* should set so old wm's don't mess up */
I can only guess why this works: in the X11 message protocol all int and long types are mapped to 32 bit integers. It
seems that the memcpy in winMultiWindowGetWMNormalHints has source data that has memory layout as in the X11 message
protocol.
Best regards,
Oliver
--
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/
Re: problem evaluating window resize hints under 64 bit
On 19/06/2014 13:22, Oliver Schmidt wrote:
The current cygwin x server 1.15.1-2 under 64-bit cygwin seems to have a
problem correctly evaluating the window resize hints.
In hw/xwin/winmultiwindowwndproc.c the function ValidateSizing calls
winMultiWindowGetWMNormalHints and gets wrong values in
sizeHints.width_inc and sizeHints.height_inc.
In function winMultiWindowGetWMNormalHints in file
hw/xwin/winmultiwindowclass.c you can see that a memcpy occurs from
prop-data with sizeof(WinXSizeHints).
As it turns out, everything is correct if you modify the typedef of
WinXSizeHints in hw/xwin/winmultiwindowclass.h so that long type becomes
int:
--- a/cygwin/hw/xwin/winmultiwindowclass.h
+++ b/cygwin/hw/xwin/winmultiwindowclass.h
@@ -63,7 +63,7 @@ typedef struct {
* used with WM_NORMAL_HINTS.
*/
typedef struct {
-long flags; /* marks which fields in this structure
are defined */
+int flags; /* marks which fields in this structure
are defined */
int x, y; /* obsolete for new window mgrs, but
clients */
int width, height; /* should set so old wm's don't mess
up */
Thanks for pointing this out and the patch.
The same problem also occurs with WM_HINTS a few lines above.
I can only guess why this works: in the X11 message protocol all int and
long types are mapped to 32 bit integers. It seems that the memcpy in
winMultiWindowGetWMNormalHints has source data that has memory layout as
in the X11 message protocol.
Yes. For historical reasons, 'long' is used for the CARD32 type in the
libX11 API (which this structure has been copied from), but because that
has a different size on x86 and x86_64, so libX11 marshalls that into a
32-bit quantity before storing it into the window property.
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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/
Re: problem with opengl (glxgears) running on cygwin ....
On 2014-03-25 09:05, Jon TURNEY wrote: On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. Yaakov Cygwin/X -- 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/
remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....)
Yaakov (Cygwin/X) wrote: On 2014-03-25 09:05, Jon TURNEY wrote: On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. FWIW, I tried another X server...VcXsrv?... Same with that program. I tried several, got some that worked, most didn't. Of the few that worked 'well' remotely, they were variations on the glgears... got about 400-500 FPS -- and about low 300's MB/s in bandwidth consumed... that sounds about right... but I think there are other problem in trying to get a remote desktop to work now... everything wants to connect to the session bus -- and many progs won't start if they can't. So if I can't figure out a way to get that to work, remote usage is left at a fairly primitive level despite the high frame rates on a 3x4 window... ;-) One of the demo progs said it required opengl 2.1 .. my card has V4.something. well above 2.1, so that seems like another latent problem. Will look for the fixed version ... thanks for the news... -- 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/
Re: problem with opengl (glxgears) running on cygwin ....
On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Same effect happens when I try remotely. Window comes up with gears displayed, but no motion. Fraps also shows 30 FPS. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. Since [1], glxgears turns at a constant 70 degrees per second. glxSwapBuffers does not block when used with indirect rendering, which means that lots of frames can be rendered almost instantly, with no apparent rotation, since the elapsed time between frames is very small. glxgears is a very basic test that GLX is functioning, and definitely not a benchmark. Real GLX clients should have a better mechanism for ensuring their animation rate doesn't outrun the vsync frequency. If you have any problems with real GLX clients, I would be interested to hear them. [1] http://cgit.freedesktop.org/mesa/demos/commit/src/xdemos/glxgears.c?id=0b19fb0a5c6299baf28e26625e39773846f815b2 When I try remote display, the above is pretty much the same except I get an error on the client system that it can't load the 3d swrast.so driver on the other end. There is some problem with loading the swrast_dri.so renderer on the remote system, so it is falling back to indirect rendering. What is the OS of the remote system? But it sees pretty much the same capabilities -- FWIW, there is next to zilch network traffic happening when I try this.. I mean while it is happening. Before and after ~ 200-400KB/s (xosview), during, all my X windows become very slow and no longer refresh steadily. Network throughput registers a drop to 1-80KB/s. Despite that -- xwin pegs a cpu @100% and stays that way until I exit glxgears. I think this is because glxgears will send frames as fast as it can, and can saturate the X server. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: problem with opengl (glxgears) running on cygwin ....
Jon TURNEY wrote: Since [1], glxgears turns at a constant 70 degrees per second. --- 70 degress/s? How is that important? glxSwapBuffers does not block when used with indirect rendering, which means that lots of frames can be rendered almost instantly, with no apparent rotation, since the elapsed time between frames is very small. According to the text in the starting window it is rendering at 30FPS. -- I.e. it is sync'ed with my monitor's refresh rate (except for the 1st iteration when it acted unsynced) ... I.e. in starting window this was displayed: Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 45623 frames in 6.4 seconds = 7166.903 FPS 834 frames in 27.4 seconds = 30.428 FPS 822 frames in 28.8 seconds = 28.542 FPS With all X-window response degraded (Xserver process was peg'ed@100%cpu), virtually no network traffic -- dropped from a norm of 200-400KB/s down to between 1KB-80KB/s. glxgears is a very basic test that GLX is functioning, and definitely not a benchmark. Real GLX clients should have a better mechanism for ensuring their animation rate doesn't outrun the vsync frequency. I thought it was the most basic. It claims (except for the 1st iteration) that it is not outruning my monitor's refresh rate. If you have any problems with real GLX clients, I would be interested to hear them. I'd be interested in finding any that work and proves that it works locally. While my initial use was to try remote GLX, I reverted to trying it localling -- just to verify it worked as it used to. Thats what brought this on. What is the OS of the remote system? --- linux (opensuse 13.1). No one else on that list was able to see normal response... some got really sluggish response, others saw no movement or nothing. It was only after I ran glxgears locally that I figured I might also have a problem in Cygwin's X, in addition to any other problem I have w/remote display. I think this is because glxgears will send frames as fast as it can, and can saturate the X server. The demo claims to sync at the same rate the monitor is refreshing. i.e -- 30 FPS. -- 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 opengl (glxgears) running on cygwin ....
and GLX_MESA_swap_control [ 86222.532] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 86222.532] (II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample [ 86222.532] (II) 482 pixel formats reported by wglGetPixelFormatAttribivARB [ 86222.548] (II) AIGLX: Set GLX version to 1.4 [ 86222.548] (II) 323 fbConfigs [ 86222.548] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 86222.548] [dix] Could not init font path element /windows/fonts, removing from list! [ 86222.641] winPointerWarpCursor - Discarding first warp: 1280 800 [ 86222.641] (--) 5 mouse buttons found [ 86222.641] (--) Setting autorepeat to delay=250, rate=31 [ 86222.641] (--) Windows keyboard layout: 0409 (0409) US, type 4 [ 86222.641] (--) Found matching XKB configuration English (USA) [ 86222.641] (--) Model = pc105 Layout = us Variant = none Options = none [ 86222.641] Rules = base Model = pc105 Layout = us Variant = none Options = none [ 86222.641] winBlockHandler - pthread_mutex_unlock() [ 86222.641] winInitMultiWindowWM - pthread_mutex_lock () returned. [ 86222.641] winInitMultiWindowWM - pthread_mutex_unlock () returned. [ 86222.641] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [ 86222.641] winInitMultiWindowWM - DISPLAY=:0.0 [ 86222.641] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [ 86222.641] winMultiWindowXMsgProc - DISPLAY=:0.0 [ 86222.641] winProcEstablishConnection - winInitClipboard returned. [ 86222.641] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [ 86222.641] winClipboardThreadProc - DISPLAY=:0.0 [ 86222.641] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 86222.657] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 86226.307] winXCursorToHCURSOR - Windows requires 32x32 cursor but X requires 48x48 [105011.433] winGetWindowInfo: forcing window to exist [105060.901] winGetWindowInfo: forcing window to exist [105079.449] winGetWindowInfo: forcing window to exist [105120.322] winGetWindowInfo: forcing window to exist [105130.040] winGetWindowInfo: forcing window to exist [105136.608] winGetWindowInfo: forcing window to exist [105264.201] winGetWindowInfo: forcing window to exist [105296.509] winGetWindowInfo: forcing window to exist [105312.671] winGetWindowInfo: forcing window to exist -- 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/
Re: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64
On Wed, Mar 19, 2014 at 08:44:29PM -0400, Thomas Dickey wrote: On Wed, Mar 19, 2014 at 04:25:44PM -0700, Mark Hansen wrote: On 3/19/2014 3:21 PM, Jyhshyong wrote: Hi I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that the Xterm in the system tray icon is no longer working. The Xwin server system tray icon has the following target C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe It works fine as the 32-bit version, click on the icon, I can start X server and open a small Xterm window. However, the Xterm system tray icon with the target defined as C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' I don't see anything wrong with the command-line, but it's been a while since I updated Cygwin packages (and I'm not in the middle of a release cycle), so I'll do that to see if it breaks for me. hmm: a) I'm uncertain how to configure the system tray to match the reported configuration (a sample .XWinrc might help). b) the latest xterm I find from mirrors is still #302 (should not be a problem with the given command-line). c) xterm comes up on my machine (which is 64-bits). -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64
On 3/19/2014 3:21 PM, Jyhshyong wrote: Hi I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that the Xterm in the system tray icon is no longer working. The Xwin server system tray icon has the following target C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe It works fine as the 32-bit version, click on the icon, I can start X server and open a small Xterm window. However, the Xterm system tray icon with the target defined as C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' failed to open an xterm window. The 32 bit version of the Xterm short icon with the target defined as C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' is still working, but only open to the 32-bit Cygwin environment. Any idea on solving this problem? Thanks for any suggestion. Jyhshyong I would start by removing arguments and trying to determine which are causing the problem. Note that (I believe) what shows up in the system try is not the XTerm, but the XServer (XWin). While the XServer is running, you can run a client, like XTerm and it will display on the XServer display. Here is the shortcut I'm using to launch an XTerm under 64-bit cygwin: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls This is working fine for me. You can also check the /var/log/xwin/XWinwhatever.log file to see if there are any errors being written there when you try to launch the XTerm. Good luck. -- 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/
Re: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64
On Wed, Mar 19, 2014 at 04:25:44PM -0700, Mark Hansen wrote: On 3/19/2014 3:21 PM, Jyhshyong wrote: Hi I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that the Xterm in the system tray icon is no longer working. The Xwin server system tray icon has the following target C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe It works fine as the 32-bit version, click on the icon, I can start X server and open a small Xterm window. However, the Xterm system tray icon with the target defined as C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' I don't see anything wrong with the command-line, but it's been a while since I updated Cygwin packages (and I'm not in the middle of a release cycle), so I'll do that to see if it breaks for me. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 11:57 AM, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. I just installed the 64-bit version of Cygwin to another 64-bit Windows 7 PC, and it did not have this problem. After the installation was finished, my user was configured in the /etc/passwd file and did not have the mkgroup group. Instead, it was set to 513 (None), which I guess is okay - at least I don't get the error when launching a shell. I don't think I did anything different during the installation other than just getting a later version (I downloaded the software on 3/15/2014). FYI -- 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/
Re: Problem with Multi-Key Sequences... They Seem To Be Filtered Out By XWin
On 06/03/2014 22:25, Cutler, David (NonStop) wrote: I downloaded a new copy of Cygwin in the last 5 days (effectively started from scratch) and am trying to use XWin on a Windows 7 virtual machine running an old proprietary X program (it's called x6530 which is a terminal emulator for a proprietary terminal built originally by Tandem Computers and now owned by Hewlett Packard.) I start up the server and window manager using the following command: /usr/bin/setsid \ /usr/bin/XWin \ -mwextwm \ -multimonitors \ -internalwm \ -nowinkill \ While probably not the cause of your problems, -mwextwm is an experimental option and -internalwm is undocumented. I think you should get the same effect with just '-multiwindow -nowinkill' I'm trying to use multi-key sequences like Control_L-Alt_L-F6, Shift_L-Control_L-F6, etc. I do see that xev recognizes these sequences but the Control_L and Alt_L keys seem to be filtered out when I run x6530. All it seems to get is F6 or Shift_L-F6. I've tried different window managers, run /usr/bin/XWin directly, used the right-hand modification keys like Control_R, etc. and no matter what I try, I see the same filtering behavior in x6530.I have recently used exceed (formally owned by Hummingbird) with x6530 and the Control_L and Alt_L keys are passed to x6530 as expected so my suspicion is that XWin is responsible for the unwanted behavior of filtering out the keys like Control_L and Alt_L keys. Is this the case? Is there a way to get these sequences unfiltered. The evidence doesn't really support your conclusion: If one X client (xev) gets these key events, why would the X server not send them to a different X client (x6530)? However, it's perfectly possibly that they aren't sent in the expected form, or some other problem. I guess that x6530 is running on a remote host, so the details of that remote host might be pertinent. FAQ 5.1.8 [1] and the linked email thread may be relevant. If you still have access to the working setup, you might want to compare the xev output for these keys to see if there any differences. You might also consider using wireshark, xmon or xscope to examine the protocol interactions between client and server to see if there is any difference there. If there is additional information I can provide, please let me know. It would be nice to see /var/log/xwin/XWin.0.log just to see what keyboard configuration is being used by the X server etc. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#alt-gr-with-old-x -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. (I don't know about this one) Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 (from yesterday) I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I'd try putting -e before the /bin/zsh, which moves it away from the bug noted. (actually, the trailing -l doesn't look right either) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 11:57 AM, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I've searched for this XTERM_SHELL error, but can't find anything. Can anybody help me? Thanks, Well, I did the following two things: 1. I changed the group id for my entry in the /etc/passwd file from 10530 (or whatever that value was) to 545 (Users) and the first error went away. 2. I changed the shortcut I use to launch the XTerms and removed the shell name at the end, so it now looks like this: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls and now the XTerm is started without any errors. I guess it's working now, but I'm curious why these problems happened on the laptop installation and not on the desktop installation. Especially why the XTerm launch command had to change. The one I showed first I've been using for years without problems. I don't remember how I came up with it now, but I remember spending a lot of time putting that together. Also, that original launch command is working on my other PC (the desktop) as well as my other machines running the 32-bit version of Cygwin. Thanks for any feedback/clarification. -- 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/
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 1:49 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. (I don't know about this one) Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 (from yesterday) I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I'd try putting -e before the /bin/zsh, which moves it away from the bug noted. (actually, the trailing -l doesn't look right either) Thanks. I think the -l was to cause a login shell, but I see now that is what the -ls argument does. Since I removed the shell argument (/bin/zsh -l) it is now working. I'm getting the shell I want, I suspect, because that is the shell mentioned in the /etc/passwd file for my user. As a result, it is working so I'll leave it alone. fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? Thanks for your help! -- 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/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: As a result, it is working so I'll leave it alone. :-) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? yes - I finished #302 at the beginning of the week. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 2:12 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: As a result, it is working so I'll leave it alone. :-) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? yes - I finished #302 at the beginning of the week. Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. I'm confused... FYI. -- 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/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. xterm handles these three cases differently: xterm xterm /bin/zsh xterm -e /bin/zsh The bug that I mentioned is in the second case - not in the other two. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 4:36 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. xterm handles these three cases differently: xterm xterm /bin/zsh xterm -e /bin/zsh The bug that I mentioned is in the second case - not in the other two. Thanks. That was the bug I hit on my laptop. However, my desktop PC was working fine with xterm ... /bin/zsh -l and then suddenly, it started getting the same error. I made the same change to it as I did on my laptop PC and it worked, so I'm not stopped - I'm just wondering how my desktop PC was working then suddenly stopped working without altering any of the Cygwin software or settings. -- 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 Multi-Key Sequences... They Seem To Be Filtered Out By XWin
Hello, I downloaded a new copy of Cygwin in the last 5 days (effectively started from scratch) and am trying to use XWin on a Windows 7 virtual machine running an old proprietary X program (it's called x6530 which is a terminal emulator for a proprietary terminal built originally by Tandem Computers and now owned by Hewlett Packard.) I start up the server and window manager using the following command: /usr/bin/setsid \ /usr/bin/XWin \ -mwextwm \ -multimonitors \ -internalwm \ -nowinkill \ I'm trying to use multi-key sequences like Control_L-Alt_L-F6, Shift_L-Control_L-F6, etc. I do see that xev recognizes these sequences but the Control_L and Alt_L keys seem to be filtered out when I run x6530. All it seems to get is F6 or Shift_L-F6. I've tried different window managers, run /usr/bin/XWin directly, used the right-hand modification keys like Control_R, etc. and no matter what I try, I see the same filtering behavior in x6530.I have recently used exceed (formally owned by Hummingbird) with x6530 and the Control_L and Alt_L keys are passed to x6530 as expected so my suspicion is that XWin is responsible for the unwanted behavior of filtering out the keys like Control_L and Alt_L keys. Is this the case? Is there a way to get these sequences unfiltered. If there is additional information I can provide, please let me know. Thanks for any information you can provide. -David Cutler -- 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/
Re: Problem with xterm-301-1
On Feb 27 17:00, Thomas Dickey wrote: On Thu, Feb 27, 2014 at 06:05:48PM +, Matt Seitz (matseitz) wrote: From: Thomas Dickey [mailto:dic...@his.com] On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote: From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) Is there any ETA for a resolution of this issue? I added that to my changes for #302 yesterday, and have a couple more issues to resolve (probably #302 will be available this weekend) I've been holding off on upgrading to xterm-301 because of this issue. I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own /etc/shells. With #302, this will work: SHELL=whatever xterm but this is a special case (the program will run - a fix - but will need to be in /etc/shells to have xterm set $SHELL): xterm whatever May I politely ask why xterm cares at all? What is the reasoning behind this? Heere's why I'm asking: Xterm is not a login process, like login(1) or sshd(8). If somebody starts xterm, the login process itself has long exec'ed the login shell, and the permission problem what shell is allowed to be started as login shell is done. Afterwards, the user is usually allowed to start whatever process he or she has a right to. It looks really weird to me that a terminal emulator would decide that certain processes are not allowed to a user which otherwise work fine. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpHL4xGcjK9K.pgp Description: PGP signature
RE: Problem with xterm-301-1
From: Thomas Dickey [mailto:dic...@his.com] On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote: From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) Is there any ETA for a resolution of this issue? I've been holding off on upgrading to xterm-301 because of this issue. I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own /etc/shells. -- 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/
Re: Problem with xterm-301-1
On Thu, Feb 27, 2014 at 06:05:48PM +, Matt Seitz (matseitz) wrote: From: Thomas Dickey [mailto:dic...@his.com] On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote: From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) Is there any ETA for a resolution of this issue? I added that to my changes for #302 yesterday, and have a couple more issues to resolve (probably #302 will be available this weekend) I've been holding off on upgrading to xterm-301 because of this issue. I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own /etc/shells. With #302, this will work: SHELL=whatever xterm but this is a special case (the program will run - a fix - but will need to be in /etc/shells to have xterm set $SHELL): xterm whatever -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Problem with xterm-301-1
Hi, After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. /bin/ash /bin/bash /bin/dash /bin/sh /bin/tcsh /bin/zsh Regards, Ola Strömfors -- 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/
Re: Problem with xterm-301-1
On Thu, Feb 20, 2014 at 10:47 AM, Ola Strömfors wrote: After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. I saw the same thing, but only on my home computer running Windows 7 Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit. I start Xwin this way (i.e. same as Cygwin-X group in Start menu): C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I don't know why SHELL defined as /bin/sh by default (my entry in the /etc/passwd file invokes bash). I could not find a way to change SHELL before XWin starts. One way I fixed it was to launch xterm from .XWinrc like this: xterm EXEC xterm -e /bin/bash instead of this: xterm EXEC xterm -ls -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
RE: Problem with xterm-301-1
From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301: Patch #301 - 2014/01/19 only set SHELL environment variable to programs found in /etc/shells (prompted by patch/report by Al Poole). -- 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/
Re: Problem with xterm-301-1
On Thu, Feb 20, 2014 at 11:33:22AM -0700, Jim Reisert AD1C wrote: On Thu, Feb 20, 2014 at 10:47 AM, Ola Strömfors wrote: After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. I saw the same thing, but only on my home computer running Windows 7 Pro 64-bit, not on my work laptop running Windows 7 Enterprise 64-bit. I start Xwin this way (i.e. same as Cygwin-X group in Start menu): C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I don't know why SHELL defined as /bin/sh by default (my entry in the /etc/passwd file invokes bash). I could not find a way to change That sounds like a case reported Saturday - see ftp://invisible-island.net/temp/xterm-301a.patch.gz I have a few other reports on different issues to iron out, and expect to be ok with #302 sometime next week. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem with xterm-301-1
On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote: From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301: Patch #301 - 2014/01/19 only set SHELL environment variable to programs found in /etc/shells (prompted by patch/report by Al Poole). yes. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem with xman-1.1.3-1
On 18/02/2014 07:56, Doran Kangwai wrote: When I use xman 1.1.3-1 to view man pages it renders the pages as postscript. It seems to omit the step to process the PS. Close, but not quite right. groff is not being given the -T option to set the output format, so it's producing the default, ps So I see stuff like this %!PS-Adobe-3.0 %%Creator: groff version 1.22.2 ... ... Using man to display the page works fine. When I use xman 1.1.2-1 the man page is also rendered correctly. Thanks for reporting this problem, and the clear reproduction steps. I can reproduce the problem, and bisecting points to this commit [1], which changes the formatting command used by xman. Yaakov, Attached is trivial patch to fix. If it looks good to you can you apply and rebuild xman? [1] http://cgit.freedesktop.org/xorg/app/xman/commit/?id=d25a3b87ce9fdf950b42f45b644242d72e7167b3 From ea0ecbfa007e03e29f80f976472a28e37cf59931 Mon Sep 17 00:00:00 2001 From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Wed, 19 Feb 2014 14:51:34 + Subject: [PATCH app/xman] Use same FORMAT command on cygwin as on linux in HANDLE_ROFFSEQ case as well Signed-off-by: Jon TURNEY jon.tur...@dronecode.org.uk --- vendor.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vendor.h b/vendor.h index 548ded6..06df38f 100644 --- a/vendor.h +++ b/vendor.h @@ -159,7 +159,7 @@ from the X Consortium. # define REFER refer # if defined(CSRG_BASED) # define FORMAT nroff -mandoc -# elif defined(linux) +# elif defined(linux) || defined(__CYGWIN__) # define FORMAT GROFF_NO_SGR= groff -Tlatin1 -mandoc # elif defined(__DARWIN__) # define FORMAT nroff -man -- 1.8.3.4 -- 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 xman-1.1.3-1
Hi, When I use xman 1.1.3-1 to view man pages it renders the pages as postscript. It seems to omit the step to process the PS. So I see stuff like this %!PS-Adobe-3.0 %%Creator: groff version 1.22.2 ... ... Using man to display the page works fine. When I use xman 1.1.2-1 the man page is also rendered correctly. Steps to repro 1)Install cygwin using setup-x86.exe (version 2.831). I choose all of Base (Default) and from X11 xinit xman xorg-server xorg-server-common xterm X-start-menu-icons 2) Start-Cygwin-X-XWin Server 3) From xterm type xman -notopbox 4) Confirm xman version using Options-Show Version 5) Display man page for cat by Options-Display Directory and selecting cat 6) You should see postscript displayed for xman 1.1.3-1 I downloaded xman-1.2.2-1.tar.bz2 and using xman.exe from there I confirmed that I can successfully see man pages. cygcheck.out and XWin.0.log attached. Note that files contain XXREDACTEDXX where information was redacted. -- Doran Kangwai cygcheck.out Description: Binary data XWin.0.log 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/
Re: Problem opening remote X applications
On 03/01/2014 04:51, Chris Carlson wrote: I just downloaded Cygwin 64-bit for the first time. I've been using Cygwin 32-bit for years. [...] I usually ssh -X remote to a remote Linux machine. I can then read mail (thunderbird), edit documents (LibreOffice 3.x), run Chrome, and edit programs (Emacs). I'll have half a dozen windows open through the X tunnel provided by ssh. Works well and lasts for hours. After upgrading to Cygwin 64-bit (this last weekend), everything *seems* to be okay for a while. After about 20 minutes, though, I can no longer open windows remotely. Even though I have thunderbird currently open, when I try to run Chrome, I get (google-chrome:20006): Gtk-WARNING **: cannot open display: localhost:10.0. If I try to open xclock from the command line, I get: xclock Error: Can't open display: localhost:10.0 Does anybody know what happened? Why has the tunnel disappeared? It hasn't actually disappeared because I'm still running thunderbird through it. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-twenty-minute-timeout Use 'ssh -Y' -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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 opening remote X applications
I just downloaded Cygwin 64-bit for the first time. I've been using Cygwin 32-bit for years. I'm running on Windows 7, and my Cygwin 32-bit has been working reasonably well for a long time. My only issue with it was a problem it had with my Caps Lock key. For whatever reason, focus would switch windows whenever I pressed the Caps Lock key. The caps would lock, but focus would change. I finally decided to download the latest and greatest to see if it has been fixed. It appears that it is no longer an issue. Now I have a new problem. I usually ssh -X remote to a remote Linux machine. I can then read mail (thunderbird), edit documents (LibreOffice 3.x), run Chrome, and edit programs (Emacs). I'll have half a dozen windows open through the X tunnel provided by ssh. Works well and lasts for hours. After upgrading to Cygwin 64-bit (this last weekend), everything *seems* to be okay for a while. After about 20 minutes, though, I can no longer open windows remotely. Even though I have thunderbird currently open, when I try to run Chrome, I get (google-chrome:20006): Gtk-WARNING **: cannot open display: localhost:10.0. If I try to open xclock from the command line, I get: xclock Error: Can't open display: localhost:10.0 Does anybody know what happened? Why has the tunnel disappeared? It hasn't actually disappeared because I'm still running thunderbird through it. Thanks for any assistance on this. Chris -- 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/
Re: Problem trying to build Cygwin X server from source
Jon TURNEY jon.tur...@dronecode.org.uk writes: This looks like [1], a mis-match in TLS-ness between XWin and libglapi. If you are building using the .cygport file it should have ./configure'ed with --disable-glx-tls? [1] http://www.cygwin.com/ml/cygwin-xfree/2011-10/msg00065.html Ah! I had indeed screwed up the configuration -- I was manually building in src using autogen.sh rather than in build and thus had lost the configuration set up by cygport. When I blew everything away and did the cygport stuff again, cd /usr/src/ cygport xorg-server.cygport prep cd /usr/src/ cygport xorg-server.cygport compile things built fine. Thank you for all your help! (To be clear, this didn't work before the 2 patches you had me make.) - Mark -- 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/
Re: Problem trying to build Cygwin X server from source
On 27/10/2013 01:26, Mark Lillibridge wrote: Jon TURNEY writes: You will need to apply the attached change to /usr/include/Xpoll.h to fix xserver compilation with w32api-headers = 3.0.0-1, which adds a new WIN32 define somewhere, which breaks this test. It's /usr/include/X11/Xpoll.h on my system. That patch indeed makes the compilation proceed further. It's now stuck at: Sorry, my mistake. CCLD XWin.exe ../../glx/.libs/libglx.a(glxcmds.o): In function `FlushContext': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:221: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `DoMakeCurrent': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:623: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_WaitGL': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:806: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_CopyContext': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:904: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_SwapBuffers': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:1647: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o):/usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:1851: more undefined references to `__emutls_v._glapi_tls_Dispatch' follow collect2: error: ld returned 1 exit status Makefile:890: recipe for target `XWin.exe' failed This looks like [1], a mis-match in TLS-ness between XWin and libglapi. If you are building using the .cygport file it should have ./configure'ed with --disable-glx-tls? [1] http://www.cygwin.com/ml/cygwin-xfree/2011-10/msg00065.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem trying to build Cygwin X server from source
Jon TURNEY jon.tur...@dronecode.org.uk writes: You will need to apply the attached change to /usr/include/Xpoll.h to fix xserver compilation with w32api-headers = 3.0.0-1, which adds a new WIN32 define somewhere, which breaks this test. It's /usr/include/X11/Xpoll.h on my system. That patch indeed makes the compilation proceed further. It's now stuck at: CCLD XWin.exe ../../glx/.libs/libglx.a(glxcmds.o): In function `FlushContext': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:221: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `DoMakeCurrent': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:623: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_WaitGL': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:806: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_CopyContext': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:904: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o): In function `_glXDisp_SwapBuffers': /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:1647: undefined reference to `__emutls_v._glapi_tls_Dispatch' ../../glx/.libs/libglx.a(glxcmds.o):/usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/glx/glxcmds.c:1851: more undefined references to `__emutls_v._glapi_tls_Dispatch' follow collect2: error: ld returned 1 exit status Makefile:890: recipe for target `XWin.exe' failed Tip: Use setup -q -Ppackagename,packagename,etc. to quickly install the required packages. Darn if I could make this work no matter what I tried. Really, you should just give the actual code here so people can cut-and-paste. Ideally, you should also specify how to get the needed packages via the setup GUI. It's not really the function of that document to tell people how to install packages on cygwin. I don't really want to put the package list there twice and have to keep both copies updated. If you're doing the package installation manually, you just find them (perhaps using the search function), and select them for installation. I found that tip useless as in I couldn't make any form of setup -q -Pfoo install a package. As for the GUI, I believe I just set: * X11, editors, shells, net: install * X11-xorg-server: source * devel: install [need for cygport] * Python: install [for lxml for X server compiling] This is *way* easier than trying to find the dozens of packages by name and trying to figure out what to check to get them. - Mark -- 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/
Re: Problem trying to build Cygwin X server from source
/fcntl.h:14, from /usr/include/X11/Xos.h:88, from win.h:152, from winauth.c:35: You will need to apply the attached change to /usr/include/Xpoll.h to fix xserver compilation with w32api-headers = 3.0.0-1, which adds a new WIN32 define somewhere, which breaks this test. Any suggestions? The online documentation is seriously out of date, predating the use of cygport. Which documentation, specifically? Hmmm. You didn't just update the documentation on me did you? The versions Google is giving me now are up-to-date. Page 9 of http://x.cygwin.com/docs/cg/cygwin-x-cg.pdf says: Tip: Use setup -q -Ppackagename,packagename,etc. to quickly install the required packages. Darn if I could make this work no matter what I tried. Really, you should just give the actual code here so people can cut-and-paste. Ideally, you should also specify how to get the needed packages via the setup GUI. It's not really the function of that document to tell people how to install packages on cygwin. I don't really want to put the package list there twice and have to keep both copies updated. If you're doing the package installation manually, you just find them (perhaps using the search function), and select them for installation. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer From 5c0c8f0a903a69313bb44b561be592e6db2c6c38 Mon Sep 17 00:00:00 2001 From: Jon TURNEY jon.tur...@dronecode.org.uk Date: Fri, 27 Sep 2013 14:41:57 +0100 Subject: [PATCH proto/x11proto] Fix WIN32 check Even if WIN32 is defined (because we have included windows.h somewhere), we want to use the UNIX-like select() interface on Cygwin This seems to be needed to compile xorg-server with MinGW-w64 w32api-headers 3.0.0, which add a new WIN32 define somewhere. Signed-off-by: Jon TURNEY jon.tur...@dronecode.org.uk --- Xpoll.h.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Xpoll.h.in b/Xpoll.h.in index 8275658..0a05424 100644 --- a/Xpoll.h.in +++ b/Xpoll.h.in @@ -50,7 +50,7 @@ from The Open Group. #ifndef _XPOLL_H_ #define _XPOLL_H_ -#ifndef WIN32 +#if !defined(WIN32) || defined(__CYGWIN__) #ifndef USE_POLL -- 1.8.3.4 -- 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/
Re: Problem trying to build Cygwin X server from source
/Xwinsock.h:55:0, from /usr/include/X11/Xpoll.h:163, from ../../os/osdep.h:85, from winauth.c:39: /usr/lib/gcc/i686-pc-cygwin/4.7.3/../../../../include/w32api/winsock2.h:1004:34: error: conflicting types for ‘gethostname’ In file included from /usr/include/unistd.h:4:0, from /usr/include/X11/Xos.h:89, from win.h:152, from winauth.c:35: /usr/include/sys/unistd.h:238:6: note: previous declaration of ‘gethostname’ was here winauth.c: In function ‘winGenerateAuthorization’: winauth.c:132:38: warning: passing argument 2 of ‘GenerateAuthorization’ discards ‘const’ qualifier from pointer target type [enabled by default] winauth.c:108:1: note: expected ‘char *’ but argument is of type ‘const char *’ winauth.c: In function ‘winSetAuthorization’: winauth.c:189:23: warning: passing argument 1 of ‘XSetAuthorization’ discards ‘const’ qualifier from pointer target type [enabled by default] winauth.c:42:13: note: expected ‘char *’ but argument is of type ‘const char *’ Makefile:966: recipe for target `winauth.o' failed make[2]: *** [winauth.o] Error 1 make[2]: Leaving directory `/usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/hw/xwin' Makefile:1082: recipe for target `all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/hw/xwin' Makefile:805: recipe for target `all' failed make: *** [all] Error 2 Any suggestions? The online documentation is seriously out of date, predating the use of cygport. Which documentation, specifically? Hmmm. You didn't just update the documentation on me did you? The versions Google is giving me now are up-to-date. Page 9 of http://x.cygwin.com/docs/cg/cygwin-x-cg.pdf says: Tip: Use setup -q -Ppackagename,packagename,etc. to quickly install the required packages. Darn if I could make this work no matter what I tried. Really, you should just give the actual code here so people can cut-and-paste. Ideally, you should also specify how to get the needed packages via the setup GUI. - Mark -- 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/
Re: Problem trying to build Cygwin X server from source
On 19/10/2013 20:54, Mark Lillibridge wrote: This is xserver-cygwin-1.14.3-1, the latest as of several weeks ago. The part that is failing (make done in /usr/src/xorg-server-1.14.3-1/src/xserver-cygwin-1.14.3-1/hw/xwin/glx): CC wgl_ext_api.lo In file included from wgl_ext_api.c:72:0: generated_wgl_wrappers.c:79:1: error: unknown type name 'PFNWGLDXSETRESOURCESHAREHANDLENVPROC' generated_wgl_wrappers.c:79:1: warning: initialization makes integer from pointer without a cast [enabled by default] generated_wgl_wrappers.c:80:1: error: unknown type name 'PFNWGLDXOPENDEVICENVPROC' generated_wgl_wrappers.c:80:1: warning: initialization makes integer from pointer without a cast [enabled by default] generated_wgl_wrappers.c:81:1: error: unknown type name 'PFNWGLDXCLOSEDEVICENVPROC' generated_wgl_wrappers.c:81:1: warning: initialization makes integer from pointer without a cast [enabled by default] ... I think this is error is due to the khronos-opengl-registry package being more recent than the wglext.h provided by w32api-headers. I think the easiest way to work around this is to update wglext.h from http://www.opengl.org/registry/api/GL/wglext.h Any suggestions? The online documentation is seriously out of date, predating the use of cygport. Which documentation, specifically? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: fltk / gl rendering problem
On 23/06/2013 14:56, marco atzeri wrote: Il 6/21/2013 1:32 PM, Jon TURNEY ha scritto: On 17/06/2013 07:48, marco atzeri wrote: Il 6/16/2013 4:51 PM, marco atzeri ha scritto: testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. Thanks for reporting this and thanks for providing the test binaries. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. I guess this should read with -nowgl, in which case, this is a limitation of the current implementation of -wgl mode, which will require lots of work to fix. Question: is -wgl disabled by some of the other Xwin options ? I was sure all my previous experiments where with -wgl But I see no difference between xwin -rootless -nowgl and xwin -rootless -wgl is only available in -multiwindow mode: (II) GLX: Initialized Win32 native WGL GL provider for screen 0 If you try it in any other mode, you'll get the following in the log: (EE) AIGLX: No native OpenGL in modes with a root window ... (II) AIGLX: Loaded and initialized swrast This could probably do with being better documented. The reason for this restriction is that the only way to constrain OpenGL drawing to a given region is make a Windows window which occupies that region. In the initial WGL implementation, these Windows windows were the ones corresponding to the top-level X windows we have in multiwindow mode. I subsequently added a bit of trickery which makes things somewhat work for non-top-level X windows, by creating a hidden Windows window hierarchy, which puts a Windows window in the right place to make the OpenGL drawing appear in the right place and at the right size, but because that drawing isn't composed into the X screen, but drawn on top of it, we get these issues. In theory this trick could be extended to provide WGL in modes other than multiwindow, but these issues would also appear. I wrote a bit about these limitations at [1] [1] http://www.cygwin.com/ml/cygwin-xfree/2012-10/msg9.html It seems the same defect so it seems related to -wgl, at least in multiwindow mode. Testing with xwin -multiwindow the moving defect is present and slide layer are drawn xwin -multiwindow -nowgl the moving defect is NOT present but the slide layer are NOT drawn ( same for both xwin -rootless -nowgl and xwin -rootless ) further experiment showed that the defect is present when the integrate windows manager is used. With external window manager (fvwm, openbox,.. ) that defect does not apper. With external window manager another defect appears, the upper bar effect is not shown at all; while it is present on the integrated window manager. When I tested this, it looks like the solid area controlled by the sides slider didn't get rendered into a separate layer when using software rendering (either -nowgl or X server in windowed mode), so this is possibly some bug or limitation in the software renderer, or possibly in a bug in the demo not recognizing the lack of capabilities of the software renderer. Do you mean more likely a OpenGL bug of fltk one ? One or the other, yes :) In a brief test, the gl_overlay demo appears the same using the software renderer under linux. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: fltk / gl rendering problem
Op 2013-06-24 17:18, Jon TURNEY schreef: On 23/06/2013 14:56, marco atzeri wrote: Il 6/21/2013 1:32 PM, Jon TURNEY ha scritto: On 17/06/2013 07:48, marco atzeri wrote: Il 6/16/2013 4:51 PM, marco atzeri ha scritto: testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. Thanks for reporting this and thanks for providing the test binaries. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. I guess this should read with -nowgl, in which case, this is a limitation of the current implementation of -wgl mode, which will require lots of work to fix. Question: is -wgl disabled by some of the other Xwin options ? I was sure all my previous experiments where with -wgl But I see no difference between xwin -rootless -nowgl and xwin -rootless -wgl is only available in -multiwindow mode: (II) GLX: Initialized Win32 native WGL GL provider for screen 0 If you try it in any other mode, you'll get the following in the log: (EE) AIGLX: No native OpenGL in modes with a root window ... (II) AIGLX: Loaded and initialized swrast This could probably do with being better documented. The reason for this restriction is that the only way to constrain OpenGL drawing to a given region is make a Windows window which occupies that region. In the initial WGL implementation, these Windows windows were the ones corresponding to the top-level X windows we have in multiwindow mode. I subsequently added a bit of trickery which makes things somewhat work for non-top-level X windows, by creating a hidden Windows window hierarchy, which puts a Windows window in the right place to make the OpenGL drawing appear in the right place and at the right size, but because that drawing isn't composed into the X screen, but drawn on top of it, we get these issues. In theory this trick could be extended to provide WGL in modes other than multiwindow, but these issues would also appear. I wrote a bit about these limitations at [1] [1] http://www.cygwin.com/ml/cygwin-xfree/2012-10/msg9.html It seems the same defect so it seems related to -wgl, at least in multiwindow mode. Testing with xwin -multiwindow the moving defect is present and slide layer are drawn xwin -multiwindow -nowgl the moving defect is NOT present but the slide layer are NOT drawn ( same for both xwin -rootless -nowgl and xwin -rootless ) further experiment showed that the defect is present when the integrate windows manager is used. With external window manager (fvwm, openbox,.. ) that defect does not apper. With external window manager another defect appears, the upper bar effect is not shown at all; while it is present on the integrated window manager. When I tested this, it looks like the solid area controlled by the sides slider didn't get rendered into a separate layer when using software rendering (either -nowgl or X server in windowed mode), so this is possibly some bug or limitation in the software renderer, or possibly in a bug in the demo not recognizing the lack of capabilities of the software renderer. Do you mean more likely a OpenGL bug of fltk one ? One or the other, yes :) In a brief test, the gl_overlay demo appears the same using the software renderer under linux. Not sure whether this is related, this one is not specific to OpenGL, but I had a rendering issue as well http://www.fltk.org/str.php?L2845 Teun -- 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/
Re: fltk / gl rendering problem
Il 6/21/2013 1:32 PM, Jon TURNEY ha scritto: On 17/06/2013 07:48, marco atzeri wrote: Il 6/16/2013 4:51 PM, marco atzeri ha scritto: testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. Thanks for reporting this and thanks for providing the test binaries. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. I guess this should read with -nowgl, in which case, this is a limitation of the current implementation of -wgl mode, which will require lots of work to fix. Question: is -wgl disabled by some of the other Xwin options ? I was sure all my previous experiments where with -wgl But I see no difference between xwin -rootless -nowgl and xwin -rootless I wrote a bit about these limitations at [1] [1] http://www.cygwin.com/ml/cygwin-xfree/2012-10/msg9.html It seems the same defect so it seems related to -wgl, at least in multiwindow mode. Testing with xwin -multiwindow the moving defect is present and slide layer are drawn xwin -multiwindow -nowgl the moving defect is NOT present but the slide layer are NOT drawn ( same for both xwin -rootless -nowgl and xwin -rootless ) further experiment showed that the defect is present when the integrate windows manager is used. With external window manager (fvwm, openbox,.. ) that defect does not apper. With external window manager another defect appears, the upper bar effect is not shown at all; while it is present on the integrated window manager. When I tested this, it looks like the solid area controlled by the sides slider didn't get rendered into a separate layer when using software rendering (either -nowgl or X server in windowed mode), so this is possibly some bug or limitation in the software renderer, or possibly in a bug in the demo not recognizing the lack of capabilities of the software renderer. Do you mean more likely a OpenGL bug of fltk one ? Regards Marco -- 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/
Re: fltk / gl rendering problem
On 17/06/2013 07:48, marco atzeri wrote: Il 6/16/2013 4:51 PM, marco atzeri ha scritto: testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. Thanks for reporting this and thanks for providing the test binaries. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. I guess this should read with -nowgl, in which case, this is a limitation of the current implementation of -wgl mode, which will require lots of work to fix. I wrote a bit about these limitations at [1] [1] http://www.cygwin.com/ml/cygwin-xfree/2012-10/msg9.html further experiment showed that the defect is present when the integrate windows manager is used. With external window manager (fvwm, openbox,.. ) that defect does not apper. With external window manager another defect appears, the upper bar effect is not shown at all; while it is present on the integrated window manager. When I tested this, it looks like the solid area controlled by the sides slider didn't get rendered into a separate layer when using software rendering (either -nowgl or X server in windowed mode), so this is possibly some bug or limitation in the software renderer, or possibly in a bug in the demo not recognizing the lack of capabilities of the software renderer. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: fltk / gl rendering problem
Il 6/16/2013 4:51 PM, marco atzeri ha scritto: Hi, testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. A copy of gl_overlay from fltk-1.3.1.9857-1 build is also uploaded. Regards Marco further experiment showed that the defect is present when the integrate windows manager is used. With external window manager (fvwm, openbox,.. ) that defect does not apper. With external window manager another defect appears, the upper bar effect is not shown at all; while it is present on the integrated window manager. Regards Marco -- 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/
fltk / gl rendering problem
Hi, testing a octave/fltk graphics issue, I noticed that also the demo of fltk with GL interface has a similar issue. On http://matzeri.altervista.org/works/fltk_gl/ I uploaded the before and after apperance of gl_overlay demo. It is enough to move the window to loose the geometrical image while the bars are correctly re-drawn. Running Xwin with -wgl does not show such defect, but it is terribly slow. So I assume it is not a fltk defect but of GL or XServer. A copy of gl_overlay from fltk-1.3.1.9857-1 build is also uploaded. Regards Marco -- 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/
Cygwin X Windows (xterm) and VirtuaWin: How to fix the refresh problem when switching virtual desktops
Hi all in short: To make VirtuaWin refresh windows correctly when switching desktops, generate a window rule that uses Hide by move for the X windows. in more detail: Several people like virtual desktops. On Windows, they can be provided by a tool called VirtuaWin. However, together with Cygwin XServer there are issues with refreshing the X windows when switching desktops. I was annoyed for this known issue since years and every now and then I looked to the internet checking if a solution appeared. Interestingly such a solution exists [1] since years (2009) but I did not find it before - now I am so happy! As this had be questioned on this list but as far as I see without presenting the solution, I decided to write this mail. To make VirtuaWin refresh windows correctly when switching desktops, generate a window rule that uses Hide by move for X windows. This can be done by clicking with the middle mouse button on the title bar of an Cygwin X Windows window, such as an xterm, and select Add Window Rule. In the dialog near bottom there is Method for hiding the window, change it to Hide by move window. Do not forget to press Add and Apply buttons afterwards. With middle-click titlebar and selecting Info it can be verified that instead of Handling: Standard,Standard now there should be Handling Move,. Please note that this might not instantly work for currently opened windows or windows on another desktop. Re-apply the rule on other desktops might help, a forum post [2] suggests rebooting (well, it's Windows). So just in case someone else lives with the same issue, I hope it helped that I repeated (copied) the solution [1] here. Regards, Steffen [1] http://sourceforge.net/projects/virtuawin/forums/forum/257054/topic/3413433 [2] http://sourceforge.net/projects/virtuawin/forums/forum/257054/topic/4089538 -- 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/
Strange xterm scrolling problem introduced in XTerm(289)
A strange scrolling problem seems to have been introduced in XTerm(289) I have a large scrollback buffer. Now when I scroll back my xterm, anything that was previously above the top of the current screen appears indented about 20 spaces: - r w x - - - - - - + 1 r e i s e r t D o m a i n U s e rs 424739 Feb 12 - r w x - - - - - - + 1 r e i s e r t D o m a i n U s e rs 424740 Feb 12 -rwx--+ 1 reisert Domain Users 424749 Feb 12 14:43 callsigns.csv.~29~ -rwx--+ 1 reisert Domain Users 424749 Feb 12 14:44 callsigns.csv Can anyone duplicate this? Note that when I copied/pasted the above lines into gmail, the first two lines (in the scrollback buffer) appeared in a different font than the two lines that were not in the buffer. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
Re: Strange xterm scrolling problem introduced in XTerm(289)
On Tue, Feb 12, 2013 at 4:01 PM, Thomas Dickey wrote: Did you run #288 before this update? (288 had several fixes for Coverity warnings, one of the #289 changes fixed something that I broke in addressing those). I believe I had been running #288 at one point. I just updated Cygwin and could only revert to 287 (not 288). There is no scrollback problem with this version. - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
Re: Strange xterm scrolling problem introduced in XTerm(289)
On Tue, Feb 12, 2013 at 04:22:05PM -0700, Jim Reisert AD1C wrote: On Tue, Feb 12, 2013 at 4:01 PM, Thomas Dickey wrote: Did you run #288 before this update? (288 had several fixes for Coverity warnings, one of the #289 changes fixed something that I broke in addressing those). I believe I had been running #288 at one point. I just updated Cygwin and could only revert to 287 (not 288). There is no scrollback problem with this version. hmm - _looking_ for the problem, I ran uxterm with valgrind (which reported no problem...), but I resized the window back and forth a few times and after several tries, got some debris on the screen which corresponds to what you're describing. (Scrolling with the shifted pageup/pagedown or with the scrollbar didn't produce it; it's the repainting due to resizes dragging text out of the scrollback which gives the result). thanks for the report (I'll work on this now) -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Strange xterm scrolling problem introduced in XTerm(289)
On Tue, Feb 12, 2013 at 06:50:48PM -0500, Thomas Dickey wrote: On Tue, Feb 12, 2013 at 04:22:05PM -0700, Jim Reisert AD1C wrote: On Tue, Feb 12, 2013 at 4:01 PM, Thomas Dickey wrote: Did you run #288 before this update? (288 had several fixes for Coverity warnings, one of the #289 changes fixed something that I broke in addressing those). I believe I had been running #288 at one point. I just updated Cygwin and could only revert to 287 (not 288). There is no scrollback problem with this version. hmm - _looking_ for the problem, I ran uxterm with valgrind (which reported no problem...), but I resized the window back and forth a few times and after several tries, got some debris on the screen which corresponds to what you're describing. (Scrolling with the shifted pageup/pagedown or with the scrollbar didn't produce it; it's the repainting due to resizes dragging text out of the scrollback which gives the result). thanks for the report (I'll work on this now) The problem is that in reverting the change from #282, I missed a piece - will followup with a _short_ patch for #290... -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem with menus in nedit-5.5-5 - cygcheck.out (1/1)
On Sat, 22 Dec 2012 11:43:43 + David Monksfield wrote: Just installed this, and the NEdit background (right-click) menu no longer appears. I'll have to look into that. Also, the menu-bar menus are behaving oddly: clicking on the bar displays the corresponding menu as normal, but if I then click on another menu without selecting anything from the first menu (e.g. click on 'File' and then 'Edit') the second menu does not appear. WFM. Yaakov Cygwin/X -- 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/
Re: Problem with menus in nedit-5.5-5 - cygcheck.out (1/1)
[Apologies - I think something ate the text of my last post, leaving only the attachment] Just installed this, and the NEdit background (right-click) menu no longer appears. Also, the menu-bar menus are behaving oddly: clicking on the bar displays the corresponding menu as normal, but if I then click on another menu without selecting anything from the first menu (e.g. click on 'File' and then 'Edit') the second menu does not appear. I have to click twice more on the second menu to make it appear. I start the X server using 'XWin -multiwindow'. If I revert to nedit-5.5-4, the menus all work as expected. Thanks, David -- 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/
RE: Cygwin/X X Server 1.12.3 Middle Click Problem
Jon, You are brilliant! Thank you. I completely forgot about the pre-installed SetPoint software that came from Dell. As soon as I disabled that... BAM, worked like a charm. Thank you and I apologize for having overlooked something so simple. -T PREVIOUS REPLY: I guess that the problem here isn't Windows 7, but that you have some extra mouse or touchpad software installed which tries to do something 'helpful' like scrolling the window, rather than sending button press/release events when the middle button is clicked. (I don't have anything mentioning auto scroll in the control panel mouse applet on W7) You need to turn off, uninstall or instruct that software to pass middle button clicks to the X server without meddling. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer ORIGINAL MESSAGE: I am running Windows 7 Enterprise SP1 on a Dell Latitude XT2 with an external Dell 3 button (scroll wheel) optical mouse. I have Cygwin package cygwin-1.7.16-1 installed with the packages in the user guide suggested for Xwin capability and SSH. My intention for use is to SSH to a Ubuntu boxes and mostly run Xemacs to program. My main problem is not being able to get the middle click to be recognized in the Xwindows, including xterm local, as a paste. I have tried a different combination of software, namely Xming and Putty, but with no greater success. I also tried an older version of Cygwin from 2010, again to no success. The mouse middle button is recognized by the windows operating system and is in the auto scroll mode under the mouse settings. The scroll functionality is recognized by the Xwindow (xemacs and xterm). But the paste does not work with the middle click. I tried a different mouse, a Logitec optical mouse, and was able to get the Xwindow to recognize a 5th mouse button (unassigned and threw an error in xemacs) when the middle click was set to zoom instead of autoscroll, but alas no paste. So, I have scoured as much google as I can follow and found more than my fair share of suggestions on how to emulate the 3rd button with a double click (left and right) for track pads and other two button appliances, but nothing much to help me diagnose why the middle button does paste with my three button mouse. What further information or tests may I try to figure out what is at the source of this problem? I have attached my cygcheck.out and my XWin.log files as well as the user guide I used to choose the packages (only the ones suggested in the setup). I assume that it is something to do with the Windows 7 operating system, as I have not had the problem in the past on other laptops running Cygwin and external usb mice, nor with other desktops. I have reached the limits of my computing knowledge and would like to inquire as to the community's knowledge of how the program treats the chain of events from middle click to xemacs paste, a chain I am not intimately familiar. Regards, TL P.S. The PDF was not liked in the email so the packages are below (in addition to the default): * xorg-server * xinit * xorg-docs * X-start-menu-icons * openssh * inetutils or rsh -- 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/
Re: Cygwin/X X Server 1.12.3 Middle Click Problem
On 18/11/2012 20:57, Taylor Lilly wrote: I am running Windows 7 Enterprise SP1 on a Dell Latitude XT2 with an external Dell 3 button (scroll wheel) optical mouse. I have Cygwin package cygwin-1.7.16-1 installed with the packages in the user guide suggested for Xwin capability and SSH. My intention for use is to SSH to a Ubuntu boxes and mostly run Xemacs to program. My main problem is not being able to get the middle click to be recognized in the Xwindows, including xterm local, as a paste. I have tried a different combination of software, namely Xming and Putty, but with no greater success. I also tried an older version of Cygwin from 2010, again to no success. The mouse middle button is recognized by the windows operating system and is in the auto scroll mode under the mouse settings. I guess that the problem here isn't Windows 7, but that you have some extra mouse or touchpad software installed which tries to do something 'helpful' like scrolling the window, rather than sending button press/release events when the middle button is clicked. (I don't have anything mentioning auto scroll in the control panel mouse applet on W7) You need to turn off, uninstall or instruct that software to pass middle button clicks to the X server without meddling. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Cygwin/X X Server 1.12.3 Middle Click Problem
On 11/18/2012 12:57 PM, Taylor Lilly wrote: I am running Windows 7 Enterprise SP1 on a Dell Latitude XT2 with an external Dell 3 button (scroll wheel) optical mouse. I have Cygwin package cygwin-1.7.16-1 installed with the packages in the user guide suggested for Xwin capability and SSH. My intention for use is to SSH to a Ubuntu boxes and mostly run Xemacs to program. My main problem is not being able to get the middle click to be recognized in the Xwindows, including xterm local, as a paste. I have tried a different combination of software, namely Xming and Putty, but with no greater success. I also tried an older version of Cygwin from 2010, again to no success. The mouse middle button is recognized by the windows operating system and is in the auto scroll mode under the mouse settings. The scroll functionality is recognized by the Xwindow (xemacs and xterm). But the paste does not work with the middle click. I tried a different mouse, a Logitec optical mouse, and was able to get the Xwindow to recognize a 5th mouse button (unassigned and threw an error in xemacs) when the middle click was set to zoom instead of autoscroll, but alas no paste. So, I have scoured as much google as I can follow and found more than my fair share of suggestions on how to emulate the 3rd button with a double click (left and right) for track pads and other two button appliances, but nothing much to help me diagnose why the middle button does paste with my three button mous e. What further information or tests may I try to figure out what is at the source of this problem? I have attached my cygcheck.out and my XWin.log files as well as the user guide I used to choose the packages (only the ones suggested in the setup). I assume that it is something to do with the Windows 7 operating system, as I have not had the problem in the past on other laptops running Cygwin and external usb mice, nor with other desktops. I have reached the limits of my computing knowledge and would like to inquire as to the community's knowledge of how the program treats the chain of events from middle click to xemacs paste, a chain I am not intimately familiar. Regards, TL Can you try starting the XServer with the -emulate3buttons command-line option? Then you should be able to paste using the L+R mouse buttons clicked simultaneously. My mouse doesn't have a middle mouse button (it is a mechanical switch used to enable/disable the ratcheting on the scroll wheel), so this may not be a good solution for you. Good luck. -- 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/
RE: Cygwin/X X Server 1.12.3 Middle Click Problem
I apologize. I mentioned that I had found the option, but failed to report that I had done it and it worked. Yes, the emulate3button works just fine. However, I was hoping to find some information on diagnosing why the 3 button does not work. For now, it is an excellent work-around, thank you. It has been a bit annoying as my muscle memory remembers third button (middle/scroll click) for paste, but I will get over it. Does anyone have a thought on what I may be able to check with regards to why my middle click does not work in Cygwin/X win? PREVIOUS REPLY: Can you try starting the XServer with the -emulate3buttons command-line option? Then you should be able to paste using the L+R mouse buttons clicked simultaneously. My mouse doesn't have a middle mouse button (it is a mechanical switch used to enable/disable the ratcheting on the scroll wheel), so this may not be a good solution for you. Good luck. ORIGINAL MESSAGE: I am running Windows 7 Enterprise SP1 on a Dell Latitude XT2 with an external Dell 3 button (scroll wheel) optical mouse. I have Cygwin package cygwin-1.7.16-1 installed with the packages in the user guide suggested for Xwin capability and SSH. My intention for use is to SSH to a Ubuntu boxes and mostly run Xemacs to program. My main problem is not being able to get the middle click to be recognized in the Xwindows, including xterm local, as a paste. I have tried a different combination of software, namely Xming and Putty, but with no greater success. I also tried an older version of Cygwin from 2010, again to no success. The mouse middle button is recognized by the windows operating system and is in the auto scroll mode under the mouse settings. The scroll functionality is recognized by the Xwindow (xemacs and xterm). But the paste does not work with the middle click. I tried a different mouse, a Logitec optical mouse, and was able to get the Xwindow to recognize a 5th mouse button (unassigned and threw an error in xemacs) when the middle click was set to zoom instead of autoscroll, but alas no paste. So, I have scoured as much google as I can follow and found more than my fair share of suggestions on how to emulate the 3rd button with a double click (left and right) for track pads and other two button appliances, but nothing much to help me diagnose why the middle button does paste with my three button mouse. What further information or tests may I try to figure out what is at the source of this problem? I have attached my cygcheck.out and my XWin.log files as well as the user guide I used to choose the packages (only the ones suggested in the setup). I assume that it is something to do with the Windows 7 operating system, as I have not had the problem in the past on other laptops running Cygwin and external usb mice, nor with other desktops. I have reached the limits of my computing knowledge and would like to inquire as to the community's knowledge of how the program treats the chain of events from middle click to xemacs paste, a chain I am not intimately familiar. Regards, TL P.S. The PDF was not liked in the email so the packages are below (in addition to the default): * xorg-server * xinit * xorg-docs * X-start-menu-icons * openssh * inetutils or rsh -- 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/
Cygwin/X X Server 1.12.3 Middle Click Problem
I am running Windows 7 Enterprise SP1 on a Dell Latitude XT2 with an external Dell 3 button (scroll wheel) optical mouse. I have Cygwin package cygwin-1.7.16-1 installed with the packages in the user guide suggested for Xwin capability and SSH. My intention for use is to SSH to a Ubuntu boxes and mostly run Xemacs to program. My main problem is not being able to get the middle click to be recognized in the Xwindows, including xterm local, as a paste. I have tried a different combination of software, namely Xming and Putty, but with no greater success. I also tried an older version of Cygwin from 2010, again to no success. The mouse middle button is recognized by the windows operating system and is in the auto scroll mode under the mouse settings. The scroll functionality is recognized by the Xwindow (xemacs and xterm). But the paste does not work with the middle click. I tried a different mouse, a Logitec optical mouse, and was able to get the Xwindow to recognize a 5th mouse button (unassigned and threw an error in xemacs) when the middle click was set to zoom instead of autoscroll, but alas no paste. So, I have scoured as much google as I can follow and found more than my fair share of suggestions on how to emulate the 3rd button with a double click (left and right) for track pads and other two button appliances, but nothing much to help me diagnose why the middle button does paste with my three button mouse. What further information or tests may I try to figure out what is at the source of this problem? I have attached my cygcheck.out and my XWin.log files as well as the user guide I used to choose the packages (only the ones suggested in the setup). I assume that it is something to do with the Windows 7 operating system, as I have not had the problem in the past on other laptops running Cygwin and external usb mice, nor with other desktops. I have reached the limits of my computing knowledge and would like to inquire as to the community's knowledge of how the program treats the chain of events from middle click to xemacs paste, a chain I am not intimately familiar. Regards, TL P.S. The PDF was not liked in the email so the packages are below (in addition to the default): . xorg-server . xinit . xorg-docs . X-start-menu-icons . openssh . inetutils or rsh cygcheck.out Description: cygcheck.out XWin.0.log Description: XWin.0.log XWin.1.log Description: XWin.1.log -- 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/
Re: Problem with geomview under cygwin
Marko, thank you for trying me to help, but I'm totally dummy about linux, cygwin and X Server. Tell me please, how can I downgrade X Server to 1.12.0-5 version. Thanks a lot. Roman. -- 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/
Re: Problem with geomview under cygwin
On 5/31/2012 5:49 PM, tilo wrote: Hello everybody. Please, help me! I'm trying to run SaVi (http://personal.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/) with Geomview under Cygwin environment (http://personal.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/building-under- Windows/) I have followed all the instructions on the page, but one problem occurs when I try to run geomview. I type ./geomview -run $savi1.4.5/savi or ./geomview -run $c:/cygwin/savi1.4.5/savi but xwin crashes with report: A fatal error has occured and Cygwin/X will now exit Caught signal 11(Segmentation Fault). Server aborting from log file: Vendor: the Cygwin/X Project Realese 1.12.1.0 Package: version 1.12.1-1 built 2012-05-02 [ 10481,718] winGetWindowInfo: forcing window to exist [ 10481,718] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10481,718] winGetWindowInfo: forcing window to exist [ 10481,718] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10481,734] wglShareLists error: Неверный дескриптор. (0006) [ 10481,734] winGetWindowInfo: forcing window to exist [ 10481,734] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10482,796] Install gdb to get reasonable backtraces [ 10482,796] /usr/bin/xorg-backtrace failed with returncode 2 [ 10482,796] Segmentation fault at address 0x0 [ 10482,796] Fatal server error: [ 10482,796] Caught signal 11 (Segmentation fault). Server aborting [ 10482,796] [ 10482,796] Server terminated with error (1). Closing log file. if needed, I can post whole log file. Could you try previous X server 1.12.0-5 ? Regards Marco -- 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 geomview under cygwin
Hello everybody. Please, help me! I'm trying to run SaVi (http://personal.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/) with Geomview under Cygwin environment (http://personal.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/building-under- Windows/) I have followed all the instructions on the page, but one problem occurs when I try to run geomview. I type ./geomview -run $savi1.4.5/savi or ./geomview -run $c:/cygwin/savi1.4.5/savi but xwin crashes with report: A fatal error has occured and Cygwin/X will now exit Caught signal 11(Segmentation Fault). Server aborting from log file: Vendor: the Cygwin/X Project Realese 1.12.1.0 Package: version 1.12.1-1 built 2012-05-02 [ 10481,718] winGetWindowInfo: forcing window to exist [ 10481,718] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10481,718] winGetWindowInfo: forcing window to exist [ 10481,718] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10481,734] wglShareLists error: Неверный дескриптор. (0006) [ 10481,734] winGetWindowInfo: forcing window to exist [ 10481,734] winCreateWindowsChildWindow - CreateWindowExA () failed: 1406 [ 10482,796] Install gdb to get reasonable backtraces [ 10482,796] /usr/bin/xorg-backtrace failed with returncode 2 [ 10482,796] Segmentation fault at address 0x0 [ 10482,796] Fatal server error: [ 10482,796] Caught signal 11 (Segmentation fault). Server aborting [ 10482,796] [ 10482,796] Server terminated with error (1). Closing log file. if needed, I can post whole log file. -- 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/
Re: Problem with basic startx and xterm - no cursor or focus
On 5/29/2012 7:18 PM, Patrick Hogan wrote: 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 try using startxwin instead of startx in addition xterm -ls /bin/bash should be better for the shell enviroment in the xterm Regards Marco -- 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/
RE: Problem with basic startx and xterm - no cursor or focus
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? I will only mention that while I am unable to recover from this same problem (rebase/reinstalling/different versions has no effect), installing cygwin and the latest stable packages does not reproduce this problem on other machines. -Justin -- 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/
Re: drag and drop problem between java windows on linux
Luke, I am having the exact problem and the latest Java for Linux did not solve the problem. I think the internal window manager is not recognizing the release event at all. Is anyone having a similar problem? Thanks, Gary -- 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/
Re: drag and drop problem between java windows on linux
After some searching I believe this post is describing the same issue: http://cygwin.com/ml/cygwin-xfree/2009-10/msg00101.html Was there any resolution? This is pretty easy to reproduce with the example given below - it just doesn't seem to recognize the drop event between the drag and drop between 2 java windows in linux. Thanks, Luke On Thu, Mar 1, 2012 at 3:59 AM, L H solderl...@gmail.com wrote: I am using xorg-server-1.10.3-1 under Cygwin in Windows 7 64-bit and have the problem of not being able to drag and drop from 2 different java windows launched off a linux server box. I am using Redhat 5.4 as my linux server that I am displaying from. For example to reproduce the problem: Launch two java Notepad applications (found in java 1.6 SDK under demos/jfc/Notepad/Notepad.jar) to display back to the Windows 7 Cygwin X Server (using the default internal window manager). Put some text in one Notepad application and try to perform a drag n drop to the other Notepad application, it fails. Copy and paste works. Drag n drop inside one notepad works. Drag n drop using different window managers with the above setup works (e.g., OpenBox, twm, etc.) This appears to be another Linux Java related issue similar to the inset menu problem fixed recently on the internal window manager. If I am displaying back QT or GTK windows such as gedit for example then the drag and drop works between the 2 different windows. Thanks, Luke -- 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/
drag and drop problem between java windows on linux
I am using xorg-server-1.10.3-1 under Cygwin in Windows 7 64-bit and have the problem of not being able to drag and drop from 2 different java windows launched off a linux server box. I am using Redhat 5.4 as my linux server that I am displaying from. For example to reproduce the problem: Launch two java Notepad applications (found in java 1.6 SDK under demos/jfc/Notepad/Notepad.jar) to display back to the Windows 7 Cygwin X Server (using the default internal window manager). Put some text in one Notepad application and try to perform a drag n drop to the other Notepad application, it fails. Copy and paste works. Drag n drop inside one notepad works. Drag n drop using different window managers with the above setup works (e.g., OpenBox, twm, etc.) This appears to be another Linux Java related issue similar to the inset menu problem fixed recently on the internal window manager. If I am displaying back QT or GTK windows such as gedit for example then the drag and drop works between the 2 different windows. Thanks, Luke -- 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/
GNU Emacs 23.3.1 problem with 20111213 snapshot
I'm having a problem with the 20111213 snapshot. I'm running GNU Emacs 23.3.1 (emacs-x11) in a Cygwin-X window If I try to reverse-search inside a file (control-R) and the search string is no longer found, after a couple more tries (more control-R), the Emacs window will close and disappear. There is no core dump. Fortunately, the times when this happened, I had already saved the buffer. This is fairly repeatable. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: using putty/brutus and x server
Dear Admin, After looking around at the web and in your faq I was not able to solve my problem. Problem: cannot connect x server to the gaussian gview function on putty/brutus I am trying to use X server 1.11 these are the command lines and answers I get in putty/brutus. * module load gaussian (input) * gview (then the file) (input) * gview: exe cannot connect to X server (answer) I get the same message when Xwin.exe is or is not running. when starting xwin with the cygwin bash shell startxwin.exe startxwin: XFree86_VT property unexpectedly has 0 items instead of 1 For me as a beginner with this program I am not sure what is going on. Im running the program on Win Vista x32 please advice how to solve this problem. Kind Regards Italo Sanhueza ETH Zurich -- 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/
Re: Problem starting XWin Server
Jon TURNEY jon.turney at dronecode.org.uk writes: On 30/07/2011 07:10, Jan Chludzinski wrote: From within a mintty shell, I get: $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. That's odd. I can't really understand how that can happen. I'd suspect that startxwin is failing to fork/exec Xwin successfully, possibly due to an application causing cygwin difficulties [1] (Unfortunately, 64-bit Windows itself seems to sometimes cause similar problems) Are you able to start the server directly by running 'XWin'? [1] http://cygwin.com/faq-nochunks.html#faq.using.bloda I have same issue. I have reinstalled Cygwin 5 times. Each time I can start XWin fine UNTIL I rebaseall or perlrebase or until I uninstall+reinstall perl/Tk. The .log file is from the first couple times it sucessfully came up (prior to the rebase and the errors) and nothing is written to any logfiles or even STDERR/STDOUT except for the: $ xinit giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. or $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. I have added the env variable CYGWIN=tty but still nothing more informative is written to any files or terminal. My hardware is a HP EliteBook sitting on MS XP Pro version 2002 SP3. I have altered the rebaseall script to actually complete, as it is failing on the 64bit dlls. ( added filter to sed to not include the specific dlls from list creation ) I have tried this both ways in 'stock' form from repository and altered to complete. This is 100% reproducible. I can reproduce this every time even with fully fresh installs of cygwin. My goal is to get a version of Cyg X running that I can run cssh and have a full menubar ( this is why the initial rebase and then the subsequent reinstalls and the mucking about with the Perl/Tk stuff ) Thanks for any information in advance, DJ -- 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/
Re: Problem starting XWin Server
On 30/07/2011 07:10, Jan Chludzinski wrote: From within a mintty shell, I get: $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. That's odd. I can't really understand how that can happen. I'd suspect that startxwin is failing to fork/exec Xwin successfully, possibly due to an application causing cygwin difficulties [1] (Unfortunately, 64-bit Windows itself seems to sometimes cause similar problems) Are you able to start the server directly by running 'XWin'? [1] http://cygwin.com/faq-nochunks.html#faq.using.bloda -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem starting XWin Server
From within a mintty shell, I get: $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. ---Jan On Tue, Jul 19, 2011 at 11:31 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 14/07/2011 10:29, Jan Chludzinski wrote: First, THANKS! $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Sorry, I hadn't quite grasped that is the whole of the output. For obscure technical reasons, the output of XWin doesn't appear in a cmd.exe terminal if cygwin wasn't started with CYGWIN=tty. Can I suggest you install mintty, and try running startxwin from that, which should produce some more informative output. It looks like Cygwin/X FAQ 2.4 could do with some improvement :-) The server is never started - no process in the Windows Resource Monitor. When I try to start xedit (or whatever X based app) nothing happens, nothing appears. As for FAQ, I'm afraid I don't see anything that might help. I looked before I posted the original e-mail. ---John On Wed, Jul 13, 2011 at 8:21 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 12/07/2011 09:10, Jan Chludzinski wrote: I just did a complete installation of X11 from Cygwin 1.7 setup.exe. But when I try to start the XWin Server using the Start menu nothing happens. If I try either startxwin or startx or xinit from the BASH shell I get: giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Any suggestions? Looking at the XWin.0.log you attached, it looks like the X server is starting up successfully. If clients are unable to connect, this might be due to firewall configuration or other software which interferes with cygwin sockets (see [1] in the Cygwin/X FAQ for some suggestions) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem starting XWin Server
On 14/07/2011 10:29, Jan Chludzinski wrote: First, THANKS! $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Sorry, I hadn't quite grasped that is the whole of the output. For obscure technical reasons, the output of XWin doesn't appear in a cmd.exe terminal if cygwin wasn't started with CYGWIN=tty. Can I suggest you install mintty, and try running startxwin from that, which should produce some more informative output. It looks like Cygwin/X FAQ 2.4 could do with some improvement :-) The server is never started - no process in the Windows Resource Monitor. When I try to start xedit (or whatever X based app) nothing happens, nothing appears. As for FAQ, I'm afraid I don't see anything that might help. I looked before I posted the original e-mail. ---John On Wed, Jul 13, 2011 at 8:21 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 12/07/2011 09:10, Jan Chludzinski wrote: I just did a complete installation of X11 from Cygwin 1.7 setup.exe. But when I try to start the XWin Server using the Start menu nothing happens. If I try either startxwin or startx or xinit from the BASH shell I get: giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Any suggestions? Looking at the XWin.0.log you attached, it looks like the X server is starting up successfully. If clients are unable to connect, this might be due to firewall configuration or other software which interferes with cygwin sockets (see [1] in the Cygwin/X FAQ for some suggestions) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem starting XWin Server
First, THANKS! $ startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. The server is never started - no process in the Windows Resource Monitor. When I try to start xedit (or whatever X based app) nothing happens, nothing appears. As for FAQ, I'm afraid I don't see anything that might help. I looked before I posted the original e-mail. ---John On Wed, Jul 13, 2011 at 8:21 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 12/07/2011 09:10, Jan Chludzinski wrote: I just did a complete installation of X11 from Cygwin 1.7 setup.exe. But when I try to start the XWin Server using the Start menu nothing happens. If I try either startxwin or startx or xinit from the BASH shell I get: giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Any suggestions? Looking at the XWin.0.log you attached, it looks like the X server is starting up successfully. If clients are unable to connect, this might be due to firewall configuration or other software which interferes with cygwin sockets (see [1] in the Cygwin/X FAQ for some suggestions) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Problem starting XWin Server
On 12/07/2011 09:10, Jan Chludzinski wrote: I just did a complete installation of X11 from Cygwin 1.7 setup.exe. But when I try to start the XWin Server using the Start menu nothing happens. If I try either startxwin or startx or xinit from the BASH shell I get: giving up. startxwin: No such file or directory (errno 2): unable to connect to X server startxwin: No such process (errno 3): Server error. Any suggestions? Looking at the XWin.0.log you attached, it looks like the X server is starting up successfully. If clients are unable to connect, this might be due to firewall configuration or other software which interferes with cygwin sockets (see [1] in the Cygwin/X FAQ for some suggestions) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: mintty problem with tail -f on Windows XP with virtual desktops
On 31 March 2011 19:45, Larry Breyer wrote: I am really glad I switched from rxvt to mintty as it works great with or without X11. I am seeing one problem, though, where I wonder if there is a fix. Mintty isn't actually an X11 program, so cygwin-xfree is the wrong list for this. Please send followups to the cygwin mailing list or the mintty discussion group. I have observed the problem when switching between virtual desktops for both Windows Desktop Manager and Dexpot Desktop Manager. By Windows Desktop Manager do you mean the Virtual Desktop Manager powertoy? Which Windows version are we talking about? I frequently remote into servers and run tail -f to monitor various log files. I have noticed when I switched to another virtual desktop, the mintty sessions in the hidden virtual desktops do not get updated. When I switch back to the desktop and hit the enter key within the mintty window it seems to catch up. But, for some reason, the windows display gets jumbled. What exactly is getting jumbled and how? Is there a way to refresh the window such that it looks normal without disturbing the running process (tail)? There are several ways you could force a refresh of mintty's display: - minimize and restore - scroll up and down - flip screen and back (i.e. press Alt+F12 twice) However, none of that should be necessary, i.e. it sounds like there's a bug there somewhere. Do you have transparency enabled in mintty? Does disabling or enabling it make a difference? Regards, Andy -- 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/
mintty problem with tail -f on Windows XP with virtual desktops
I am really glad I switched from rxvt to mintty as it works great with or without X11. I am seeing one problem, though, where I wonder if there is a fix. I have observed the problem when switching between virtual desktops for both Windows Desktop Manager and Dexpot Desktop Manager. I frequently remote into servers and run tail -f to monitor various log files. I have noticed when I switched to another virtual desktop, the mintty sessions in the hidden virtual desktops do not get updated. When I switch back to the desktop and hit the enter key within the mintty window it seems to catch up. But, for some reason, the windows display gets jumbled. Is there a way to refresh the window such that it looks normal without disturbing the running process (tail)? Thank you! -- Larry Breyer Isis Pharmaceuticals Carlsbad, Calif. -- 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/
Re: X server segfault problem
On 05/01/2011 01:32, chm wrote: Final update: I tried on another cygwin install and it worked out of the box with the new XWin.2011 program. Then I went back and tried the original system and it now works as expected. Maybe there was a lingering font connection to the previous XWin.exe. Thanks for the fix, Thanks for testing. I'll make an updated package with this change when I can. I can't offer any insight into your 'font errors' since you didn't provide any details. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: X server segfault problem
On 1/5/2011 12:02 PM, Jon TURNEY wrote: On 05/01/2011 01:32, chm wrote: Final update: I tried on another cygwin install and it worked out of the box with the new XWin.2011 program. Then I went back and tried the original system and it now works as expected. Maybe there was a lingering font connection to the previous XWin.exe. Thanks for the fix, Thanks for testing. I'll make an updated package with this change when I can. Great! I can't offer any insight into your 'font errors' since you didn't provide any details. Since I could not reproduce it, details were difficult. :-) Thanks again, Chris -- 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/
Re: X server segfault problem
On 1/3/2011 2:41 PM, chm wrote: On 1/3/2011 2:32 PM, chm wrote: On 1/3/2011 12:54 PM, chm wrote: On 1/3/2011 11:55 AM, Jon TURNEY wrote: On 02/01/2011 01:11, chm wrote: I'm having a problem with cygwin 1.7.7 and X version 1.9.3.0 where an OpenGL application from perl using the Mesa3D binding dies in the test with a segfault: X related questions belong on the cygwin-xfree list. A fatal error has occurred and Cygwin/X will now exit. Caught signal 11 (Segmentation fault). Server aborting. Please open /var/log/xwin/XWin.0.log for more information. When I close the popup alert, X exits. The XWin.0.log only has Segmentation fault at address 0xe. I've been unable to determine if the problem is in the perl OpenGL module code or in the updated X+GLX+Mesa3D. Even incorrectly written X clients shouldn't make the X server crash, so if the X server crashes, it is an X server problem. To reproduce, just download the perl OpenGL module source: http://search.cpan.org/CPAN/authors/id/C/CH/CHM/OpenGL-0.64.tar.gz and extract the directory. cd to the OpenGL-0.64 directory and run the following command: ( set -x ; perl Makefile.PL ; make ; make test ) 21 | tee ../pogl-x-crash-log.txt which should configure, build and run the test for this module. You will need to have gcc, perl and opengl installed in your cygwin. Any help appreciated since I can no longer develop on cygwin since the X server started crashing...not even to fix the problem (if it is the OpenGL module code). This kind of implies it used to work, but doesn't tell me which version it worked with. It worked with cygwin 1.5.25 and earlier. The X that came with the move to the 1.7.x series was the first that had the crash. Anyhow, I've just fixed an OpenGL related problem which looks similar to this, perhaps you could try the snapshot in [1] and see if that helps. [1] http://cygwin.com/ml/cygwin-xfree/2011-01/msg1.html I assume this is a binary to replace the existing XWin.exejust ran the new XWin.20110102-git-29db9091c6ae4995.exe and the server did not crash when I ran the test. There was a problem with a missing font so the text did not display but I don't know if that was because I did not set something up correctly in just running the XWin program by hand. --Chris I've just added myself to the cygwin-xfree list so this reply should go through now. Took a bit more of a look at the font problem and I don't see anything obvious. The last time I had this problem it was something related to the X font setup. The crashing problem is definitely fixed with this XWin.20110102... I tried passing the new XWin.20110102 as the server option to startxwin but am still getting the font errors. No crashes, though. Final update: I tried on another cygwin install and it worked out of the box with the new XWin.2011 program. Then I went back and tried the original system and it now works as expected. Maybe there was a lingering font connection to the previous XWin.exe. Thanks for the fix, Chris Cheers, Chris -- 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/
Re: X server segfault problem
On 02/01/2011 01:11, chm wrote: I'm having a problem with cygwin 1.7.7 and X version 1.9.3.0 where an OpenGL application from perl using the Mesa3D binding dies in the test with a segfault: X related questions belong on the cygwin-xfree list. A fatal error has occurred and Cygwin/X will now exit. Caught signal 11 (Segmentation fault). Server aborting. Please open /var/log/xwin/XWin.0.log for more information. When I close the popup alert, X exits. The XWin.0.log only has Segmentation fault at address 0xe. I've been unable to determine if the problem is in the perl OpenGL module code or in the updated X+GLX+Mesa3D. Even incorrectly written X clients shouldn't make the X server crash, so if the X server crashes, it is an X server problem. To reproduce, just download the perl OpenGL module source: http://search.cpan.org/CPAN/authors/id/C/CH/CHM/OpenGL-0.64.tar.gz and extract the directory. cd to the OpenGL-0.64 directory and run the following command: ( set -x ; perl Makefile.PL ; make ; make test ) 21 | tee ../pogl-x-crash-log.txt which should configure, build and run the test for this module. You will need to have gcc, perl and opengl installed in your cygwin. Any help appreciated since I can no longer develop on cygwin since the X server started crashing...not even to fix the problem (if it is the OpenGL module code). This kind of implies it used to work, but doesn't tell me which version it worked with. Anyhow, I've just fixed an OpenGL related problem which looks similar to this, perhaps you could try the snapshot in [1] and see if that helps. [1] http://cygwin.com/ml/cygwin-xfree/2011-01/msg1.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: X server segfault problem
On 1/3/2011 11:55 AM, Jon TURNEY wrote: On 02/01/2011 01:11, chm wrote: I'm having a problem with cygwin 1.7.7 and X version 1.9.3.0 where an OpenGL application from perl using the Mesa3D binding dies in the test with a segfault: X related questions belong on the cygwin-xfree list. A fatal error has occurred and Cygwin/X will now exit. Caught signal 11 (Segmentation fault). Server aborting. Please open /var/log/xwin/XWin.0.log for more information. When I close the popup alert, X exits. The XWin.0.log only has Segmentation fault at address 0xe. I've been unable to determine if the problem is in the perl OpenGL module code or in the updated X+GLX+Mesa3D. Even incorrectly written X clients shouldn't make the X server crash, so if the X server crashes, it is an X server problem. To reproduce, just download the perl OpenGL module source: http://search.cpan.org/CPAN/authors/id/C/CH/CHM/OpenGL-0.64.tar.gz and extract the directory. cd to the OpenGL-0.64 directory and run the following command: ( set -x ; perl Makefile.PL ; make ; make test ) 21 | tee ../pogl-x-crash-log.txt which should configure, build and run the test for this module. You will need to have gcc, perl and opengl installed in your cygwin. Any help appreciated since I can no longer develop on cygwin since the X server started crashing...not even to fix the problem (if it is the OpenGL module code). This kind of implies it used to work, but doesn't tell me which version it worked with. It worked with cygwin 1.5.25 and earlier. The X that came with the move to the 1.7.x series was the first that had the crash. Anyhow, I've just fixed an OpenGL related problem which looks similar to this, perhaps you could try the snapshot in [1] and see if that helps. [1] http://cygwin.com/ml/cygwin-xfree/2011-01/msg1.html I assume this is a binary to replace the existing XWin.exejust ran the new XWin.20110102-git-29db9091c6ae4995.exe and the server did not crash when I ran the test. There was a problem with a missing font so the text did not display but I don't know if that was because I did not set something up correctly in just running the XWin program by hand. --Chris P.S. This might bounce from the cygwin-xfree since I don't know if I have sign up for that list. -- 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/
Re: X server segfault problem
On 1/3/2011 12:54 PM, chm wrote: On 1/3/2011 11:55 AM, Jon TURNEY wrote: On 02/01/2011 01:11, chm wrote: I'm having a problem with cygwin 1.7.7 and X version 1.9.3.0 where an OpenGL application from perl using the Mesa3D binding dies in the test with a segfault: X related questions belong on the cygwin-xfree list. A fatal error has occurred and Cygwin/X will now exit. Caught signal 11 (Segmentation fault). Server aborting. Please open /var/log/xwin/XWin.0.log for more information. When I close the popup alert, X exits. The XWin.0.log only has Segmentation fault at address 0xe. I've been unable to determine if the problem is in the perl OpenGL module code or in the updated X+GLX+Mesa3D. Even incorrectly written X clients shouldn't make the X server crash, so if the X server crashes, it is an X server problem. To reproduce, just download the perl OpenGL module source: http://search.cpan.org/CPAN/authors/id/C/CH/CHM/OpenGL-0.64.tar.gz and extract the directory. cd to the OpenGL-0.64 directory and run the following command: ( set -x ; perl Makefile.PL ; make ; make test ) 21 | tee ../pogl-x-crash-log.txt which should configure, build and run the test for this module. You will need to have gcc, perl and opengl installed in your cygwin. Any help appreciated since I can no longer develop on cygwin since the X server started crashing...not even to fix the problem (if it is the OpenGL module code). This kind of implies it used to work, but doesn't tell me which version it worked with. It worked with cygwin 1.5.25 and earlier. The X that came with the move to the 1.7.x series was the first that had the crash. Anyhow, I've just fixed an OpenGL related problem which looks similar to this, perhaps you could try the snapshot in [1] and see if that helps. [1] http://cygwin.com/ml/cygwin-xfree/2011-01/msg1.html I assume this is a binary to replace the existing XWin.exejust ran the new XWin.20110102-git-29db9091c6ae4995.exe and the server did not crash when I ran the test. There was a problem with a missing font so the text did not display but I don't know if that was because I did not set something up correctly in just running the XWin program by hand. --Chris I've just added myself to the cygwin-xfree list so this reply should go through now. Took a bit more of a look at the font problem and I don't see anything obvious. The last time I had this problem it was something related to the X font setup. The crashing problem is definitely fixed with this XWin.20110102... Cheers, Chris P.S. This might bounce from the cygwin-xfree since I don't know if I have sign up for that list. -- 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/
Re: X server segfault problem
On 1/3/2011 2:32 PM, chm wrote: On 1/3/2011 12:54 PM, chm wrote: On 1/3/2011 11:55 AM, Jon TURNEY wrote: On 02/01/2011 01:11, chm wrote: I'm having a problem with cygwin 1.7.7 and X version 1.9.3.0 where an OpenGL application from perl using the Mesa3D binding dies in the test with a segfault: X related questions belong on the cygwin-xfree list. A fatal error has occurred and Cygwin/X will now exit. Caught signal 11 (Segmentation fault). Server aborting. Please open /var/log/xwin/XWin.0.log for more information. When I close the popup alert, X exits. The XWin.0.log only has Segmentation fault at address 0xe. I've been unable to determine if the problem is in the perl OpenGL module code or in the updated X+GLX+Mesa3D. Even incorrectly written X clients shouldn't make the X server crash, so if the X server crashes, it is an X server problem. To reproduce, just download the perl OpenGL module source: http://search.cpan.org/CPAN/authors/id/C/CH/CHM/OpenGL-0.64.tar.gz and extract the directory. cd to the OpenGL-0.64 directory and run the following command: ( set -x ; perl Makefile.PL ; make ; make test ) 21 | tee ../pogl-x-crash-log.txt which should configure, build and run the test for this module. You will need to have gcc, perl and opengl installed in your cygwin. Any help appreciated since I can no longer develop on cygwin since the X server started crashing...not even to fix the problem (if it is the OpenGL module code). This kind of implies it used to work, but doesn't tell me which version it worked with. It worked with cygwin 1.5.25 and earlier. The X that came with the move to the 1.7.x series was the first that had the crash. Anyhow, I've just fixed an OpenGL related problem which looks similar to this, perhaps you could try the snapshot in [1] and see if that helps. [1] http://cygwin.com/ml/cygwin-xfree/2011-01/msg1.html I assume this is a binary to replace the existing XWin.exejust ran the new XWin.20110102-git-29db9091c6ae4995.exe and the server did not crash when I ran the test. There was a problem with a missing font so the text did not display but I don't know if that was because I did not set something up correctly in just running the XWin program by hand. --Chris I've just added myself to the cygwin-xfree list so this reply should go through now. Took a bit more of a look at the font problem and I don't see anything obvious. The last time I had this problem it was something related to the X font setup. The crashing problem is definitely fixed with this XWin.20110102... I tried passing the new XWin.20110102 as the server option to startxwin but am still getting the font errors. No crashes, though. Cheers, Chris P.S. This might bounce from the cygwin-xfree since I don't know if I have sign up for that list. -- 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/
Re: X server segfault problem
On Mon, Jan 03, 2011 at 02:32:15PM -0500, chm wrote: I've just added myself to the cygwin-xfree list so this reply should go through now. You don't have to subscribe to the list to send email. Witness: http://cygwin.com/ml/cygwin-xfree/2011-01/msg3.html -- 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/
libglade2.0_0 problem
Started installing cygwinX on Windows XP August 19 EST 1700h. Used ucalgary.ca mirror Chose default, plus ssh, ssl, vim Download OK, installing Ok, final stages stopped ~1900h Error libglade2.0_0 and libglade2.0.sh 'package does not exist' or words to that effect Hit Back, so lost the exact error message. Oops. What do I do ? Typo in the installation script ? Nick -- 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/
Re: Resizing problem
On Fri, Jul 16, 2010 at 6:10 AM, Olwe Melwasul wrote: So what exactly should I do with make-emacs-shortcut? Run it from the xterm: type its name into xterm and press Enter. -- Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- 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/
Re: Resizing problem
On 7/16/2010 12:10 AM, Olwe Melwasul wrote: On Thu, Jul 15, 2010 at 9:20 PM, Ken Brownkbr...@cornell.edu wrote: I should have added that you should see /usr/share/doc/Cygwin/emacs.README for more information about that script and the shortcut it creates. Ken make-emacs-shortcut was in /bin. There was nothing in the .../README about it, though. README talked about a source code compile and install of Emacs. /bin and /usr/bin are the same (via mount) in Cygwin. If they appear different, then you're looking at them with non-Cygwin tools. And the README for emacs-23.2-1 does talk about make-emacs-shortcut. Under Usage notes it says: 2. The script /usr/bin/make-emacs-shortcut can be used to create a shortcut for starting emacs. As shipped, this shortcut starts emacs under X if an X server is running and in a mintty window otherwise. Edit it as desired. And a little further down it says: In addition, you will need cygutils in order to run the make-emacs-shortcut script described above, and you will need mintty and run2 to use the shortcut it creates. Ken -- 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/
Re: Resizing problem
On 15/07/2010 18:02, Olwe Melwasul wrote: I installed cygwin/xcygwin 1.7.5 with KDE. I don't know where you got KDE from, but it's not in the standard cygwin distribution. If you have problems with KDE, perhaps you should try the place you got it from. I tried clicking on XWin Server from the Start menue, but nothing happened. I tried startx from the cygwin basic terminal. Nothing. After some Google archaeology, I found someone that had done this: cd \cygwin\bin ash PATH=. rebaseall -v at the DOS command. Good. It worked. Running startx at the cygwin command did start a twm session. But how the KDE would run, I couldn't figure out from any amount of documentation or Googling. Given the rest of this email, I find it hard to believe that the documentation you read included 'man Xwin' or the Cygwin/X User Guide [1] If you did, and you found it unclear, I'd welcome your suggestions as to how to improve that documentation. After some more Googling, I saw a reference to an Openbox. Guessing along, I got startx /usr/bin/openbox to give me Openbox. My problem is that I cannot minimize anything because it goes down below and out of sight. Nope. What's happening here is that you have no panel/taskbar running, so there is nothing to show minimized applications. Openbox is just a Window Manager. The XWin container window is sized on start up to my right computer screen, but when I drag it over to my larger left screen, it can't be resized. from 'man XWin': The display mode can not be changed once the X server has started. We do not currently support resizing the X screen of a running X server. I suspect Openbox has a default size larger (lower?) and down in the hidden part is no doubt either a task bar with the minimized apps or the minimized apps themselves, right? Wrong, as explained above. Alt-Tab only cycles the Win7 apps, not the XWin session apps, BTW. This behaviour is by design. [2] If you want to allow the X server to capture alt-tab key presses, you should read about the -keyhook option in 'man XWin': -[no]keyhook: Enable [disable] a low-level keyboard hook for catching special keypresses like Menu and Alt+Tab and passing them to the X Server instead of letting Windows handle them. And indeed 'startx /usr/bin/openbox-session -- -keyhook' gives you an openbox session where you can switch windows using alt-tab. It's kind of unfortunate that the default configuration of openbox and the X server interact in this way to make it difficult to work out how to get your minimized applications back, and we could certainly do with some words in the User's Guide about using the WMs we provide, but that would best be written by someone who actually uses them, which isn't me :-) Actually, I don't need the startx version, I could very well use the startxwin multi-windows version IF I could get Emacs in shell mode to do cygwin bash. Starting the X server and then Emacs multi-windows style gets a shell mode that apparently doesn't see cygwin. I'm guessing it's using the DOS command. How can I a) get at the minimized apps? or b) how can I get a stand-alone X server-run Emacs to see cygwin bash? [1] http://x.cygwin.com/docs/ug/cygwin-x-ug.html [2] http://x.cygwin.com/docs/ug/using-switching.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Resizing problem
On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 15/07/2010 18:02, Olwe Melwasul wrote: I installed cygwin/xcygwin 1.7.5 with KDE. I don't know where you got KDE from, but it's not in the standard cygwin distribution. If you have problems with KDE, perhaps you should try the place you got it from. I tried clicking on XWin Server from the Start menue, but nothing happened. I tried startx from the cygwin basic terminal. Nothing. After some Google archaeology, I found someone that had done this: cd \cygwin\bin ash PATH=. rebaseall -v at the DOS command. Good. It worked. Running startx at the cygwin command did start a twm session. But how the KDE would run, I couldn't figure out from any amount of documentation or Googling. Given the rest of this email, I find it hard to believe that the documentation you read included 'man Xwin' or the Cygwin/X User Guide [1] If you did, and you found it unclear, I'd welcome your suggestions as to how to improve that documentation. I don't think I'd want to try. I'd likely have too many questions. And my feelings would either be bolstered by people like Ken Brown who answered these initial questions promptly and accurately with patience, or trampled rudely and brusquely as is Jon Turney's habit. Yes, I've seen other Jon Turney's responses, and they're not winning the cygwin cause many friends. I'm not your typical newbie from hell, and if I'm having this level of trouble with cygwin/Xcygwin out of the box, let that be a barometer that your product lacks proper documentation. After all, how many casual Windows users curious about GNU/Linux who found Xcygwin not working out of the box (still not working after reading your spotty Xcygwin user's guide) would have Googled around for a solution? I found the rebase all and it worked. Why? I still don't know. But do you expect a real beginner to have gone to those lengths? As for where I got my distro, I chose the ucalgary mirror because it's one of the closest to me here in Minnesota. If the ucalgary mirror is dealing bad source, is that my fault? I'm a GNU/Linux user who has to teach a course on GNU text/file manipulation tools to students who've never seen GNU/Linux and will probably not want to install it on their laptops. Therefore I have to get cygwin going on their computers. I think I can limp along now After some more Googling, I saw a reference to an Openbox. Guessing along, I got startx /usr/bin/openbox to give me Openbox. My problem is that I cannot minimize anything because it goes down below and out of sight. Nope. What's happening here is that you have no panel/taskbar running, so there is nothing to show minimized applications. Openbox is just a Window Manager. The XWin container window is sized on start up to my right computer screen, but when I drag it over to my larger left screen, it can't be resized. from 'man XWin': The display mode can not be changed once the X server has started. We do not currently support resizing the X screen of a running X server. I suspect Openbox has a default size larger (lower?) and down in the hidden part is no doubt either a task bar with the minimized apps or the minimized apps themselves, right? Wrong, as explained above. Alt-Tab only cycles the Win7 apps, not the XWin session apps, BTW. This behaviour is by design. [2] If you want to allow the X server to capture alt-tab key presses, you should read about the -keyhook option in 'man XWin': -[no]keyhook: Enable [disable] a low-level keyboard hook for catching special keypresses like Menu and Alt+Tab and passing them to the X Server instead of letting Windows handle them. And indeed 'startx /usr/bin/openbox-session -- -keyhook' gives you an openbox session where you can switch windows using alt-tab. It's kind of unfortunate that the default configuration of openbox and the X server interact in this way to make it difficult to work out how to get your minimized applications back, and we could certainly do with some words in the User's Guide about using the WMs we provide, but that would best be written by someone who actually uses them, which isn't me :-) Actually, I don't need the startx version, I could very well use the startxwin multi-windows version IF I could get Emacs in shell mode to do cygwin bash. Starting the X server and then Emacs multi-windows style gets a shell mode that apparently doesn't see cygwin. I'm guessing it's using the DOS command. How can I a) get at the minimized apps? or b) how can I get a stand-alone X server-run Emacs to see cygwin bash? [1] http://x.cygwin.com/docs/ug/cygwin-x-ug.html [2] http://x.cygwin.com/docs/ug/using-switching.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ
Re: Resizing problem
On 16 July 2010 15:39, Olwe Melwasul wrote: On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY wrote: I installed cygwin/xcygwin 1.7.5 with KDE. I don't know where you got KDE from, but it's not in the standard cygwin distribution. If you have problems with KDE, perhaps you should try the place you got it from. I tried clicking on XWin Server from the Start menue, but nothing happened. I tried startx from the cygwin basic terminal. Nothing. After some Google archaeology, I found someone that had done this: cd \cygwin\bin ash PATH=. rebaseall -v at the DOS command. Good. It worked. Running startx at the cygwin command did start a twm session. But how the KDE would run, I couldn't figure out from any amount of documentation or Googling. Given the rest of this email, I find it hard to believe that the documentation you read included 'man Xwin' or the Cygwin/X User Guide [1] If you did, and you found it unclear, I'd welcome your suggestions as to how to improve that documentation. I don't think I'd want to try. I'd likely have too many questions. And my feelings would either be bolstered by people like Ken Brown who answered these initial questions promptly and accurately with patience, or trampled rudely and brusquely as is Jon Turney's habit. Yes, I've seen other Jon Turney's responses, and they're not winning the cygwin cause many friends. That's both insulting and untrue. Jon's doing a great job maintaining and supporting one of the most complex pieces of Cygwin, and as far as I remember, his responses are always helpful and accurate. You did get answers to your questions, and Jon acknowledged that the documentation needs improvement, so what exactly are you taking umbrage at anyway? The suggestion that reading the actual manual instead of just googling around might have helped? I'm a GNU/Linux user who has to teach a course on GNU text/file manipulation tools to students who've never seen GNU/Linux and will probably not want to install it on their laptops. You do realise that you don't need Cygwin/X to run a Cygwin console or terminal? Andy -- 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/
Re: Resizing problem
On 7/16/2010 10:39 AM, Olwe Melwasul wrote: On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY wrote: ^ http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. On 15/07/2010 18:02, Olwe Melwasul wrote: I installed cygwin/xcygwin 1.7.5 with KDE. I don't know where you got KDE from, but it's not in the standard cygwin distribution. If you have problems with KDE, perhaps you should try the place you got it from. snip I'm not your typical newbie from hell, and if I'm having this level of trouble with cygwin/Xcygwin out of the box, let that be a barometer that your product lacks proper documentation. After all, how many casual Windows users curious about GNU/Linux who found Xcygwin not working out of the box (still not working after reading your spotty Xcygwin user's guide) would have Googled around for a solution? I found the rebase all and it worked. Why? I still don't know. But do you expect a real beginner to have gone to those lengths? As for where I got my distro, I chose the ucalgary mirror because it's one of the closest to me here in Minnesota. If the ucalgary mirror is dealing bad source, is that my fault? No but I just checked the calgary mirror and it contains only some qt3 and qt4 packages, albeit under the heading of KDE. Still, there is no KDE window manager or other goodies there so if you really have KDE installed (which is available from http://sourceware.org/cygwinports/), you didn't get it from the Cygwin distribution, which is the main thing that Jon was pointing out. While you can't be held responsible for the state of software found on some mirror, it's also not fair to hold the Cygwin community responsible for software that it doesn't distribute. You want to go to the source for support in the case of packages that are outside the Cygwin distribution. Your issue requiring rebase is a known one. Unfortunately, it's hard to fix and it's not possible to predict which installations will have problems (though typically those with more packages and those containing packages from other sources will likely have more trouble). This isn't just a Cygwin-X issue though. It's a Cygwin issue in general. Anyway, I'm just clarifying some about what you saw rather than providing any silver bullets to address it. We're still looking for those silver bullets. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/
Re: Resizing problem
On Fri, Jul 16, 2010 at 04:39:58PM +0100, Andy Koppe wrote: On 16 July 2010 15:39, Olwe Melwasul wrote: On Fri, Jul 16, 2010 at 8:50 AM, Jon TURNEY wrote: I installed cygwin/xcygwin 1.7.5 with KDE. I don't know where you got KDE from, but it's not in the standard cygwin distribution. ??If you have problems with KDE, perhaps you should try the place you got it from. I tried clicking on XWin Server from the Start menue, but nothing happened. I tried startx from the cygwin basic terminal. Nothing. After some Google archaeology, I found someone that had done this: cd \cygwin\bin ash PATH=. rebaseall -v at the DOS command. Good. It worked. Running startx at the cygwin command did start a twm session. But how the KDE would run, I couldn't figure out from any amount of documentation or Googling. Given the rest of this email, I find it hard to believe that the documentation you read included 'man Xwin' or the Cygwin/X User Guide [1] If you did, and you found it unclear, I'd welcome your suggestions as to how to improve that documentation. I don't think I'd want to try. I'd likely have too many questions. And my feelings would either be bolstered by people like Ken Brown who answered these initial questions promptly and accurately with patience, or trampled rudely and brusquely as is Jon Turney's habit. Yes, I've seen other Jon Turney's responses, and they're not winning the cygwin cause many friends. That's both insulting and untrue. Jon's doing a great job maintaining and supporting one of the most complex pieces of Cygwin, and as far as I remember, his responses are always helpful and accurate. Big ditto. And, I will once again offer my usual pragmatic observation that going personal in a response is not going to have any positive effect on your prospects of additional support from the object of your diatribe. We are giving you stuff for free, including mailing list support. If you don't like the type of support you receive then you *can* send email to a mailing list expressing your outrage but that is not likely to have any positive effect whatsoever beyond the temporary flush from expressing righteous indignation. And, additionally, the argument from a stranger who says 1) I know a lot. 2) I found this confusing but I have no intentions of offering constructive feedback. is likely going to cause a number of people to discount 1). cgf -- 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/
Re: Resizing problem
If you people simply want to flame me, fine. But everything I said is true: a) I had problems that no true Windows newbie could have solved from reading any amount of your documentation. b) this or that man page is NOT documentation. (Man pages will eventually be outlawed under the Geneva Convention as a form of torture.) c) after not finding answers, I spent three days searching for this and that clue, scavenger-hunt-style... d) ... where I encountered many of Jon T's answers, and, yes, they were all quite brusque and patronizing -- which put me off wanting to get on your mailing list. e) ...where I got some good help from a nice young man, but then patronized by a not-so-nice person who blew off all my legitimate complains and problems to patronize me -- as he has done many others. f) Microsoft's main dig against open source software still has a ring of truth to it, i.e., whenever you leave the customer-provider business relationship (where there's money on the table and even laws), you very well might encounter this sort of attitude and behavior. That being, of course, providers who don't care about customers, or don't even see end-users as customers, but as hoards of pests sucking up their valuable time with frivolous questions. So if cygwin is on the front lines of trying to win Windows users over to GNU/Linux, then we have a problem. I, for one, would expect cygwin to be inundated with clueless newbies who are a) not very computer saavy (e.g. what newbie would have done a rebase all?) b) nervous and in a hurry about deviating so far from Big Redmond Brother, i.e., not good with challenging documentation, likely to do stupid things. c) needing lots of hand-holding and not much scolding. I could go on (and on and on), but I hope you got my drift. Olwe Grand Marais, MN -- 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/
