desktop-packages team mailing list archive

[Thomas Hellström <1365490@xxxxxxxxxxxxxxxxxx>]

The problem is I can't verify the bug is fixed in trusty because it doesn't show any obvious symptoms.
This is probably due to different stack ordering of local variables compared to the trusty stack on precise.

The only way to verify the fix is in the trusty stack on precise where
the bug is very obvious...

/Thomas

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1365490

Title:
  ubuntu 12.04.5 broken on VMware

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa-lts-trusty” package in Ubuntu:
  Invalid
Status in “mesa-lts-trusty” source package in Precise:
  Incomplete
Status in “mesa” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  A user might find Ubuntu 12.04.5 unusable on vmware because he would
  face a black screen after logging in. Although there is a workaround
  (disabling 3D) a user may have given up at that point.

  Backporting will help the user run the distro after upgrading, so I
  believe it's highly justified.

  [Test Case]

  On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using "easy install".
  Boot the VM, log in. You'll see a black screen only.

  [Regression Potential]

  The bug affects a function that impots a shared buffer to the 3D
  driver. The function is completely broken by the bug. Even if the
  patch should introduce another type of breakage, the problem couldn't
  be much worse than it already is, and should be confined to the
  specific function in question.

  [Other info]

  Due to different stack ordering of automatic variables, the bug may or
  may not be visible depending on the C compiler and the level of
  optimization used. For example, if -O0 -g is used the bug is not
  visible on 12.04.5. I have not encountered any symptoms of the bug yet
  on 14.04.

  [ Original bug report ]
  Ubuntu 12.04.5 shows a black screen after login with 3D enabled on
  VMware. This is due to a bug in the svga gallium driver's winsys.

  It's recently fixed in mesa master commit 2d6206140a, "winsys/svga: Fix
  incorrect type usage in IOCTL v2", with a request to backport to mesa
  stable, but I'm not sure whether anyone's still maintaining the 10.1 branch.

  Due to the severity of the symptoms it would be greatly appreciated if
  this fix could be incorporated in the
  libgl1-mesa-dri-lts-trusty package as soon as possible.

  Unfortunately it's affecting the package on the installation iso. Is
  there anything that can be done about that?

  Thanks,
  Thomas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions