qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] regression in 2.8: unable to exit screen grab in SDL mode
Date: Thu, 15 Dec 2016 16:55:27 +0200	[thread overview]
Message-ID: <20161215165406-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1481793479.21413.6.camel@redhat.com>

On Thu, Dec 15, 2016 at 10:17:59AM +0100, Gerd Hoffmann wrote:
> On Do, 2016-12-15 at 07:50 +0000, Stefan Hajnoczi wrote:
> > On Thu, Dec 15, 2016 at 06:35:39AM +0200, Michael S. Tsirkin wrote:
> > > The problem always reproduces for me:
> > > - start qemu with -sdl
> > > - wait for guest to boot
> > > - click anywhere within guest screen
> > > - message "press ctrl+alt to exit capture" appears on screen,
> > >   but pressing that immediately restarts capture again
> > > 
> > > Note:
> > > - had to exit to another VT and kill qemu
> > > - why was I able to do that?
> > >   should not ctrl-alt-Fn be captured too?
> > 
> > Sounds related to:
> > 
> > commit 56f289f383a871e871f944c7226920b35794efe6
> > Author: Cole Robinson <crobinso@redhat.com>
> > Date:   Fri May 6 14:03:06 2016 -0400
> > 
> >     ui: sdl2: Release grab before opening console window
> > 
> > Stefan
> 
> Doesn't look related to me, also this is in the v2.7 release already.
> There are no SDL updates in 2.8.  Hmm.  /me looks a bit puzzled.
> 
> What is the known-good setup?
> 
> cheers,
>   Gerd


Testing it now.

BTW I note that on f23, build of 2.7 fails since it uses
deprecated APIs from gtk. Easy to work around with --disable-werror,
but I wonder whether we should add --disable-werror in release tarballs
generally.

-- 
MST

  reply	other threads:[~2016-12-15 14:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 14:25 [Qemu-devel] [PATCH for-2.8] ui/gtk: fix "Copy" menu item segfault Stefan Hajnoczi
2016-12-14 14:35 ` Stefan Weil
2016-12-14 15:15 ` Gerd Hoffmann
2016-12-14 22:49 ` Michael S. Tsirkin
2016-12-15  7:34   ` Stefan Hajnoczi
2016-12-15  7:48   ` Stefan Hajnoczi
2016-12-15  8:47   ` Kevin Wolf
2016-12-15  9:50     ` Stefan Hajnoczi
2016-12-15  4:35 ` [Qemu-devel] regression in 2.8: unable to exit screen grab in SDL mode Michael S. Tsirkin
2016-12-15  7:50   ` Stefan Hajnoczi
2016-12-15  9:17     ` Gerd Hoffmann
2016-12-15 14:55       ` Michael S. Tsirkin [this message]
2016-12-15 16:17         ` Gerd Hoffmann
2016-12-15 15:07       ` Michael S. Tsirkin
2016-12-15 16:25         ` Gerd Hoffmann
2016-12-15 19:15           ` Michael S. Tsirkin
2016-12-15 19:19             ` Michael S. Tsirkin
2016-12-16  8:26               ` Thomas Huth
2016-12-16  8:45                 ` Liviu Ionescu
2016-12-16  9:00                 ` Kevin Wolf
2016-12-16  9:21                   ` Howard Spoelstra
2016-12-16  9:48               ` Gerd Hoffmann
2016-12-15 22:30           ` Michael S. Tsirkin
2016-12-16  9:27             ` Kevin Wolf
2016-12-16  9:36             ` Gerd Hoffmann

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=20161215165406-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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 NNTP newsgroup(s).