touch-packages team mailing list archive

[Launchpad Bug Tracker <1432899@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
       Status: New => Confirmed

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

Title:
  VESA error: Cannot read int vect

Status in Xorg Xserver VESA:
  New
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-driver-vesa package in Ubuntu:
  Confirmed

Bug description:
  After installing the most recent updates on Vivid Vervet within a KVM
  virtual machine, the X server fails to start up with error message
  "VESA(0): Cannot read int vect". During the recent update, several
  xserver-xorg-* packages were upgraded; the X server (xserver-xorg-
  core) was updated from 1.16.2.901-1ubuntu4 to 1.17.1-0ubuntu2.

  After some searching, I found, this upstream patch may have introduced the issue:
  http://cgit.freedesktop.org/xorg/xserver/commit/hw/xfree86/int10?id=21b216ad6ce2e9c89359b95e4196e42d91bf9420

  Excerpt from X.org log:

  [  3612.095] (II) LoadModule: "vbe"
  [  3612.095] (II) Loading /usr/lib/xorg/modules/libvbe.so
  [  3612.095] (II) Module vbe: vendor="X.Org Foundation"
  [  3612.095] 	compiled for 1.17.1, module version = 1.1.0
  [  3612.095] 	ABI class: X.Org Video Driver, version 19.0
  [  3612.095] (II) Loading sub module "int10"
  [  3612.095] (II) LoadModule: "int10"
  [  3612.095] (II) Loading /usr/lib/xorg/modules/libint10.so
  [  3612.096] (II) Module int10: vendor="X.Org Foundation"
  [  3612.096] 	compiled for 1.17.1, module version = 1.0.0
  [  3612.096] 	ABI class: X.Org Video Driver, version 19.0
  [  3612.096] (II) VESA(0): initializing int10
  [  3612.096] (EE) VESA(0): Cannot read int vect
  [  3612.096] (II) UnloadModule: "vesa"
  [  3612.096] (II) UnloadSubModule: "int10"
  [  3612.096] (II) Unloading int10
  [  3612.096] (II) UnloadSubModule: "vbe"
  [  3612.096] (II) Unloading vbe
  [  3612.096] (EE) Screen(s) found, but none have a usable configuration.
  [  3612.096] (EE) 
  Fatal server error:
  [  3612.096] (EE) no screens found(EE) 

  The full X.org log has been attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-vesa/+bug/1432899/+subscriptions