qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1439800] Re: GTK fullscreen mode start stretched but f


From: Viniciusferrao
Subject: [Qemu-devel] [Bug 1439800] Re: GTK fullscreen mode start stretched but fixes after leaving and returning full screen mode
Date: Thu, 02 Apr 2015 20:03:55 -0000

** Tags removed: gkt
** Tags added: gtk

** Description changed:

  I'm running QEMU 2.2.91 compiled directly from git and starting QEMU
- with the -full-screen option. The guest OS is Windows 8.1 using the VGA
- driver from QEMU.
+ with the -full-screen option using the GTK display. The guest OS is
+ Windows 8.1 using the VGA driver from QEMU.
  
- The image can be fixed leaving the full-screen mode and returning it
- back. So it appears that QEMU loses the information with multiple
- resolution changes of the boot process and fails in the end.
+ The GTK window resizes three times on the boot process, and every time
+ it deforms the output, but the image can be fixed leaving the full-
+ screen mode and returning it back. So it appears that QEMU loses the
+ information with multiple resolution changes of the boot process and
+ fails in the end.
  
  The description can be a little confusing, so I've put a video on Youtube, so 
it can demonstrate the real issue:
  https://www.youtube.com/watch?v=-lWbWEUOSsk

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

Title:
  GTK fullscreen mode start stretched but fixes after leaving and
  returning full screen mode

Status in QEMU:
  New

Bug description:
  I'm running QEMU 2.2.91 compiled directly from git and starting QEMU
  with the -full-screen option using the GTK display. The guest OS is
  Windows 8.1 using the VGA driver from QEMU.

  The GTK window resizes three times on the boot process, and every time
  it deforms the output, but the image can be fixed leaving the full-
  screen mode and returning it back. So it appears that QEMU loses the
  information with multiple resolution changes of the boot process and
  fails in the end.

  The description can be a little confusing, so I've put a video on Youtube, so 
it can demonstrate the real issue:
  https://www.youtube.com/watch?v=-lWbWEUOSsk

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]