I noticed that updating to the latest xinit (1.3.4-1) from the previous
one (1.3.2 I believe) completely breaks existing configurations.
The changes have been mentioned in the release announcement:
https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html
And numerous posts have since reported
Laurens Blankers wrote:
I noticed that updating to the latest xinit (1.3.4-1) from the previous
one (1.3.2 I believe) completely breaks existing configurations.
What about changing the way X server is started? I flagged here:
https://cygwin.com/ml/cygwin-xfree/2014-11/msg00040.html
my
On 30-12-2014 13:46, Angelo Graziosi wrote:
What about changing the way X server is started?
I could change the way I start X, and I have successfully gotten things
to work by doing so. But that is not my point. My point is that I need
to make significant changes to the configuration to get back
Laurens Blankers wrote:
Then I drag the X icon to my
Start-up folder, so that it starts every time my desktop boots
The same you can do with the link created as suggested in my previous
replay. When I had Win XP I did that way for almost 7 years without
tacking care of any configuration
On 30-12-2014 17:04, Angelo Graziosi wrote:
The same you can do with the link created as suggested in my previous
replay.
You are probably right, but again, that is not the issue. The point I am
trying to make is that breaking configurations which have worked for
many years in a patch release is
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.16.3-1
These packages contain XWin and the other X.Org X11 servers.
In addition to upstream fixes [1], the following cygwin-specific changes
have been made since 1.16.2-1:
* Defend against and report
