From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: xorg-server-1.18.3-1
Date: Tue, 12 Jul 2016 06:02:00 -0000 [thread overview]
Message-ID: <342edbeb-00a9-f30c-1a53-b6c84dde970f@gmail.com> (raw)
In-Reply-To: <YEnxm5kk/QmkvVS5AtYMhI@4GugzL7zRhT1bMFYSRuBg>
On 11/07/2016 23:13, Jack wrote:
> On 2016.07.11 16:31, Marco Atzeri wrote:
>>
>>
>> On 21/06/2016 19:04, Jon Turney wrote:
>>>
>>> The following packages have been updated in the Cygwin distribution:
>>>
>>> *** xorg-server-*1.18.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.18.2-1:
>>>
>>> * In multiwindow mode, enable the -compositewm option by default, so
>>> top-level window contents which are occluded are shown correctly in task
>>> bar and task switcher previews. Add a -nocompositewm option so it can
>>> be disabled.
>>> * Fix any custom sysmenu configured in .XWinrc not being used when
>>> window is initially shown (Thanks to Colin Harrison)
>>>
>>> [1] https://lists.x.org/archives/xorg-announce/2016-April/002683.html
>>>
>>
>> 32 bit seem to have an issue. 64 bit is fine
>>
[cut]
> It works fine for me, with cygwin 32 bit under Windows 7 Pro 32 bit,
> although my CPU is actually 64 bit. Let me know if you want any other
> details about my system.
>
> Jack
Thanks for the confirmation.
After a reboot the 32 bit restarted to work, I suspect there was
some type of race and XWin was always loosing.
I am back to the *normal* with both versions, where normal means
only the first race is usually lost but all the successive are fine.
May be WOW need more time to load dll's.
$ uname -svrm
CYGWIN_NT-6.1-WOW 2.5.2(0.297/5/3) 2016-06-23 14:27 i686
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-07-12 6:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <564F47CC.70306@dronecode.org.uk>
2015-11-20 16:31 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.0-1 (TEST) Jon Turney
[not found] ` <564F4A62.9070202@dronecode.org.uk>
2016-01-13 5:56 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.0-2 (TEST) Jon Turney
2016-01-27 21:01 ` Jon Turney
2016-02-19 16:20 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.1-1 Jon Turney
2016-03-03 15:19 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.1-2 Jon Turney
2016-03-25 12:35 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.2-1 Jon Turney
2016-06-21 20:33 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.3-1 Jon Turney
2016-07-11 20:31 ` Marco Atzeri
2016-07-11 21:14 ` Jack
2016-07-12 6:02 ` Marco Atzeri [this message]
2016-07-23 12:17 ` [ANNOUNCEMENT] Updated: xorg-server-1.18.4-1 Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=342edbeb-00a9-f30c-1a53-b6c84dde970f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).