public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Greywolf <greywolf@starwolf.com>
To: cygwin@cygwin.com
Subject: X Windows disappearing/unmapping (Win10 + 3rd party virtual desktops)
Date: Mon, 17 Aug 2015 09:08:00 -0000	[thread overview]
Message-ID: <55D1A466.8060408@starwolf.com> (raw)

ENVIRONMENT:
	OS:	Windows 10 Pro 64-bit
	Cygwin:
		setup 2.871
		X11 1.17.2 (x86_64-unknown-cygwin);
			package version	1.17.2-1 built 2015-07-09
		xterm 318-1
	OTHER:
		3rd party virtual desktop managers - have tried with
		- dexpot 1.6
		- virtuawin 4.3

WHAT HAPPENS:

1.  I start mintty, which starts bash.
2.  I start an X server; DISPLAY=:0
3.  I start an xterm on the local host, to $DISPLAY.
4.  I switch to another desktop on the desktop manager.
5.  I return to that window, and the xterm window vanishes.
	- the processes bound to the window are still running,
	  as is the xterm itself.
6.  I see no way to access or return the window to the desktop.
* even winlister no longer can access the window handle.

The window just hops off the deep end, never to be seen again,
but everything connected with that window remains present.

The only desktop manager it works with is the one that comes with Win10,
but that lacks some features; notably, the ability to directly access a
desktop with a keystroke.  It is just not a viable alternative.

WHY I AM SUBMITTING THIS AS A CYGWIN BUG:

Because this happens as a result of using at least two different
non-microsoft desktop managers, and ONLY X11-based applications
are vanishing (xterm plus, as a test, xfd).

				--*greywolf;



--
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

             reply	other threads:[~2015-08-17  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  9:08 Greywolf [this message]
2015-08-17 15:54 ` Nem W Schlecht
2015-08-18  6:12 ` Greywolf
2015-08-20 19:10   ` Jon TURNEY
2015-08-21 14:49     ` Nem W Schlecht
2015-08-24  3:01     ` Michael Jennings

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=55D1A466.8060408@starwolf.com \
    --to=greywolf@starwolf.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).