public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Pete <sneakypete81@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: XServer draws to incorrect window when using VirtuaWin
Date: Fri, 03 Sep 2010 09:01:00 -0000	[thread overview]
Message-ID: <AANLkTin-fHMEfHKE+PEL72s0bxvfzaC5mzLjFHCnho5W@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin1qcb7NkF9zfbaMBSXxS8ya-2daTtDox0ddHic@mail.gmail.com>

On 13 August 2010 11:38, Pete <sneakypete81@gmail.com> wrote:
> VirtuaWin (http://virtuawin.sourceforge.net/) is a virtual desktop
> manager for Windows that lets you switch between several "virtual
> desktops", similar to those provided in KDE & Gnome.
>
> When switching between desktops that have CygwinX windows open,
> occasionally the Xserver draws to the wrong window. This is difficult
> to describe, so will continue with an example:
>
> Using Windows 7, Cygwin/X v1.8.0
>
> Steps to reproduce:
> 1) Install VirtuaWin from http://virtuawin.sourceforge.net/
> 2) Start the CygwinX server
> 3) Open a (DOS) cygwin window
> 4) Type "xterm &" twice, to open two xterm windows. Maximise these two
> windows to full screen.
> 5) Move one of these windows to desktop2
> 6) Type "ping google.com -n 1000" to get a stream of data appearing in
> the xterm window on desktop2
> 7) Go back to desktop1, and make sure the DOS cygwin window is selected
> 8) Switch back to desktop2. The "ping" xterm window should be selected.
> 9) Switch back to desktop1. The cygwin window should be selected.
>
> What should happen:
> The empty xterm session on desktop1 should be displayed in the window
> behind the cygwin window
>
> What happens:
> The ping data stream appears in the xterm window on desktop1, and
> continues receiving updates every second.
> Selecting the xterm window causes the ping data to disappear and the
> empty xterm session to be displayed correctly.
>
> This is reproducible every time. The critical thing is that if the
> xterm window on desktop1 is not selected after a desktop switch, it
> shows the data from the xterm window on desktop 2.
>
> FWIW, this problem doesn't exist with xming, and I haven't seen the
> issue with any other applications.
>
> Any questions, please let me know.
> Thanks,
> Pete
>

Is there anything else I can do to help debug this? Unfortunately it
is necessary to install VirtuaWin to reproduce the issue, but it's
very reproducible.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2010-09-03  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimMGMLYqBe4pDPO=R5NJ+vV8em9EpEorRN=Ah7D@mail.gmail.com>
     [not found] ` <AANLkTinuqPcousugZwCVhPP3vgZ5tKrX39wbi2Wmr1BR@mail.gmail.com>
     [not found]   ` <AANLkTim5rt1Pn-uVmf7p6iuS3Dc-oQXwSKTStcuMwKJq@mail.gmail.com>
2010-08-13 11:09     ` Pete
2010-09-03  9:01       ` Pete [this message]
2010-09-07 13:38         ` Jon TURNEY
2010-09-07 15:54           ` Pete
2010-10-03 23:05           ` Marcin Wiśnicki
2010-10-03 23:30             ` Marcin Wiśnicki

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=AANLkTin-fHMEfHKE+PEL72s0bxvfzaC5mzLjFHCnho5W@mail.gmail.com \
    --to=sneakypete81@gmail.com \
    --cc=cygwin-xfree@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).