desktop-packages team mailing list archive

[Launchpad Bug Tracker <1417034@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity-control-center -
15.04.0+15.04.20150203.2-0ubuntu1

---------------
unity-control-center (15.04.0+15.04.20150203.2-0ubuntu1) vivid; urgency=medium

  [ Sebastien Bacher ]
  * shell: don't use deprecated properties, avoid runtime warnings

  [ Jian-Ding Chen (timchen119) ]
  * Set higher priority of glxinfo's result then Xorg's log for
    "Details" -> "Overview" -> "Graphics" info in control center. (LP:
    #1417034) (LP: #1417034)

  [ Dan Winship ]
  * network: update for nma-wifi-dialog renaming
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Tue, 03 Feb 2015 12:26:36 +0000

** Changed in: unity-control-center (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  Set higher priority of glxinfo's result then Xorg's log for "Details"
  -> "Overview" -> "Graphics" info in control center.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  In some of OEM's AMD platforms,

  open "System setting"->"Details"->"Graphics" from control center,

  find the Graphics Driver show VESA: XXXXXX strings ,

  not as accurate as what glxinfo -l | grep "OpenGL renderer string"
  shows.

  The "VESA:XXXX" string displayed in "System Settings-->Details->Graphics" was because
  unity-control-center will find the driver information via:

  (1) parse /var/log/Xorg.0.log and find "VESA VBE OEM Product:" String

  (2) if (1) is not found, parse the result of "glxinfo -l" and find
  "OpenGL renderer string", and use this info as the string being shown.

  There're some of AMD's fglrx driver will show "VESA VBE OEM Product:
  XXXXX" string in /var/log/Xorg.0.log,

  I've asked AMD and their reply is that the VESA BIOS message is traced
  by VBEInit (libvbe.so) , which is out of fglrx’s control.

  Curently this "VESA:XXXXX" string instead of the more accurate string
  from glxinfo was being shown in the panel.

  I think Use glxinfo's information (when available) first is more
  accurate.

  Private bugs were filed at:
  https://bugs.launchpad.net/bugs/1369859
  https://bugs.launchpad.net/bugs/1415303

  A merge proposal is submitted at
  https://code.launchpad.net/~timchen119/unity-control-center/unity-
  control-center.lp1417034/+merge/248220

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions