this problem again confirmed for Ubuntu 16.04.1 on i386 during the
install into virtual box 5.1.6

the amount of people affected is assumed to be high and thus even if
there is a work around (but not anybody gets it fast enough how to solve
that but rather assume its just broken) it still would serve the Linux
community much better if those issue is simply fixed and thus never
seen.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1443853

Title:
  Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a
  corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Incomplete
Status in kbd package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0000000000000000 w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0000000000000000 w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=000000000a7f0000 w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.055559 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to