From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: BALATON Zoltan <balaton@eik.bme.hu>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Monitor and serial output window broken with SDL2
Date: Tue, 18 Dec 2018 11:16:03 +0000 [thread overview]
Message-ID: <20181218111603.GE22638@redhat.com> (raw)
In-Reply-To: <f3d7a0ed-785d-4176-147d-26a4d58d1a36@ilande.co.uk>
On Tue, Dec 18, 2018 at 10:54:06AM +0000, Mark Cave-Ayland wrote:
> On 17/12/2018 14:56, BALATON Zoltan wrote:
>
> > I still have this problem after updating everything on my machine, latest QEMU and
> > SDL 2.0.9 so it's not likely to be a bug in some external component. If I just start
> > qemu-system-ppc (compiled with --disable-gtk) and try to open monitor console with
> > Ctrl-Alt-2 I see QEMU monitor but when I type in this window the serial output window
> > contents flash in this window. At the same time the window that opens for Ctrl-Alt-3
> > which should have the serial output is empty. It looks like an index may be off
> > somewhere or window contents are not associated with the right window but I have no
> > idea where to look for it. Can you reproduce it now and do you have any idea what
> > could cause this?
>
> Are you using Fedora Core 29 at all? I know Howard has been experiencing redraw
> issues since upgrading from FC 28 to FC 29. A couple of other things to check:
There is no "Fedora Core" since Fedora Core 6, just Fedora :-P
But seriously, I teted on Fedora 29 and didn't see any problem, so there
must be some more specific scenario that is hurting it.
> 1) Does QEMU 3.0 work correctly? If so, a bisection would help.
> 2) Are you using an Nvidia graphics card with the nouveau driver?
This second point is a good idea to consider.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-12-18 11:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 22:43 [Qemu-devel] Monitor and serial output window broken with SDL2 BALATON Zoltan
2018-03-21 14:06 ` Gerd Hoffmann
2018-03-21 17:25 ` BALATON Zoltan
2018-12-17 14:56 ` BALATON Zoltan
2018-12-17 15:00 ` Daniel P. Berrangé
2018-12-17 21:57 ` BALATON Zoltan
2018-12-18 5:54 ` Gerd Hoffmann
2018-12-18 10:58 ` Daniel P. Berrangé
2018-12-18 10:54 ` Mark Cave-Ayland
2018-12-18 11:16 ` Daniel P. Berrangé [this message]
2018-12-18 13:11 ` BALATON Zoltan
2018-12-18 13:27 ` Daniel P. Berrangé
2018-12-18 19:05 ` BALATON Zoltan
2018-12-19 9:53 ` Daniel P. Berrangé
2018-12-19 18:11 ` BALATON Zoltan
2018-12-20 5:42 ` Gerd Hoffmann
2018-12-20 11:18 ` BALATON Zoltan
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=20181218111603.GE22638@redhat.com \
--to=berrange@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=mark.cave-ayland@ilande.co.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.