public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin-xfree@cygwin.com
Subject: Re: XWin.exe causes Windows apps. to freeze
Date: Mon, 21 Nov 2011 17:40:00 -0000	[thread overview]
Message-ID: <4ECA8CEB.7080805@cs.utoronto.ca> (raw)
In-Reply-To: <CAK-n8j7HbTstUvLgZWj-W6ySTpTwwOeB-fMZPXsW6vCRRezA=Q@mail.gmail.com>

On 21/11/2011 12:14 PM, Jim Reisert AD1C wrote:
> I have a persistent problem at work after XWin has been running for a
> while (sometimes hours, sometimes days).  Windows programs will
> spontaneously freeze
> For example,
> I'm composing a message in Outlook, and all of a sudden, my keyboard
> stops responding, then I'll get the Windows hourglass in that window.
> Or I'll be surfing in Firefox and window changes just stop, again
> hourglass.  Once this happens, killing XWin.exe from the task manager
> immediately releases the hang condition(s), though the hang may
> release itself if I wait several minutes (yeah, right).  At this
> point, I can re-start XWin, but later on, it will happen again.
>
> I'm starting XWin.exe from the install shortcut:
>
>    C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe
>
> I'm running the latest of Cygwin everything, the problem has been
> across several (many) releases of the Xorg server.  I think it's using
> the default options for multi-monitor, cut/paste, etc.  I can usually
> copy/paste between XWin and MS Windows (and usually Citrix) without
> any problems.  I keep thinking that the problem is something in the
> XWin code that interfaces to Windows' copy/paste engine (OLE?).
If you think it's clipboard related, try running with -noclipboard and 
see if that fixes it. Downside is, you lose all clipboard functionality...

BTW, what do you use x11 for? Other than the odd gnuplot session, I've 
not needed an X server since switching from xterm to mintty (which just 
became the official cygwin terminal). If a similar situation applies to 
you, you could temporarily switch to mintty while doing the above 
experiment and still be able to use clipboard in the meantime.

Finally, I've never used a multi-monitor setup myself, but according to 
the XWin man page you should specify the -multimonitors option since you 
apparently (really??) don't run in -multiwindow mode. Or maybe the man 
page is just out of date and -multiwindow is the default now, in which 
case multiple monitor support comes for free.

Ryan


--
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:[~2011-11-21 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 17:14 Jim Reisert AD1C
2011-11-21 17:40 ` Ryan Johnson [this message]
2011-11-21 17:58   ` Jim Reisert AD1C
2011-11-21 20:07     ` Andy Koppe
2011-11-21 20:21     ` Ryan Johnson
2011-11-21 21:26       ` Jim Reisert AD1C
2011-11-21 23:46         ` Ryan Johnson
2011-11-22  5:27           ` Andy Koppe
2011-11-22  5:47             ` Ryan Johnson
2011-11-22 21:28             ` Jim Reisert AD1C

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=4ECA8CEB.7080805@cs.utoronto.ca \
    --to=ryan.johnson@cs.utoronto.ca \
    --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).