All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1819908@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1819908] Re: slight screen corruption when maximizing window
Date: Tue, 20 Apr 2021 08:29:18 -0000	[thread overview]
Message-ID: <161890735834.26897.11005526654351866178.malone@gac.canonical.com> (raw)
In-Reply-To: 155248066265.30093.16981724484173262651.malonedeb@gac.canonical.com

Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819908

Title:
  slight screen corruption when maximizing window

Status in QEMU:
  New

Bug description:
  Host: Ubuntu disco
  qemu-kvm: 1:3.1+dfsg-2ubuntu2
  libvirt: 5.0.0-1ubuntu2

  Guest: ubuntu bionic
  guest is using cirrus video, with the extra modules kernel package installed and the cirrus kernel module loaded. I also tried QXL, but got the same problem.

  A non-maximized terminal window works just fine. As an example, I run
  "lsmod". It fills the screen, which then scrolls a bit.

  The moment I maximize that window, though, the rendering breaks. I can
  see the commands I type, but not their output. See attached video.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1819908/+subscriptions


       reply	other threads:[~2021-04-20  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <155248066265.30093.16981724484173262651.malonedeb@gac.canonical.com>
2021-04-20  8:29 ` Thomas Huth [this message]
2021-04-20 12:26 ` [Bug 1819908] Re: slight screen corruption when maximizing window Thomas Huth
2021-06-20  4:17 ` Launchpad Bug Tracker

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=161890735834.26897.11005526654351866178.malone@gac.canonical.com \
    --to=1819908@bugs.launchpad.net \
    --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.