public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ed Avis <ed@membled.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Feature request: version report
Date: Wed, 03 Mar 2004 20:46:00 -0000	[thread overview]
Message-ID: <l1ad2xd5w2.fsf@budvar.future-i.net> (raw)
In-Reply-To: <404558DC.6050002@msu.edu>

Harold L Hunt II <huntharo@msu.edu> writes:

>>If you could add some means to manually kill and/or restart the
>>clipboard code inside the X server then I could switch back without
>>the risk of losing work,

>I would add a manual kill/restart as a last resort in a few months.
>Until then I would prefer to swat bugs rather than try to work around
>the problem.

I agree that fixing the bugs is better, but as well as testing XWin to
find bugs I also try to use it for work, and if Windows apps hang
unrecoverably then I can't use the clipboard support.  So you may be
able to swat bugs faster if users can use the software with less risk.

>XFree86-xserv-4.3.0-49 has some changes that may help to recover from
>and/or to prevent the deadlock situations.  Please try it and let me
>know if it improves things or not.

Thanks for looking at this - I will try 4.3.0-50.  (And try running
with -clipboard once again.)

-- 
Ed Avis <ed@membled.com>


  reply	other threads:[~2004-03-03 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02  8:28 Ed Avis
2004-03-02 15:18 ` Harold L Hunt II
2004-03-02 19:58   ` Ed Avis
2004-03-03  4:02     ` Harold L Hunt II
2004-03-03 20:46       ` Ed Avis [this message]
2004-03-08  9:18         ` Still clipboard deadlock with 4.3.0-50 Ed Avis
2004-03-08 19:15           ` Harold L Hunt II
2004-03-08 20:16             ` Ed Avis
2004-03-08 20:35               ` Igor Pechtchanski
2004-03-09 12:58                 ` Ed Avis
2004-03-09 15:18                   ` Really still " Ed Avis
2004-03-10  3:54                     ` Harold L Hunt II
2004-03-10  9:48                       ` Ed Avis

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=l1ad2xd5w2.fsf@budvar.future-i.net \
    --to=ed@membled.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).