From lukashaase@gmx.at Sun May 4 06:06:00 2014 From: lukashaase@gmx.at (Lukas Haase) Date: Sun, 04 May 2014 06:06:00 -0000 Subject: XWin ignores all parameters related to multiple monitors Message-ID: Hi, I use Cygwin/X to display a CAD application on my Windows cient. For some reason new windows always open on the secondary display and I always need to manually drag them to my primary display. That's sooo annoying (since UNIX applications tend to open new windows on every action). To avoid this, I want to disable the second monitor (and *only* use the primary). But whatever I do, XWin seems to ignore whatever I supply. For example, I start /usr/bin/startxwin.exe -- -nomultiplemonitors /usr/bin/startxwin.exe -- -screen 0 @1 -nomultiplemonitors /usr/bin/startxwin.exe -- -screen 0 @1 /usr/bin/startxwin.exe -- -mwextwm -screen 0 @1 -nomultiplemonitors and so on. Nothing works - everything as before. When I select "Hide Root Window" from the tray icon I see that the root window indeed covers both monitors. Any suggestions? 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/ From nem@emptec.com Mon May 5 18:39:00 2014 From: nem@emptec.com (Nem W Schlecht) Date: Mon, 05 May 2014 18:39:00 -0000 Subject: xterm crashing when trying to access Ctrl- menu items Message-ID: Hello all, For over a month now I've been having issues with my xterms in Cygwin. If I try to access *any* menu item under the Ctrl- menu items (change font, turn on/off scrollbar, redraw window, etc.), my xterm crashes the moment I un-press my mouse button. I don't access them all that often, so I don't know how long the issue has been around, but it's been a couple of months now. I've tried launching it with an empty .Xdefaults file (home dir) and by moving my .bashrc/.bash_profile files out of the way - still the same result. I've also gone out and downloaded the latest XTerm code and have a version compiled with debugging, but my C skills are really rusty and I'm not seeing anything terribly useful in gdb (I set my CYGWIN env var to "error_start=dumper -d %1 %2" so I would get core dumps). I compiled a version with a different "DEFCLASS" set so that I *know* it's not a bad resource or resource file. I'm running 64 bit on Windows 7. More details in the attached cygcheck.out. Anybody else on 64bit Cygwin / Win 7 having the same issues? -- Nem W Schlecht nem@emptec.com Empyreal Technologies http://www.emptec.com/ "Perl did the magic. I just waved the wand." -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 268615 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From jon.turney@dronecode.org.uk Mon May 5 20:03:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 05 May 2014 20:03:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: References: Message-ID: <5367EE90.4000205@dronecode.org.uk> On 04/05/2014 06:56, Lukas Haase wrote: > I use Cygwin/X to display a CAD application on my Windows cient. For > some reason new windows always open on the secondary display and I > always need to manually drag them to my primary display. That's sooo > annoying (since UNIX applications tend to open new windows on every action). I'm assuming that your secondary display is to the left of your primary display. I think that it's a bug that these windows are appearing at the top-left, rather than on the primary display, in that we don't distinguish well enough between "the application asked us to place the window at 0x0" and "the application didn't specify where to put the window" It would help if you could give the name of this application, and can you install 'xprop', and show the output you get from running that, then clicking on one of the window which gets placed incorrectly. > To avoid this, I want to disable the second monitor (and *only* use the > primary). But whatever I do, XWin seems to ignore whatever I supply. For > example, I start > > /usr/bin/startxwin.exe -- -nomultiplemonitors > /usr/bin/startxwin.exe -- -screen 0 @1 -nomultiplemonitors > /usr/bin/startxwin.exe -- -screen 0 @1 > /usr/bin/startxwin.exe -- -mwextwm -screen 0 @1 -nomultiplemonitors > > and so on. > Nothing works - everything as before. When I select "Hide Root Window" > from the tray icon I see that the root window indeed covers both monitors. This is not how it behaves for me. Using -nomultiplemontiors, or an explicit -screen setting shows an appropriately sized root window when turning off "Hide Root Window". (Although this is not terribly useful as you can move the Windows windows out of this area, which causes their contents to not be drawn) Can you check if the screen dimensions reported by xdpyinfo match those you are requesting, and attach your /var/log/xwin/XWin.0.log? Separately, it's possible that we should do something better with the combination of -nomultiplemontors and -multiwindow, but it's not quite clear to me what. (See discussion [1]) [1] https://sourceware.org/ml/cygwin-xfree/2011-07/msg00007.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/ From lukashaase@gmx.at Tue May 6 21:54:00 2014 From: lukashaase@gmx.at (Lukas Haase) Date: Tue, 06 May 2014 21:54:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: <5367EE90.4000205@dronecode.org.uk> References: <5367EE90.4000205@dronecode.org.uk> Message-ID: Hi Jon, Thanks for helping! On 2014-05-05 13:03, Jon TURNEY wrote: > On 04/05/2014 06:56, Lukas Haase wrote: >> I use Cygwin/X to display a CAD application on my Windows cient. For >> some reason new windows always open on the secondary display and I >> always need to manually drag them to my primary display. That's sooo >> annoying (since UNIX applications tend to open new windows on every >> action). > > I'm assuming that your secondary display is to the left of your primary > display. Yes. Secondary: builtin laptop display (on left) Primary: main monitor (on right) If I do "Identify", the laptop display is identified as "1" and the main monitor as "2". > I think that it's a bug that these windows are appearing at the > top-left, rather than on the primary display, in that we don't > distinguish well enough between "the application asked us to place the > window at 0x0" and "the application didn't specify where to put the window" > > It would help if you could give the name of this application, and can > you install 'xprop', and show the output you get from running that, then > clicking on one of the window which gets placed incorrectly. Sure. It's Cadence Virtuoso/ADE. The xprop output is: _WINDOWSWM_NATIVE_HWND(INTEGER) = 77728452 WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. bitmap id # to use for icon: 0x200178 bitmap id # of mask for icon: 0x200179 window id # of group leader: 0x200001 _NET_WM_ICON(CARDINAL) = Icon (50 x 50): [...] _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 2097527 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL _NET_WM_USER_TIME(CARDINAL) = 744838078 _NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x200176 WM_CLIENT_LEADER(WINDOW): window id # 0x200001 _NET_WM_PID(CARDINAL) = 24636 WM_LOCALE_NAME(STRING) = "C" WM_CLIENT_MACHINE(STRING) = "corn" WM_NORMAL_HINTS(WM_SIZE_HINTS): program specified location: 0, 0 program specified minimum size: 100 by 100 program specified maximum size: 3820 by 2500 window gravity: NorthWest WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_CLASS(STRING) = "Qt-subapplication", "Virtuoso" WM_ICON_NAME(STRING) = "Virtuoso?? Schematic Editor L Editing: project sch1 schematic on corn" _NET_WM_ICON_NAME(UTF8_STRING) = "Virtuoso?? Schematic Editor L Editing: project sch1 schematic on corn" WM_NAME(STRING) = "Virtuoso?? Schematic Editor L Editing: project sch1 schematic on corn" _NET_WM_NAME(UTF8_STRING) = "Virtuoso?? Schematic Editor L Editing: project sch1 schematic on corn" >> To avoid this, I want to disable the second monitor (and *only* use the >> primary). But whatever I do, XWin seems to ignore whatever I supply. For >> example, I start >> >> /usr/bin/startxwin.exe -- -nomultiplemonitors >> /usr/bin/startxwin.exe -- -screen 0 @1 -nomultiplemonitors >> /usr/bin/startxwin.exe -- -screen 0 @1 >> /usr/bin/startxwin.exe -- -mwextwm -screen 0 @1 -nomultiplemonitors >> >> and so on. >> Nothing works - everything as before. When I select "Hide Root Window" >> from the tray icon I see that the root window indeed covers both >> monitors. > > This is not how it behaves for me. Using -nomultiplemontiors, or an > explicit -screen setting shows an appropriately sized root window when > turning off "Hide Root Window". (Although this is not terribly useful as > you can move the Windows windows out of this area, which causes their > contents to not be drawn) You are right. Further research shows me that my arguments never showed up in XWin.0.log. Maybe I there's a different bug here? I call XWin like this: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -nomultimonitors And this appears in XWin.0.log: XWin was started with the following command line: X :0 -multiwindow However, if I directly start the XServer, XWin.exe -screen 0 @1 -multiwindow -nomultimonitors it works: XWin was started with the following command line: XWin -screen 0 @1 -multiwindow -nomultimonitors Why does startxwin.exe does not pass the parameters to the XServer. However, unfortunately this does not change anything: You are right that when I uncheck "Hide Root window", the black root window *only* covers the primary monitor. That's good. But windows are *still* opened at the second monitor! What's even worse (and pretty astonishing to me): All X windows are *only* displayed correctly on the *secondary* display with the command line above. On the primary display, the window frames are shown but the windows are not drawn (they are transparent) and they do not accept mouse/keyboard input. So it's completely the oppisite as it is intended ... > Can you check if the screen dimensions reported by xdpyinfo match those > you are requesting, and attach your /var/log/xwin/XWin.0.log? Hmm, I have here: [...] default screen number: 0 number of screens: 1 screen #0: dimensions: 1920x1080 pixels (508x286 millimeters) resolution: 96x96 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 root window id: 0x6b depth of root window: 24 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x20 default number of colormap cells: 256 preallocated pixels: black 0, white 16777215 options: backing-store WHEN MAPPED, save-unders NO largest cursor: 32x32 current input event mask: 0x4a0007 KeyPressMask KeyReleaseMask ButtonPressMask StructureNotifyMask SubstructureNotifyMask PropertyChangeMask number of visuals: 21 default visual id: 0x21 visual: visual id: 0x21 class: TrueColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff0000, 0xff00, 0xff significant bits in color specification: 8 bits [...] I think that's fine. XWin.0.log with the command line from above is attached. > Separately, it's possible that we should do something better with the > combination of -nomultiplemontors and -multiwindow, but it's not quite > clear to me what. (See discussion [1]) I would reaaaally appreciate that. Unfortunately I am not really an X expert. What bothers me a little bit is that windows are displayed on a screen which should not even exist. (besides the problem reported above that the windows are not even drawn on the intended screen). Thanks Luke -------------- next part -------------- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.2-WOW64 thinktank 1.7.29(0.272/5/3) 2014-04-07 13:44 i686 OS: Windows 8 [Windows NT 6.2 build 9200] (WoW64) Package: version 1.15.1-1 built 2014-04-16 XWin was started with the following command line: XWin -screen 0 @1 -multiwindow -nomultimonitors ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeScreenDefaults - native DPI x 96 y 96 winInitializeScreens - 1 winInitializeScreen - 0 ddxProcessArgument - screen - Found Valid ``@Monitor'' = 1 arg _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 _XSERVTransmkdir: this may cause subsequent errors [745929.703] Initializing built-in extension Generic Event Extension [745929.703] Initializing built-in extension SHAPE [745929.703] Initializing built-in extension MIT-SHM [745929.703] Initializing built-in extension XInputExtension [745929.703] Initializing built-in extension XTEST [745929.703] Initializing built-in extension BIG-REQUESTS [745929.703] Initializing built-in extension SYNC [745929.703] Initializing built-in extension XKEYBOARD [745929.703] Initializing built-in extension XC-MISC [745929.703] Initializing built-in extension XINERAMA [745929.703] Initializing built-in extension XFIXES [745929.703] Initializing built-in extension XFree86-Bigfont [745929.703] Initializing built-in extension RENDER [745929.703] Initializing built-in extension RANDR [745929.703] Initializing built-in extension COMPOSITE [745929.703] Initializing built-in extension DAMAGE [745929.703] Initializing built-in extension MIT-SCREEN-SAVER [745929.703] Initializing built-in extension DOUBLE-BUFFER [745929.703] Initializing built-in extension RECORD [745929.703] Initializing built-in extension DPMS [745929.703] Initializing built-in extension Present [745929.703] Initializing built-in extension X-Resource [745929.703] Initializing built-in extension GLX [745929.703] (II) xorg.conf is not supported [745929.703] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [745929.703] LoadPreferences: /home/niki/.XWinrc not found [745929.703] LoadPreferences: Loading /etc/X11/system.XWinrc [745929.703] LoadPreferences: Done parsing the configuration file... [745929.718] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [745929.718] winDetectSupportedEngines - Returning, supported engines 00000015 [745929.718] winSetEngine - Multi Window or Rootless => ShadowGDI [745929.718] winScreenInit - Using Windows display depth of 32 bits per pixel [745929.812] winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32 [745929.812] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [745929.812] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [745929.812] winInitMultiWindowWM - Calling pthread_mutex_lock () [745929.812] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [745929.812] MIT-SHM extension disabled due to lack of kernel support [745929.812] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [745929.828] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' [745929.968] GL_VERSION: 4.0.0 - Build 9.17.10.2875 [745929.968] GL_VENDOR: Intel [745929.968] GL_RENDERER: Intel(R) HD Graphics 4000 [745929.968] (II) AIGLX: enabled GLX_SGI_make_current_read [745929.968] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [745929.968] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [745929.968] (II) AIGLX: enabled GLX_SGIX_pbuffer [745929.968] (II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample [745929.968] (II) 66 pixel formats reported by wglGetPixelFormatAttribivARB [745929.968] (II) AIGLX: Set GLX version to 1.4 [745929.984] (II) 21 fbConfigs [745929.984] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [745930.109] winPointerWarpCursor - Discarding first warp: 960 540 [745930.109] (--) 5 mouse buttons found [745930.109] (--) Setting autorepeat to delay=500, rate=31 [745930.109] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [745930.109] (--) Found matching XKB configuration "English (USA)" [745930.109] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [745930.109] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [745930.109] winBlockHandler - pthread_mutex_unlock() [745930.109] winInitMultiWindowWM - pthread_mutex_lock () returned. [745930.109] winInitMultiWindowWM - pthread_mutex_unlock () returned. [745930.109] winInitMultiWindowWM - DISPLAY=:0.0 [745930.109] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [745930.109] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [745930.109] winMultiWindowXMsgProc - DISPLAY=:0.0 [745930.109] winProcEstablishConnection - winInitClipboard returned. [745930.109] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [745930.109] winClipboardThreadProc - DISPLAY=:0.0 [745930.109] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [745930.109] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [745938.484] OS has icon alpha channel support: yes [745948.156] executing 'xterm', pid 7992 [745948.250] (pid 7992 stderr) Warning: Missing charsets in String to FontSet conversion [745980.343] executing 'xterm', pid 13548 [745980.453] (pid 13548 stderr) Warning: Missing charsets in String to FontSet conversion -------------- next part -------------- -- 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/ From jon.turney@dronecode.org.uk Wed May 7 12:59:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 07 May 2014 12:59:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.15.1-2 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.15.1-2 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.15.1-1: * Fix X server sometimes getting stuck during exit if it owns the Windows clipboard * Fix sometimes missing system menu icons in multiwindow mode on Vista and later * Avoid a "Your OS is unknown" warning when configuring Xorg for cygwin x86: a4a3a9cbf96f57caea3aa75817c315fd *xorg-server-1.15.1-2-src.tar.xz f2005846a8c6532f525e47bd2c7835b6 *xorg-server-1.15.1-2.tar.xz 3e528d91583a661723b278c14f653f1d *xorg-server-common-1.15.1-2.tar.xz 66a59d1dbc264082ad358cbdb92b858f *xorg-server-debuginfo-1.15.1-2.tar.xz a2b7312bb6fd367f1f7c8d87cec35c1a *xorg-server-devel-1.15.1-2.tar.xz ddcb841a1d0957b2752791bdf7c4f76f *xorg-server-dmx-1.15.1-2.tar.xz 3cb714b19889766592f5a66cdcf2dbee *xorg-server-extra-1.15.1-2.tar.xz b5c65120980a02352801c5d9ae74e13b *xwinclip-1.15.1-2.tar.xz x86_64: db259c96e6c865a3d2ffebfce8a61014 *xorg-server-1.15.1-2-src.tar.xz ab3522058a8ef4f8381c87070f468718 *xorg-server-1.15.1-2.tar.xz 2a0be52c750164ce76c534e5760f4042 *xorg-server-common-1.15.1-2.tar.xz 2dfed21f9a7207908a69fd48df228a1e *xorg-server-debuginfo-1.15.1-2.tar.xz f91d28ef5fe063f1198eae5a4769f56c *xorg-server-devel-1.15.1-2.tar.xz cb7686a79e2638a8740a4348cc4863c6 *xorg-server-dmx-1.15.1-2.tar.xz df0247c00f3d419181ee378db9e0ee50 *xorg-server-extra-1.15.1-2.tar.xz 6c3b481887427ad640fcb7614d43b85a *xwinclip-1.15.1-2.tar.xz -- 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/ From jon.turney@dronecode.org.uk Thu May 8 12:15:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 08 May 2014 12:15:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: References: <5367EE90.4000205@dronecode.org.uk> Message-ID: <536B755C.2040602@dronecode.org.uk> On 06/05/2014 22:54, Lukas Haase wrote: > On 2014-05-05 13:03, Jon TURNEY wrote: >> On 04/05/2014 06:56, Lukas Haase wrote: >>> I use Cygwin/X to display a CAD application on my Windows cient. For >>> some reason new windows always open on the secondary display and I >>> always need to manually drag them to my primary display. That's sooo >>> annoying (since UNIX applications tend to open new windows on every >>> action). > >> I think that it's a bug that these windows are appearing at the >> top-left, rather than on the primary display, in that we don't >> distinguish well enough between "the application asked us to place the >> window at 0x0" and "the application didn't specify where to put the window" >> >> It would help if you could give the name of this application, and can >> you install 'xprop', and show the output you get from running that, then >> clicking on one of the window which gets placed incorrectly. > > Sure. > > It's Cadence Virtuoso/ADE. > > The xprop output is: [...] > WM_NORMAL_HINTS(WM_SIZE_HINTS): > program specified location: 0, 0 > program specified minimum size: 100 by 100 > program specified maximum size: 3820 by 2500 Hmmm... There are 2 possible flags here: "program specified location" and "user specified location" (e.g. by using -geometry on the command line), and at the moment we honour them both. Now, it might be that the client expects to see some EWMH capabilities advertised by the multiwindow mode WM, the absence of which causes it to set this, or it only sets this after the window is placed, but if it always creates the window with that property, it's not clear how to fix this. (Just ignoring "program specified location" is tempting, but there are legitimate uses, for example a toolbar window which should be placed at the side) So, do you have an example of this working as you would like on a unix system, and what is the window manager is that case? I've built a snapshot [1], which adds a heuristic which ignores a 'program specified location' hint if the location is the origin, which you might like to try and see if that fixes your problem, but I'm not sure if that is the correct solution. (I also found a bug with how this hint is handled in 64-bit builds, but I don't think that affects you) [1] ftp://cygwin.com/pub/cygwinx/x86/XWin.20140508-git-c4a16a6606868d3e.exe.bz2 >> This is not how it behaves for me. Using -nomultiplemontiors, or an >> explicit -screen setting shows an appropriately sized root window when >> turning off "Hide Root Window". (Although this is not terribly useful as >> you can move the Windows windows out of this area, which causes their >> contents to not be drawn) > > You are right. Further research shows me that my arguments never showed > up in XWin.0.log. Maybe I there's a different bug here? > > I call XWin like this: > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- > -nomultimonitors > > And this appears in XWin.0.log: > > XWin was started with the following command line: > > X :0 -multiwindow You need to quote the whole command after bash's -c flag, otherwise they are interpreted as additional flags to bash. See http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-command-line-args for an example. > However, unfortunately this does not change anything: You are right that > when I uncheck "Hide Root window", the black root window *only* covers > the primary monitor. That's good. > > But windows are *still* opened at the second monitor! > > What's even worse (and pretty astonishing to me): All X windows are > *only* displayed correctly on the *secondary* display with the command > line above. On the primary display, the window frames are shown but the > windows are not drawn (they are transparent) and they do not accept > mouse/keyboard input. > > So it's completely the opposite as it is intended ... Yes, it seems there is also something wrong with the translation between Windows (which has 0,0 at the top-left of the primary monitor) and X (which has 0,0 at the top-left of the virtual screen) coordinate spaces here. But even if that was fixed, there is still the problem of how X windows are supposed to behave when moved off the virtual screen (not allowed to move? empty?) Because of that, assuming that I can fix your problem with correct window placement, I am inclined to just disable the combination of -multiwindow and -screen. -- 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/ From lukashaase@gmx.at Thu May 8 23:28:00 2014 From: lukashaase@gmx.at (Lukas Haase) Date: Thu, 08 May 2014 23:28:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: <536B755C.2040602@dronecode.org.uk> References: <5367EE90.4000205@dronecode.org.uk> <536B755C.2040602@dronecode.org.uk> Message-ID: Hi Jon, First of all, thank you so much for your effort! I am struggling for so long with the issue and I am so happy to see your encouragement here. On 2014-05-08 5:15, Jon TURNEY wrote: > On 06/05/2014 22:54, Lukas Haase wrote: >> On 2014-05-05 13:03, Jon TURNEY wrote: >>> [...] >>> It would help if you could give the name of this application, and can >>> you install 'xprop', and show the output you get from running that, then >>> clicking on one of the window which gets placed incorrectly. >> >> Sure. >> >> It's Cadence Virtuoso/ADE. >> >> The xprop output is: > [...] >> WM_NORMAL_HINTS(WM_SIZE_HINTS): >> program specified location: 0, 0 >> program specified minimum size: 100 by 100 >> program specified maximum size: 3820 by 2500 > > Hmmm... > > There are 2 possible flags here: "program specified location" and "user > specified location" (e.g. by using -geometry on the command line), and > at the moment we honour them both. > > Now, it might be that the client expects to see some EWMH capabilities > advertised by the multiwindow mode WM, the absence of which causes it to > set this, or it only sets this after the window is placed, but if it > always creates the window with that property, it's not clear how to fix > this. Thank you! I think I understand it (I am no X expert). > (Just ignoring "program specified location" is tempting, but there are > legitimate uses, for example a toolbar window which should be placed at > the side) Sounds legitimate. Aside: Maybe it's possible to make this configurable via config or environment variable? (but I guess the X server does not see environment variables etc.) > So, do you have an example of this working as you would like on a unix > system, and what is the window manager is that case? I am not sure if I get the question. What I could do is to login via VNC and see how the windows are placed are if they are placed the correct way? Is this what you mean? Unfortunately I have no chance to install Cadence locally and run it from a local, dual monitor setup from Linux because Cadence is a proprietary, expensive tool. > I've built a snapshot [1], which adds a heuristic which ignores a > 'program specified location' hint if the location is the origin, which > you might like to try and see if that fixes your problem, but I'm not > sure if that is the correct solution. > > (I also found a bug with how this hint is handled in 64-bit builds, but > I don't think that affects you) > > [1] > ftp://cygwin.com/pub/cygwinx/x86/XWin.20140508-git-c4a16a6606868d3e.exe.bz2 Thanks so much for that! I have just the issue that the exe does not seem to work for me. Is there anything special I need to consider? I tried copying both, 63 and 32 bit versions to c:\cygwin\bin: 32 bit version gives: c:\cygwin\bin>XWin.new.32 XWin.new.32:./.libs/lt-XWin.c:233: FATAL: couldn't find XWin.new.32. And 64 bit gives: "The application was unable to start correctly (0xc000007b). Click OK to close the application". What bothers me is that my original XWin.exe has 2363943 Bytes (and the X icon) whereas your new versions are just 26624 and 27150 Byes (and no icon). c:\cygwin\bin>uname -a CYGWIN_NT-6.2-WOW64 think 1.7.29(0.272/5/3) 2014-04-07 13:44 i686 Cygwin >> [...] >> I call XWin like this: >> >> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- >> -nomultimonitors >> >> And this appears in XWin.0.log: >> >> XWin was started with the following command line: >> >> X :0 -multiwindow > > You need to quote the whole command after bash's -c flag, otherwise they > are interpreted as additional flags to bash. > > See http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-command-line-args > for an example. Thanks but I think I have tried that already. It may be hard to believe but: c:\cygwin\var\log\xwin>del XWin.0.log c:\cygwin\var\log\xwin>C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe -- -nomultimonitors -foobar" c:\cygwin\var\log\xwin>c:\cygwin\bin\head -n 10 XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.2-WOW64 think 1.7.29(0.272/5/3) 2014-04-07 13:44 i686 OS: Windows 8 [Windows NT 6.2 build 9200] (WoW64) Package: version 1.15.1-1 built 2014-04-16 XWin was started with the following command line: X :0 -multiwindow c:\cygwin\var\log\xwin> I made sure that XWin was not running before and waited after the call until I saw the tray icon. >> [...] >> What's even worse (and pretty astonishing to me): All X windows are >> *only* displayed correctly on the *secondary* display with the command >> line above. On the primary display, the window frames are shown but the >> windows are not drawn (they are transparent) and they do not accept >> mouse/keyboard input. >> >> So it's completely the opposite as it is intended ... > > Yes, it seems there is also something wrong with the translation between > Windows (which has 0,0 at the top-left of the primary monitor) and X > (which has 0,0 at the top-left of the virtual screen) coordinate spaces > here. I mean something different here: Even when I just start the local xterm.exe the problem appears. And it's reproduceable: XWin was started with the following command line: XWin -screen 0 @1 -multiwindow -nomultimonitors When, if I start xterm.exe, it is not rendered on the *primary* monitor at all (only the window frame is and whichever content was previously displayed in the window). Only if I drag the xterm window to the secondary display (which is not even supposed to exist now), the content is updated/rendered. > But even if that was fixed, there is still the problem of how X windows > are supposed to behave when moved off the virtual screen (not allowed to > move? empty?) I am not sure if I understand the question but in my humble understanding this can't just happen: it would behave the same as if you moved the window out of the monitor. The part moved out is just not displayed. > Because of that, assuming that I can fix your problem with correct > window placement, I am inclined to just disable the combination of > -multiwindow and -screen. I understand. I have no idea about the implications and the implementation details; in my humble understanding it would just work as described above ;-) But that's probably too simplified ... 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/ From jon.turney@dronecode.org.uk Fri May 9 10:15:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 09 May 2014 10:15:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: References: <5367EE90.4000205@dronecode.org.uk> <536B755C.2040602@dronecode.org.uk> Message-ID: <536CAABE.4020308@dronecode.org.uk> On 09/05/2014 00:27, Lukas Haase wrote: > On 2014-05-08 5:15, Jon TURNEY wrote: > >> So, do you have an example of this working as you would like on a unix >> system, and what is the window manager is that case? > > I am not sure if I get the question. > > What I could do is to login via VNC and see how the windows are placed > are if they are placed the correct way? > > Is this what you mean? > > Unfortunately I have no chance to install Cadence locally and run it > from a local, dual monitor setup from Linux because Cadence is a > proprietary, expensive tool. I understand that. I am just looking for some evidence that it isn't a bug in the application, i.e. that it works correctly for *anyone* :D Knowing a window manager which places these windows correctly would also give me some source code to look at to work out what I need to change. >> I've built a snapshot [1], which adds a heuristic which ignores a >> 'program specified location' hint if the location is the origin, which >> you might like to try and see if that fixes your problem, but I'm not >> sure if that is the correct solution. > > I have just the issue that the exe does not seem to work for me. Is > there anything special I need to consider? Sorry, my snapshot building script went wrong and the snapshot was broken. Try this one instead. ftp://cygwin.com/pub/cygwinx/x86/XWin.20140509-git-c4a16a6606868d3e.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/ From yselkowitz@users.sourceforge.net Fri May 9 15:14:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Fri, 09 May 2014 15:14:00 -0000 Subject: [ANNOUNCEMENT] Updated: qt4-4.8.6-1 Message-ID: The following packages have been updated for the Cygwin distribution: *** qt4-*-4.8.6-1 *** libQt*4-4.8.6-1 *** libQt*4-devel-4.8.6-1 Qt is a cross-platform application framework for desktop and embedded development. Qt enables programmers to create advanced GUI applications once and deploy them to Windows, Mac OS X and Linux without rewriting the source code. This release is an update to the latest bugfix release, and also includes a patch for CVE-2014-0190. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From yselkowitz@users.sourceforge.net Fri May 9 15:15:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Fri, 09 May 2014 15:15:00 -0000 Subject: [ANNOUNCEMENT] Updated: fontconfig-2.11.1-1 Message-ID: The following packages have been updated for the Cygwin distribution: *** fontconfig-2.11.1-1 *** libfontconfig1-2.11.1-1 *** libfontconfig-devel-2.11.1-1 Fontconfig is a library designed to provide system-wide font configuration, customization and application access. This is an update to the latest upstream release. The Windows font directory has been removed from the default fonts path due to issues caused by stale caches; a separate package to add it to the path, as well as keep the cache current automatically, should be available soon. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From pjs@hackthetruth.org Fri May 9 15:22:00 2014 From: pjs@hackthetruth.org (Philip Schneider) Date: Fri, 09 May 2014 15:22:00 -0000 Subject: configure errors for xclock Message-ID: Greetings - Very long-time X user/programmer, complete n00b using it in cygwin? I have what should be an up-to-date cygwin install on a Windows 7 box. Used the setup application to retrieve the source code for xclock (tried both the 6 and 7 versions). Trying to run ?configure?, I get errors: No package ?xaw7? found No package ?xmu? found I don?t see an entry for either of these in the setup application? What am I doing wrong? Am I missing some somewhat-less-obvious thing to install? I using ?configure; make? not the right way to do things? Thanks! ? Philip -- 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/ From n8tm@aol.com Fri May 9 15:47:00 2014 From: n8tm@aol.com (Tim Prince) Date: Fri, 09 May 2014 15:47:00 -0000 Subject: configure errors for xclock In-Reply-To: References: Message-ID: <536CF87C.60607@aol.com> On 5/9/2014 11:22 AM, Philip Schneider wrote: > Greetings - > > Very long-time X user/programmer, complete n00b using it in cygwin?? > > I have what should be an up-to-date cygwin install on a Windows 7 box. Used the setup application to retrieve the source code for xclock (tried both the 6 and 7 versions). Trying to run ??configure??, I get errors: > > No package ??xaw7?? found > No package ??xmu?? found > > http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html installing xinit should have installed xclock and all its dependencies. -- Tim Prince -- 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/ From robert.c.withers.ctr@mail.mil Fri May 9 15:55:00 2014 From: robert.c.withers.ctr@mail.mil (Withers, Robert C CTR USARMY USAASC (US)) Date: Fri, 09 May 2014 15:55:00 -0000 Subject: startxwin.exe no longer processes -- :1 Message-ID: <79436EC50B4CD448A10CFE6AAD833F693E74E152@umechpao5.easf.csd.disa.mil> I have tried -- :1, -d 1 and -display 1, none of which work. What am I doing wrong? Chris Withers Contractor, APEX Systems/IBM PDS Altess UNIX OPS Work: 540-731-3570 Cell: 501-514-0914 Office email: robert.c.withers.ctr@mail.mil Personal email: old_kyle_w@yahoo.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xwin_log.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xygcheck_out.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5682 bytes Desc: not available URL: From marco.atzeri@gmail.com Fri May 9 16:52:00 2014 From: marco.atzeri@gmail.com (Marco Atzeri) Date: Fri, 09 May 2014 16:52:00 -0000 Subject: configure errors for xclock In-Reply-To: References: Message-ID: <536D07D7.5030206@gmail.com> On 09/05/2014 17:22, Philip Schneider wrote: > Greetings - > > Very long-time X user/programmer, complete n00b using it in cygwin?? > > I have what should be an up-to-date cygwin install on a Windows 7 box. Used the setup application to retrieve the source code for xclock (tried both the 6 and 7 versions). Trying to run ??configure??, I get errors: > > No package ??xaw7?? found > No package ??xmu?? found > > I don??t see an entry for either of these in the setup application?? > > What am I doing wrong? Am I missing some somewhat-less-obvious thing to install? I using ??configure; make?? not the right way to do things? > > Thanks! > > ?? Philip > -- you need to install the packages that includes the needed header libXaw-devel libXmu-devel for info http://www.cygwin.com/packages/ http://cygwin.com/cgi-bin2/package-grep.cgi?grep=xaw7&arch=x86 http://cygwin.com/cgi-bin2/package-grep.cgi?grep=xmu&arch=x86 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/ From lukashaase@gmx.at Fri May 9 20:26:00 2014 From: lukashaase@gmx.at (Lukas Haase) Date: Fri, 09 May 2014 20:26:00 -0000 Subject: XWin ignores all parameters related to multiple monitors In-Reply-To: <536CAABE.4020308@dronecode.org.uk> References: <5367EE90.4000205@dronecode.org.uk> <536B755C.2040602@dronecode.org.uk> <536CAABE.4020308@dronecode.org.uk> Message-ID: On 2014-05-09 3:15, Jon TURNEY wrote: > On 09/05/2014 00:27, Lukas Haase wrote: >> On 2014-05-08 5:15, Jon TURNEY wrote: >> >>> So, do you have an example of this working as you would like on a unix >>> system, and what is the window manager is that case? >> >> I am not sure if I get the question. >> >> What I could do is to login via VNC and see how the windows are placed >> are if they are placed the correct way? >> >> Is this what you mean? >> >> Unfortunately I have no chance to install Cadence locally and run it >> from a local, dual monitor setup from Linux because Cadence is a >> proprietary, expensive tool. > > I understand that. > > I am just looking for some evidence that it isn't a bug in the > application, i.e. that it works correctly for *anyone* :D > > Knowing a window manager which places these windows correctly would also > give me some source code to look at to work out what I need to change. Hmm, what I just did is that I started a VNC session and used VNC. Everything seems to work as expected, new windows are /not/ placed at (0,0). Window manager is Gnome. However, as mentioned, this is clearly not a local multi-monitor X session :( >>> I've built a snapshot [1], which adds a heuristic which ignores a >>> 'program specified location' hint if the location is the origin, which >>> you might like to try and see if that fixes your problem, but I'm not >>> sure if that is the correct solution. >> >> I have just the issue that the exe does not seem to work for me. Is >> there anything special I need to consider? > > Sorry, my snapshot building script went wrong and the snapshot was > broken. Try this one instead. > > ftp://cygwin.com/pub/cygwinx/x86/XWin.20140509-git-c4a16a6606868d3e.exe.bz2 Can't believe it, great! Works exactly as it should (just with the standard configuration, "X :0 -multiwindow")!! Now I just hope that this 'patch' somehow finds its way into the trunk ;-) 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/ From jon.turney@dronecode.org.uk Mon May 12 10:34:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 12 May 2014 10:34:00 -0000 Subject: xterm crashing when trying to access Ctrl- menu items In-Reply-To: References: Message-ID: <5370A3BB.8080300@dronecode.org.uk> On 05/05/2014 19:39, Nem W Schlecht wrote: > For over a month now I've been having issues with my xterms in Cygwin. > If I try to access *any* menu item under the Ctrl- menu > items (change font, turn on/off scrollbar, redraw window, etc.), my > xterm crashes the moment I un-press my mouse button. I don't access > them all that often, so I don't know how long the issue has been > around, but it's been a couple of months now. > > I've tried launching it with an empty .Xdefaults file (home dir) and > by moving my .bashrc/.bash_profile files out of the way - still the > same result. I've also gone out and downloaded the latest XTerm code > and have a version compiled with debugging, but my C skills are really > rusty and I'm not seeing anything terribly useful in gdb (I set my > CYGWIN env var to "error_start=dumper -d %1 %2" so I would get core > dumps). I compiled a version with a different "DEFCLASS" set so that > I *know* it's not a bad resource or resource file. > > I'm running 64 bit on Windows 7. More details in the attached cygcheck.out. > > Anybody else on 64bit Cygwin / Win 7 having the same issues? Thanks for reporting this issue. I can reproduce it. This appears to be an issue with Xt, as a Cygwin-specific patch does not work correctly on x86_64 when another DLL which is using Xt is loaded >2GB away from it. Until we have a fix, you *might* be able to work around this by rebasing the DLLs, e.g. in the specific case of xterm, which uses Xaw: cd /usr/bin rebase -v -b 0x400000000 cygXt-6.dll rebase -v -b 0x410000000 cygXaw-7.dll -- 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/ From jon.turney@dronecode.org.uk Mon May 12 10:45:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 12 May 2014 10:45:00 -0000 Subject: startxwin.exe no longer processes -- :1 In-Reply-To: <79436EC50B4CD448A10CFE6AAD833F693E74E152@umechpao5.easf.csd.disa.mil> References: <79436EC50B4CD448A10CFE6AAD833F693E74E152@umechpao5.easf.csd.disa.mil> Message-ID: <5370A649.7060800@dronecode.org.uk> On 09/05/2014 16:55, Withers, Robert C CTR USARMY USAASC (US) wrote: > I have tried -- :1, -d 1 and -display 1, none of which work. What am I doing > wrong? This works fine for me. > $startxwin -- :1 > > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.15.1.0 > OS: CYGWIN_NT-6.3 tambora 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 > OS: Windows 8.1 [Windows NT 6.3 build 9600](Win64) > Package: version 1.15.1-2 built 2014-05-06 > > XWin was started with the following command line: > > X :1 -multiwindow > [...] > [143571.031] winInitMultiWindowWM - DISPLAY=:1.0 > [143571.031] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. > [143571.046] winProcEstablishConnection - winInitClipboard returned. > [143571.046] winClipboardThreadProc - DISPLAY=:1.0 > [143571.046] winMultiWindowXMsgProc - DISPLAY=:1.0 You seem to have cut off the start of your log, so I can't actually see what command line the X server is being started with. -- 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/ From nem@emptec.com Mon May 12 14:37:00 2014 From: nem@emptec.com (Nem W Schlecht) Date: Mon, 12 May 2014 14:37:00 -0000 Subject: xterm crashing when trying to access Ctrl- menu items In-Reply-To: <5370A3BB.8080300@dronecode.org.uk> References: <5370A3BB.8080300@dronecode.org.uk> Message-ID: Thanks for the reply, Jon! I'm happy you were able to reproduce the issue - I assumed I had screwed something up in my environment. :) Your attempted fix with rebase worked perfectly - all of my menus are now working correctly. If you'd like me to do any additional testing in the future, don't hesitate to ask. On Mon, May 12, 2014 at 5:34 AM, Jon TURNEY wrote: > On 05/05/2014 19:39, Nem W Schlecht wrote: >> >> For over a month now I've been having issues with my xterms in Cygwin. >> If I try to access *any* menu item under the Ctrl- menu >> items (change font, turn on/off scrollbar, redraw window, etc.), my >> xterm crashes the moment I un-press my mouse button. I don't access >> them all that often, so I don't know how long the issue has been >> around, but it's been a couple of months now. >> >> I've tried launching it with an empty .Xdefaults file (home dir) and >> by moving my .bashrc/.bash_profile files out of the way - still the >> same result. I've also gone out and downloaded the latest XTerm code >> and have a version compiled with debugging, but my C skills are really >> rusty and I'm not seeing anything terribly useful in gdb (I set my >> CYGWIN env var to "error_start=dumper -d %1 %2" so I would get core >> dumps). I compiled a version with a different "DEFCLASS" set so that >> I *know* it's not a bad resource or resource file. >> >> I'm running 64 bit on Windows 7. More details in the attached >> cygcheck.out. >> >> Anybody else on 64bit Cygwin / Win 7 having the same issues? > > > Thanks for reporting this issue. I can reproduce it. > > This appears to be an issue with Xt, as a Cygwin-specific patch does not > work correctly on x86_64 when another DLL which is using Xt is loaded >2GB > away from it. > > Until we have a fix, you *might* be able to work around this by rebasing the > DLLs, e.g. in the specific case of xterm, which uses Xaw: > > cd /usr/bin > rebase -v -b 0x400000000 cygXt-6.dll > rebase -v -b 0x410000000 cygXaw-7.dll > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer -- Nem W Schlecht nem@emptec.com Empyreal Technologies http://www.emptec.com/ "Perl did the magic. I just waved the wand." -- 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/ From kbrown@cornell.edu Tue May 13 01:45:00 2014 From: kbrown@cornell.edu (Ken Brown) Date: Tue, 13 May 2014 01:45:00 -0000 Subject: [ANNOUNCEMENT] Updated: fontconfig-2.11.1-1 In-Reply-To: References: Message-ID: <53717920.7050401@cornell.edu> On 5/9/2014 11:07 AM, Yaakov (Cygwin/X) wrote: > The following packages have been updated for the Cygwin distribution: > > *** fontconfig-2.11.1-1 > *** libfontconfig1-2.11.1-1 > *** libfontconfig-devel-2.11.1-1 > > Fontconfig is a library designed to provide system-wide font > configuration, customization and application access. > > This is an update to the latest upstream release. The Windows font > directory has been removed from the default fonts path due to issues > caused by stale caches; a separate package to add it to the path, as > well as keep the cache current automatically, should be available soon. You also removed /usr/share/ghostscript/fonts, /usr/share/texmf-dist/fonts/opentype, /usr/share/texmf-dist/fonts/truetype, and /usr/share/texmf-dist/fonts/type1. Was that intentional? 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/ From yselkowitz@users.sourceforge.net Tue May 13 20:38:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 13 May 2014 20:38:00 -0000 Subject: [ANNOUNCEMENT] Updated: fontconfig-2.11.1-1 In-Reply-To: <53717920.7050401@cornell.edu> References: <53717920.7050401@cornell.edu> Message-ID: <537282B0.3090603@users.sourceforge.net> On 2014-05-12 20:45, Ken Brown wrote: > On 5/9/2014 11:07 AM, Yaakov (Cygwin/X) wrote: >> This is an update to the latest upstream release. The Windows font >> directory has been removed from the default fonts path due to issues >> caused by stale caches; a separate package to add it to the path, as >> well as keep the cache current automatically, should be available soon. > > You also removed /usr/share/ghostscript/fonts, > /usr/share/texmf-dist/fonts/opentype, > /usr/share/texmf-dist/fonts/truetype, and > /usr/share/texmf-dist/fonts/type1. Was that intentional? Yes, because it seems that they would also have this issue because nothing in the providing packages updates the cache. (cygport only generates fontconfig postinstall scripts for /usr/share/fonts.) Yaakov -- 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/ From kbrown@cornell.edu Tue May 13 21:14:00 2014 From: kbrown@cornell.edu (Ken Brown) Date: Tue, 13 May 2014 21:14:00 -0000 Subject: [ANNOUNCEMENT] Updated: fontconfig-2.11.1-1 In-Reply-To: <537282B0.3090603@users.sourceforge.net> References: <53717920.7050401@cornell.edu> <537282B0.3090603@users.sourceforge.net> Message-ID: <53728B3C.3000405@cornell.edu> On 5/13/2014 4:38 PM, Yaakov (Cygwin/X) wrote: > On 2014-05-12 20:45, Ken Brown wrote: >> On 5/9/2014 11:07 AM, Yaakov (Cygwin/X) wrote: >>> This is an update to the latest upstream release. The Windows font >>> directory has been removed from the default fonts path due to issues >>> caused by stale caches; a separate package to add it to the path, as >>> well as keep the cache current automatically, should be available soon. >> >> You also removed /usr/share/ghostscript/fonts, >> /usr/share/texmf-dist/fonts/opentype, >> /usr/share/texmf-dist/fonts/truetype, and >> /usr/share/texmf-dist/fonts/type1. Was that intentional? > > Yes, because it seems that they would also have this issue because > nothing in the providing packages updates the cache. (cygport only > generates fontconfig postinstall scripts for /usr/share/fonts.) I don't know about the ghostscript fonts, but cygport does generate the appropriate fc-cache commands in the postinstall scripts for the texlive-collection-* packages that install fonts. This is done in __prep_texlive() in src_postinst.cygpart. 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/ From apchar@yahoo.com Fri May 16 16:35:00 2014 From: apchar@yahoo.com (apchar) Date: Fri, 16 May 2014 16:35:00 -0000 Subject: where are xfig libraries specified? Message-ID: [moved from gmane.os.cygwin] I want to add some components to the default xfig libraries. I want to put them where they'd ultimately go (/usr/lib/xfig/Libraries/newstuffdir). But I cant find the resource or file that determines the path to the libraries available to xfig. It's not specified in /etc/X11/app-defaults/Fig where I'd expect it to be. $XFIGLIBDIR is not set. It's not in /etc/X11/xinit/xinitrc. I can't add anything to the library without access to that resource (or file). I know I can use the -library_dir switch but I want my stuff to show up in the default menus. So where is the resource/file I edit to add my library? -- 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/ From yselkowitz@users.sourceforge.net Fri May 16 22:08:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Fri, 16 May 2014 22:08:00 -0000 Subject: [ANNOUNCEMENT] Updated: libXfont-1.4.8-1 [SECURITY] Message-ID: The following packages have been added or updated in the Cygwin distribution: * libXfont1-1.4.8-1 * libXfont-devel-1.4.8-1 libXfont provides the core of the legacy X11 font system, handling the index files (fonts.dir, fonts.alias, fonts.scale), the various font file formats, and rasterizing them. It is used by the X servers, the X Font Server (xfs), and some font utilities (namely bdftopcf), but should not be used by normal X11 clients. X11 clients access fonts via either the new APIs in libXft, or the legacy APIs in libX11. This update fixes CVE-2014-0209, CVE-2014-0210, and CVE-2014-0211 as described here: http://lists.x.org/archives/xorg-announce/2014-May/002431.html -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From jon.turney@dronecode.org.uk Tue May 20 11:32:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 20 May 2014 11:32:00 -0000 Subject: where are xfig libraries specified? In-Reply-To: References: Message-ID: <537B3D34.5050607@dronecode.org.uk> On 16/05/2014 17:19, apchar wrote: > [moved from gmane.os.cygwin] I don't really know anything about xfig, so perhaps you can clarify a few things for me? > I want to add some components to the default xfig libraries. I want to put > them where they'd ultimately go (/usr/lib/xfig/Libraries/newstuffdir) Are you asking if that path is correct (it seems to be)? Or are you asking how to discover that path programmatically? > $XFIGLIBDIR is not set. I think the idea of XFIGLIBDIR is for you to set it to override the default. -- 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/ From gulliver.m.smith@gmail.com Thu May 22 13:19:00 2014 From: gulliver.m.smith@gmail.com (Gulliver Smith) Date: Thu, 22 May 2014 13:19:00 -0000 Subject: Window manager commands in native window manager multiwindow mode Message-ID: I ask this question from time to time just in case someone new sees it and decides to work on it or others might agree that it is a priority. Other people have raised this over the last few years as well. The issue is that I would like to raise windows from within a program (Emacs to be precise), but it doesn't work with the native window manager running in multiwindow mode. Emacs has several nice commands for which I have not-so-nice work arounds (opening and closing windows). These are: (raise-frame f) (iconify-frame f) (decionify-frame f) (make-frame-visible f) None of these work with Cygwin X. Thanks Gulliver -- 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/ From Ralf.Oltmanns@financial.com Mon May 26 13:19:00 2014 From: Ralf.Oltmanns@financial.com (Ralf Oltmanns) Date: Mon, 26 May 2014 13:19:00 -0000 Subject: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11 Message-ID: To whom it may concern, I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 XWin was started with the following command-line: X :0 -multiwindow Please find attached the XWin.0.log. Kind regards Ralf Oltmanns Systems Adminstrator financial.com AG Munich Head Office/Hauptsitz M?nchen: Georg-Muche-Stra?e 3 | 80807 Munich | Germany | Tel. +49 89 318528-0 | Google Maps: http://goo.gl/maps/UHwj9 Frankfurt Branch Office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt am Main | Germany | Google Maps: http://goo.gl/maps/oSGjR Management Board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson Supervisory Board/Aufsichtsrat: Rolf Richter (Chairman/Vorsitzender) Register Court/Handelsregister: Munich ? HRB 128972 | Sales Tax ID Number/St.Nr.: DE205370553 -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 7723 bytes Desc: XWin.0.log URL: -------------- next part -------------- -- 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/ From jon.turney@dronecode.org.uk Mon May 26 13:32:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 26 May 2014 13:32:00 -0000 Subject: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11 In-Reply-To: References: Message-ID: <53834272.4050605@dronecode.org.uk> On 26/05/2014 14:18, Ralf Oltmanns wrote: > I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). > > When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) > > My installation is as follows: > Release: 1.15.0.0 > Package: version 1.15.0-2 built 2014-01-11 Thanks for the bug report. The current XWin version is 1.15.1-2. Perhaps you could try again with that? If that doesn't resolve your problem, I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Could you then install the xorg-server-debuginfo package, which enables a more useful backtrace to be generated in the log, and try again? With 1.15.1, I also enabled a tool I have been working to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- 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/ From Ralf.Oltmanns@financial.com Mon May 26 15:55:00 2014 From: Ralf.Oltmanns@financial.com (Ralf Oltmanns) Date: Mon, 26 May 2014 15:55:00 -0000 Subject: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11 In-Reply-To: <53834272.4050605@dronecode.org.uk> References: <53834272.4050605@dronecode.org.uk> Message-ID: <538363EE.2090402@financial.com> Hi Jon, I updated to 1.15.1-2 and placed the crash-reporter into cygwin64/bin. A crash report has been submitted to your server. The same problem still persists. Regards Ralf On 05/26/2014 03:32 PM, Jon TURNEY wrote: > On 26/05/2014 14:18, Ralf Oltmanns wrote: >> I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). >> >> When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) >> >> My installation is as follows: >> Release: 1.15.0.0 >> Package: version 1.15.0-2 built 2014-01-11 > > Thanks for the bug report. > > The current XWin version is 1.15.1-2. Perhaps you could try again with > that? > > If that doesn't resolve your problem, I'm afraid that the log doesn't > contain enough information for me to identify the cause of the crash. > > Could you then install the xorg-server-debuginfo package, which enables > a more useful backtrace to be generated in the log, and try again? > > With 1.15.1, I also enabled a tool I have been working to automate > sending better crash information using minidumps. If you would like to > try that, download it from [1] (anonymous ftp) and put it into /usr/bin > and reproduce your crash again. > > [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe > -- Ralf Oltmanns Systemadministrator financial.com AG Munich Head Office/Hauptsitz M?nchen: Georg-Muche-Stra?e 3 | 80807 Munich | Germany | Tel. +49 89 318528-0 | Google Maps: http://goo.gl/maps/UHwj9 Frankfurt Branch Office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt am Main | Germany | Google Maps: http://goo.gl/maps/oSGjR Management Board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson Supervisory Board/Aufsichtsrat: Rolf Richter (Chairman/Vorsitzender) Register Court/Handelsregister: Munich ? HRB 128972 | Sales Tax ID Number/St.Nr.: DE205370553 -- 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/ From hgs@chalmers.se Tue May 27 11:45:00 2014 From: hgs@chalmers.se (Hans-Georg Scherneck) Date: Tue, 27 May 2014 11:45:00 -0000 Subject: emacs holding focus, not granting it to xterm Message-ID: <53847AC8.6070000@chalmers.se> I'm running cygwin x on my laptop [version 1.7.29(0.272/5/3), Windows 7 prof], start windows on remote machines (cygwin and linux mint), that are exported to my laptop. I've noted the problem for more than a year now and it's irritating still, new versions of cygwin and applications notwithstanding. Here's what happens: I enter text into emacs, move mouse to an xterm, click and enter text there, but text is going into emacs. I can only move keyboard flow away from emacs after having done some nuisance operations in the emacs window, like moving around the pointer; it mostly helps with one such instance, sometimes I have to repeat. It's rather unpredictable. The raised status of the xterm window, however, is deceiving me. So text goes even into hidden emacs windows. Vague guess: Something's waiting in emacs to get satisfied so it would release the keyboard association. I don't want focus-follows-mouse without a click for focus shift. So I haven't tried this option. Would expect it wouldn't help. Is there an environment setting that would help? Anything else to get rid of the glue? -- Med v??nliga h??lsningar / With best regards yours ----- Hans-Georg Scherneck / A \ ---------------------+----------------------------------- | / \ | . Telephone & -fax | Chalmers University of Technology \ / . +46 31 772 5556 | Earth and Space Sciences ----- . +46 31 772 5590 fx | & Onsala Space Observatory | | . E-Mail: | SE-439 92 Onsala, Sweden / \ . hgs@chalmers.se | http://www.chalmers.se/rss ---------------- . Ocean Loading Serv.| holt.oso.chalmers.se/loading /===\ ,===//===\ . Gravimeter | holt.oso.chalmers.se/hgs/SCG / /`===,/ / ---------------------+---------------------------------\===//===' \===/ -- 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/ From p.fedin@samsung.com Tue May 27 12:52:00 2014 From: p.fedin@samsung.com (Pavel Fedin) Date: Tue, 27 May 2014 12:52:00 -0000 Subject: Automatic X server startup Message-ID: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> Hello! Recently i have started using Insight (https://sourceware.org/insight/) under Cygwin/X. Everything is quite good except one thing. I remember once upon a time i worked on MacOS X. There, X server starts up automatically if there is some program requesting it. On Cygwin i still have to run it by hands. Is is possible to set up autostart of the X server ? May be i just don't know how to do it ? Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- 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/ From moss@cs.umass.edu Tue May 27 13:38:00 2014 From: moss@cs.umass.edu (Eliot Moss) Date: Tue, 27 May 2014 13:38:00 -0000 Subject: Automatic X server startup In-Reply-To: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> References: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> Message-ID: <53849544.10407@cs.umass.edu> On 5/27/2014 8:52 AM, Pavel Fedin wrote: > Hello! > > Recently i have started using Insight (https://sourceware.org/insight/) > under Cygwin/X. Everything is quite good except one thing. > I remember once upon a time i worked on MacOS X. There, X server starts up > automatically if there is some program requesting it. On Cygwin i still have > to run it by hands. Is is possible to set up autostart of the X server ? May > be i just don't know how to do it ? I use the xlaunch program and have it set to start when I log in. It can start programs for you, if you want anything started from the beginning, but you can have it run no programs and simply wait for any X programs to come along. If you run xlaunch with no arguments it pops up a short interactive GUI for setting up the configuration. And of course "man xlaunch" will tell you more. Best wishes -- Eliot Moss -- 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/ From jon.turney@dronecode.org.uk Tue May 27 15:20:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 27 May 2014 15:20:00 -0000 Subject: Automatic X server startup In-Reply-To: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> References: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> Message-ID: <5384AD24.4080504@dronecode.org.uk> On 27/05/2014 13:52, Pavel Fedin wrote: > Recently i have started using Insight (https://sourceware.org/insight/) > under Cygwin/X. Everything is quite good except one thing. > I remember once upon a time i worked on MacOS X. There, X server starts up > automatically if there is some program requesting it. On Cygwin i still have > to run it by hands. Is is possible to set up autostart of the X server ? May > be i just don't know how to do it ? I believe this is arranged using launchd on OS X, which listens on the socket the X server will use, and starts the X server when something connects. Unfortunately, there is no similar system facility on Windows. You can achieve a somewhat similar effect by copying the X server shortcut to the startup group to start it automatically at login, at the cost of slowing down system startup somewhat. -- 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/ From jon.turney@dronecode.org.uk Tue May 27 15:27:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 27 May 2014 15:27:00 -0000 Subject: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11 In-Reply-To: <538363EE.2090402@financial.com> References: <53834272.4050605@dronecode.org.uk> <538363EE.2090402@financial.com> Message-ID: <5384AED9.5010907@dronecode.org.uk> On 26/05/2014 16:55, Ralf Oltmanns wrote: > I updated to 1.15.1-2 and placed the crash-reporter into cygwin64/bin. A > crash report has been submitted to your server. The same problem still > persists. Thanks very much. Could you please also install the xorg-server-debuginfo package, remove xorg_cygwin_crash_reporter_gui and show the log you get then? > On 05/26/2014 03:32 PM, Jon TURNEY wrote: >> On 26/05/2014 14:18, Ralf Oltmanns wrote: >>> I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). >>> >>> When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) >>> >>> My installation is as follows: >>> Release: 1.15.0.0 >>> Package: version 1.15.0-2 built 2014-01-11 >> >> Thanks for the bug report. >> >> The current XWin version is 1.15.1-2. Perhaps you could try again with >> that? >> >> If that doesn't resolve your problem, I'm afraid that the log doesn't >> contain enough information for me to identify the cause of the crash. >> >> Could you then install the xorg-server-debuginfo package, which enables >> a more useful backtrace to be generated in the log, and try again? >> >> With 1.15.1, I also enabled a tool I have been working to automate >> sending better crash information using minidumps. If you would like to >> try that, download it from [1] (anonymous ftp) and put it into /usr/bin >> and reproduce your crash again. >> >> [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- 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/ From p.fedin@samsung.com Wed May 28 12:57:00 2014 From: p.fedin@samsung.com (Pavel Fedin) Date: Wed, 28 May 2014 12:57:00 -0000 Subject: Automatic X server startup In-Reply-To: <5384AD24.4080504@dronecode.org.uk> References: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> <5384AD24.4080504@dronecode.org.uk> Message-ID: <004001cf7a74$5c6b3ac0$1541b040$%fedin@samsung.com> Hello! > I believe this is arranged using launchd on OS X, which listens on the > socket the X server will use, and starts the X server when something > connects. > > Unfortunately, there is no similar system facility on Windows. But it should be possible to make xlib a little bit more smart, isn't it ? It could automatically run X server when a connection is attempted but refused. So we would achieve the same effect as on MacOS. We could e. g. have some directory like /etc/X11/autostart, to be examined by xlib. If it detects that e. g. :0 screen is not accessible, it would attempt to look up 0.xlaunch file there and run "xlaunch -run /etc/X11/autostart/0.xlaunch" command. What do you think ? I could implement this idea if you have no time to work on that, i believe it should be very easy. > You can achieve a somewhat similar effect by copying the X server > shortcut to the startup group to start it automatically at login, at > the cost of slowing down system startup somewhat. Heh, it's already slow because of antivirus and other corporate stuff (i cannot disable it). Running on demand would be better. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- 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/