run.exe will not work with upgrade from 1.14.4 to 1.16.3

Yaakov Selkowitz
Mon Jan 5 09:49:00 GMT 2015

On 2015-01-05 03:06, Laurens Blankers wrote:
> On 5-1-2015 05:04, Larry Hall (Cygwin-X) wrote:
> As far as I can tell, from the available information, users which meet
> any of the following criteria will run into trouble:
> - Custom .startxwinrc or .xinitrc

Just .startxwinrc, and the changes were explained in the announcement.

> - Using untrusted X11 forwards over SSH (e.g. ssh -X or PuTTY)

ssh -X hasn't been supported since X11R7.4 way back in 2008 (see the FAQ 
for details).

> As a software engineer I strongly believe in the principle of least
> astonishment [2]. At least for the vast majority of users. In this case,
> in my opinion at least, that would mean that changing the behaviour of
> startxwin should be done in such a way as to provide a seamless way of
> users to upgrade. Preferably by maintaining compatibility with existing
> configurations, or by automatic conversion, or, if necessary through a
> well documented manual transition process.

That's what the announcement was for.

> What I am trying to say is that I don't object to your solutions, but I
> would really like this to be solved in a way that provides a create user
> experience. For me that would mean that the first step would be to
> retract the update (revert back to 1.3.2-1) as to prevent more users
> from running into problems. I do realize that that would mean forcing
> people who have already converted to go back. But I assume this is a
> minority of users. Then I would propose to evaluate what could be done
> to provide a smooth transition, possibly over a longer time, popping up
> increasingly annoying warnings about the configuration, for example.

I am not going to revert the recent changes, which are important and 
long overdue.  If any has constructive suggestions for incremental 
improvements thereto, they will be duly considered, but going backwards 
is not the solution.

>> So I withdraw my previous request that you not post
>> your policy question to the Cygwin main list (since I agree it is a
>> general issue) but instead request that you only discuss the policy and
>> not overlap with the specifics covered in the xinit package threads [..]
> Thank you, I would like to discussion on the general list to be broader.

That won't be necessary.  As a rolling distribution without stable 
releases, these kind of changes in UX happen from time to time.  That's 
what announcements are for.


Unsubscribe info:
Problem reports:

More information about the Cygwin-xfree mailing list