Jon TURNEY | 3 Mar 21:38 2015

[ANNOUNCEMENT] cygwin-xfree list deprecation

Dear Internet,

It no longer makes much sense to have a separate list for Cygwin X 
related traffic, so the cygwin-xfree list is now officially deprecated.

Reasons for this decision include:
- the level of traffic on the cygwin-xfree list is low
- splitting the traffic in this way currently serves no useful purpose
- the distinction between what is and is not an X issue is artificial, 
vague, and often ignored

The cygwin-xfree list will continue to operate, but I suggest and 
encourage you to use the main cygwin list for all your cygwin X server 
and X application related questions, bug reports, moans, gripes, whines 
and patches ;-).

The Cygwin X website and documentation will be updated to point to the 
main cygwin list.

Mail delivery for the cygwin-xfree list may be turned off at some future 
date, but even if that happens, the list archives will continue to be 

Live Long and Prosper,


Volunteer Cygwin/X X Server maintainer
(Continue reading)

Corinna Vinschen | 3 Mar 21:23 2015

[ANNOUNCEMENT] Merge of cygwin-xfree-announce into cygwin-announce

Hi folks,

it's becoming awkward having to split package announcements between two
mailing lists.  In fact, there's neither a good reason having to decide
where to send an announcement, nor having to subscribe to two lists for
Cygwin package announcements.

Therefore, effectiv immediately, we're going to give up the
cygwin-xfree-announce mailing list in favor of only the cygwin-announce
mailing list.

In future, new Cygwin packages and package updates will be announced on
cygwin-announce only.

If you're not subscribed to cygwin-announce, only to cygwin-xfree-announce,
I'll suggest to subscribe to cygwin-announce instead.

For reference and archeological diggings, the cygwin-xfree-announce
archives will stay available.



Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

(Continue reading)

Jim Reisert AD1C | 25 Feb 18:22 2015

Xorg server 1.7.1 spontaneously exiting with clipboard message

I've created a separate thread for tracking this problem.

The attached files are from the computer at work.  I have never seen
the problem here before, only at home (both running Windows 7 64-bit).
The computer at home has been showing this symptom since later
versions of the server (1.6.x).

[118193.783] winDeinitMultiWindowWM - Noting shutdown in progress
[118193.783] winClipboardProc - winClipboardFlushWindowsMessageQueue
trapped WM_QUIT message, exiting main loop.
[118193.783] winClipboardProc - XDestroyWindow succeeded.
[118193.783] winClipboardIOErrorHandler!
[118193.783] winMultiWindowXMsgProcIOErrorHandler!
[118193.783] winInitMultiWindowXMsgProc - Caught IO Error.  Exiting.
[118193.829] winDeinitMultiWindowWM - Noting shutdown in progress
[118193.829] (II) Server terminated successfully (0). Closing log file.

Here's how I start the server:

    C:\Cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;

Cygwin version:

    CYGWIN_NT-6.1-WOW machine 1.7.35(0.286/5/3) 2015-02-18 11:28 i686 Cygwin

I have a faint sneaking suspicion that the problem is related to
TeamViewer remote access software:
(Continue reading)

Maarten Hoes | 25 Feb 00:06 2015

Display issue


Im experiencing an issue where the graphics arent displayed correctly. 
When I start LibreOffice on my Fedora 21 Linux system from a cygwin/x 
system, the left hand side (open file, template, writer document, etc.) 
isnt displayed properly initially. After clicking around some, the 
display updates and gets displayed right.

Here's a screenshot of the badly displayed graphics:

And this is what it looks like (correctly) after some clicking around:

I have no idea on how to start troubleshooting the issue; all thoughts 
and ideas are more than welcome.

- Maarten

Unsubscribe info:
Problem reports:

Will Parsons | 24 Feb 21:59 2015

X refuses to start

I'm accustomed to start X via a shortcut which runs the command:

C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l \
-c "cd; /usr/bin/startxwin -- -listen"

This was working, but now doesn't, with the following shown in the log

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
OS: CYGWIN_NT-6.1-WOW sothis 1.7.34(0.285/5/3) 2015-02-04 12:12 i686
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.17.1-2 built 2015-02-23

XWin was started with the following command line:

/usr/bin/XWin :0 -listen -auth /home/william/.serverauth.4460

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1366 h 768
winInitializeScreenDefaults - native DPI x 96 y 96
_XSERVTransTransListen: unable to find transport: -auth
Failed to enable listen for -auth transportUnrecognized option:
use: X [:<display>] [option]
-a #                   default pointer acceleration (factor)
-ac                    disable access control restrictions
-audit int             set audit trail level
(Continue reading)

GEORGE BARRICK | 24 Feb 19:03 2015

Dfficulty with xorg-server-1.17.1-2.

                                    2015.02.24.09:26:38 EST

Hey cygwin folks,

     I've been using xlaunch with a windows desktop shortcut for
about a year to start a multi-window instance of xwin on my Win7
computers.  This is cygwin32 on an installation of Win7_x86-64.
The command within the shortcut is:

C:\cygwin\bin\run.exe /usr/bin/Xlaunch.exe -run ~/config/config.xlaunch

and I've defined the ~-directory to be C:\cygwin\home\gbarrick
using the HOME variable in the Win7 environment.  My .xlaunch-file
is just:

<file: C:/cygwin/home/gbarrick/config/config.xlaunch >
<?xml version="1.0" encoding="UTF-8"?>
<XLaunch WindowMode="MultiWindow" ClientMode="StartProgram"
  LocalClient="True" Display="0" RemoteProtocol=""
  LocalProgram="xterm -rw -sb -rightbar -geometry 128x44+72+60 -bg goldenrod"
  RemoteProgram="" RemoteHost="" RemoteUser="" XDMCPHost=""
  XDMCPBroadcast="False" XDMCPIndirect="False" Clipboard="True"
  ExtraParams="" Wgl="True" DisableAC="False" XDMCPTerminate="False"
  SSHKeyChain="False" SSHTerminal="True" ExtraSSH=""/>

(without the "file:"-tags).  This setup successfully gives me
the multi-window instance of xwin, and generates a
/var/log/xwin/Xwin.0.log file as follows.  The only thing that
I've done is to edit the log-file to better fit the width for
(Continue reading)

Fj | 24 Feb 17:55 2015

Re: Can't open display with PuTTY and xinit 1.3.4-1

On 2015-01-05 05:31, Laurens Blankers wrote:

> When using PuTTY with X11 forwarding enabled X clients are no longer
able to connect to the X server running locally. When reverting back to
1.3.2-1 the problem goes away.

> This may be related to the -nolisten tcp which is now the default[1]. If
this is indeed the case it would be create of adding the '-listen' flag
to startxwin could be added to the FAQ. Or another, more secure,
solution would also be appreciated.

Hi, I updated Cygwin today and hit the same problem, except even after
I added "-listen tcp" xterm (and gvim) still refused to work
complaining about "No protocol specified" (before was: "Can't open

Putty logs say "Opening X11 forward connection succeeded" (before
"-listen tcp" it was: "Forwarded X11 connection terminated due to
local error"), which seems to indicate that the problem is with the X
server (and the way xterm/gvim communicate with it).

Ssh-ing to the server from Cygwin terminal works and I can even launch
gvim from the Putty's tty by specifying the same DISPLAY the Cygwin
connection provides.

After reverting to some early 2014 version of xinit and xorg (thank
god for Cygwin Time Machine) everything resumed working properly.

(on a side note, I tried to figure out what are the possible "-listen"
options by looking at the xserver code, there are three, "tcp",
(Continue reading)

Paul | 24 Feb 15:59 2015

Disable xterm auto-wrap: Mess up vi-like command line

If I disable auto-wrap, the vi editing at the comand line misbehaves
when the line being edited is long, especially when yanking a lot of
text and pasting it.  I suppose that this might be technically correct
behaviour, since an extra long command line needs to wrap in order to
see it properly.  But I use the vi command line exclusively, and
almost always, I don't want autowrap in the results from commands
being sent to the screen.  Is there a way to get both at the same
time, without having to always toggle the xterm autowrap?

Unsubscribe info:
Problem reports:

Michael DePaulo | 24 Feb 04:57 2015

Help porting the XLaunch feature to autoselect the display number


i was talking with Jon Turney about this on IRC.

I am trying to port this feature of VcXsrv (and XMing also I think) to
Cygwin XLaunch:

Attached is my WIP patch. (I know it needs the comments updated for

There's a bug in that is causing this to happen when -1 is specified:

I am not very familiar with C or C++. I am hoping that someone could
give me some advice. (I am much better at Java and bash.)

Unsubscribe info:
Problem reports:
Yaakov Selkowitz | 24 Feb 01:23 2015

[ANNOUNCEMENT] Updated: xedit-1.2.2-1

The following package has been updated in the Cygwin distribution:

* xedit-1.2.2-1

Xedit is a simple text editor for the X Window System.

This is an update to the latest upstream release.  A desktop menu entry
has been added.


Unsubscribe info:
Problem reports:

Yaakov Selkowitz | 24 Feb 01:19 2015

[ANNOUNCEMENT] Updated: glib2.0-2.42.1-2

The following packages have been updated in the Cygwin distribution:

* libglib2.0_0-2.42.1-2
* libglib2.0-devel-2.42.1-2
* libglib2.0-doc-2.42.1-2

GLib is the low-level core library that forms the basis for projects
such as GTK+ and GNOME. It provides data structure handling for C,
portability wrappers, and interfaces for such runtime functionality as
an event loop, threads, dynamic loading, and an object system.

This release fixes the installation of the gdb python scripts in


Unsubscribe info:
Problem reports: