qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Philip Boulain <prb@ecs.soton.ac.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Triple-fault causes abort(), which doesn't end pointer grabs
Date: Tue, 08 May 2007 17:46:17 +0100	[thread overview]
Message-ID: <1178642777.6713.8.camel@panther> (raw)
In-Reply-To: <jeps5bmftd.fsf@sykes.suse.de>

On Tue, 2007-05-08 at 18:38 +0200, Andreas Schwab wrote:
> Samuel Bronson <naesten@gmail.com> writes:
> > So, if the guest system has a triple-fault, and I had had my mouse grabbed, it
> > stays grabbed, so that X has to be restarted (as far as I know).
> Not if you have XF86_Ungrab bound to a key.

That's a workaround, not a fix.

Phil

      reply	other threads:[~2007-05-08 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 19:51 [Qemu-devel] Triple-fault causes abort(), which doesn't end pointer grabs Samuel Bronson
2007-05-08 16:30 ` Paul Brook
2007-05-13 19:59   ` Samuel Bronson
2007-05-08 16:38 ` Andreas Schwab
2007-05-08 16:46   ` Philip Boulain [this message]

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=1178642777.6713.8.camel@panther \
    --to=prb@ecs.soton.ac.uk \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).