From: Ronald Blaschke <mailing-lists@rblasch.org>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: xorg-server-1.17.1-5
Date: Sun, 05 Jul 2015 21:09:00 -0000 [thread overview]
Message-ID: <55999D03.1090605@rblasch.org> (raw)
In-Reply-To: <5595C916.1090104@dronecode.org.uk>
On 07/03/2015 01:28 AM, Jon TURNEY wrote:
> On 15/06/2015 20:08, Ronald Blaschke wrote:
>> On 06/02/2015 07:38 PM, Jon TURNEY wrote:
>>>
>>> The following packages have been updated in the Cygwin distribution:
>>>
>>> *** xorg-server-*1.17.1-5
>>
>> I think this update breaks XWin for me. When starting any client (gvim,
>> emacs-X11), I get a broken window, sometimes empty, sometimes partially
>> filled. I cannot click the content, the click just goes through to the
>> window below, which brings the bottom window up. If I focus the broken
>> window (through the taskbar), I seem to be able to interact with the
>> program, e.g. after inserting something in gvim using the keyboard, the
>> title reflects this through the modified flag ('+'). But again, the
>> content stays empty.
>>
>> If I run XWin without multiwindow, the program (gvim or emacs) renders
>> just fine in the XWin window.
>>
>> If I revert back to 1.17.1-4, multiwindow works just fine as well.
>
> Thanks for reporting this.
>
> This is rather puzzling, as the change in 1.17.1-5 was not directly
> related to how windows are rendered.
Thank you very much for picking this up.
> Can you provide some more details? e.g. an XWin.0.log so I can see if
> that shows anything unusual? Are these local X clients?
After quite some time looking, I think I have found the culprit. I am
using UltraMon on my system. It seems like the changes in 1.17.1-5
interact badly with the Window management feature [1]. The good news
is, this feature can be disabled by program. After excluding XWin.exe,
everything is back to normal. Sorry for the noise, but it's the first
time I have had a problem with either program, so it was hard to make
the connection. I'll probably notify the UltraMon authors, to consider
excluding XWin by default.
Thanks,
Ron
[1] http://www.realtimesoft.com/ultramon/tour/windows.asp
--
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:[~2015-07-05 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55411449.7020106@dronecode.org.uk>
2015-04-29 19:19 ` Updated: xorg-server-1.17.1-3 Robin Flynn
2015-04-29 19:29 ` Eric Blake
2015-05-01 20:40 ` [ANNOUNCEMENT] Updated: xorg-server-1.17.1-4 Jon TURNEY
2015-06-02 17:40 ` [ANNOUNCEMENT] Updated: xorg-server-1.17.1-5 Jon TURNEY
2015-06-15 19:08 ` Ronald Blaschke
2015-07-02 23:28 ` Jon TURNEY
2015-07-05 21:09 ` Ronald Blaschke [this message]
2015-07-08 13:52 ` Jon TURNEY
2015-07-09 16:38 ` [ANNOUNCEMENT] Updated: xorg-server-1.17.2-1 (TEST) Jon TURNEY
2015-07-24 14:59 ` Jon TURNEY
[not found] ` <559EA1AD.5070208@dronecode.org.uk>
2015-07-17 12:01 ` Michael DePaulo
2015-08-12 13:50 ` [ANNOUNCEMENT] Updated: xorg-server-1.17.2-2 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=55999D03.1090605@rblasch.org \
--to=mailing-lists@rblasch.org \
--cc=cygwin@cygwin.com \
--cc=ron@rblasch.org \
/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).