[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Changed in: oem-priority Status: New = Fix Released ** Changed in: oem-priority/trusty Status: New = 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: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in unity-control-center source package in Trusty: Fix Released Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
This bug was fixed in the package unity-control-center - 14.04.3+14.04.20140922-0ubuntu1.1 --- unity-control-center (14.04.3+14.04.20140922-0ubuntu1.1) trusty; urgency=medium [ 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) -- Sebastien Bacher seb...@ubuntu.com Mon, 27 Jul 2015 18:23:16 +0200 ** Changed in: unity-control-center (Ubuntu Trusty) Status: Fix Committed = 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 Status in unity-control-center source package in Trusty: Fix Released Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
I've verified trusty unity-control- center14.04.3+14.04.20140922-0ubuntu1.1 from trusty-proposed archive, verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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 Status in unity-control-center source package in Trusty: Fix Committed Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
Hello Tim, or anyone else affected, Accepted unity-control-center into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unity-control-center/14.04.3+14.04.20140922-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity-control-center (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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 Status in unity-control-center source package in Trusty: Fix Committed Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Branch linked: lp:ubuntu/trusty-proposed/unity-control-center -- 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 Status in unity-control-center source package in Trusty: Fix Committed Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
sponsored to trusty as well, sorry for the delay ** Changed in: unity-control-center (Ubuntu Trusty) Status: New = In Progress ** Changed in: unity-control-center (Ubuntu Trusty) Importance: Undecided = High -- 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 Status in unity-control-center source package in Trusty: In Progress Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Branch linked: lp:~timchen119/unity-control-center/unity-control- center.lp1417034.trusty -- 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 Status in unity-control-center source package in Trusty: New Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Also affects: unity-control-center (Ubuntu Trusty) Importance: Undecided Status: New -- 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 Status in unity-control-center source package in Trusty: New Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: + Trusty (and Utopic) SRU Request: + + [Impact] + + * Set higher priority of glxinfo's result then Xorg's log for Details + - Overview - Graphics info in Unity Control Center. + + [Test Case] + + * System with glxinfo installed (in mesa-utils) will show glxinfo's + result first for Details - Overview - Graphics info in Unity + Control Center. + + * System without glxinfo will still parse Xorg's log for Details - + Overview - Graphics info in Unity Control Center. + + [Regression Potential] + + * Should be minimal, the info showed in glxinfo is more accurate. + + [Original Bug Info] + In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- 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: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
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-jenk...@lists.canonical.com Tue, 03 Feb 2015 12:26:36 + ** 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: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Branch linked: lp:ubuntu/vivid-proposed/unity-control-center -- 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: In Progress Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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. - A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 + Private bugs were filed at: + https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted. ** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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/1369859 https://bugs.launchpad.net/bugs/1415303 - A merge proposal is submitted. + A merge proposal is submitted at https://code.launchpad.net/~timchen119 + /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- 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: New Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- 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: New Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Branch linked: lp:~timchen119/unity-control-center/unity-control- center.lp1417034 -- 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: In Progress Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Changed in: unity-control-center (Ubuntu) Importance: Undecided = High ** Changed in: unity-control-center (Ubuntu) Status: New = In Progress ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) = Tim Chen (timchen119) -- 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: In Progress Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: 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: X 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:X 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
