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 21:19:29 +0200 [thread overview]
Message-ID: <20161215211838-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20161215202505-mutt-send-email-mst@kernel.org>
On Thu, Dec 15, 2016 at 09:15:27PM +0200, Michael S. Tsirkin wrote:
> On Thu, Dec 15, 2016 at 05:25:50PM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > > > 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
> >
> > [ 2.6 good, 2.7, 2.8 bad ]
> >
> > > I'd say SDL is mostly useless with this bug.
> > >
> > > Do we fix this or disable SDL altogether?
> >
> > Well, it can't be *that* bad, otherwise it would not went unnoticed for
> > a whole release cycle.
>
> That's what I'm saying, maybe no one uses SDL anymore.
>
> > It doesn't reproduce here.
>
> Are you on Fedora 25 too?
>
> > There must be some other factor which is
> > needed to trigger this. What desktop you are using? gnome? kde?
> > something else?
>
> XFCE
>
> > Xorg or wayland?
>
> Xorg
>
> > Can you try to bisect it?
> >
> > cheers,
> > Gerd
>
>
> Trying to.
One strange thing - I only see it when guest is in graphical mode.
If guest is in text mode it works ok.
Command line:
./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 1000 -cpu host -smp 2
/home/mst/images/f20-x64.qcow2 -netdev user,id=foo -redir tcp:8022::22
-device virtio-net,netdev=foo -kernel /boot/vmlinuz-${release} -initrd
/boot/initramfs-${release}.img -append 'root=/dev/sda3 ro
vconsole.font=latarcyrheb-sun16 rhgb noquiet LANG=en_US.UTF-8
console=tty0 console=ttyS0,9600n8,9600n8' -sdl
so nothing special.
next prev parent reply other threads:[~2016-12-15 19:19 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
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 [this message]
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=20161215211838-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).