Xorg does not utilize the 3D graphics acceleration capabilities of my device

[Nicholas Christian Langkjær Ipsen]

Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Oct 12 09:57:12 2016
DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: yakkety
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd]
InstallationDate: Installed on 2016-01-21 (264 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc.
 Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. T300CHI
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)
dmi.bios.date: 03/18/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T300CHI.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T300CHI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: T300CHI
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Wed Oct 12 09:59:28 2016
xserver.configfile: default
xserver.errors:
 Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory
 modeset: Failed to load module "glamoregl" (loader failed, 7)
 modeset(0): Failed to load glamor module.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

[Timo Aaltonen (tjaalton)]

you've somehow managed to uninstall libgbm1, reinstall it and things should be fine

[Nicholas Christian Langkjær Ipsen (ncli)]

No, I have not. Libgbm1 is installed, as well as all other packages included in the ubuntu-desktop meta-package.

[Timo Aaltonen (tjaalton)]

your logfile disagrees

[ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory

[Nicholas Christian Langkjær Ipsen (ncli)]

The package is installed, but the file is not there.

On 12 Oct 2016 13:50, "Timo Aaltonen" <email address hidden> wrote:

> your logfile disagrees
>
> [ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so:
> libgbm.so.1: cannot open shared object file: No such file or directory
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1632593
>
> Title:
> Xorg does not utilize the 3D graphics acceleration capabilities of my
> device
>
> Status in xorg package in Ubuntu:
> New
>
> Bug description:
> Everything worked fine in 16.04. I then upgraded to 16.10 a bit early
> to see if I could find any bugs, and immediately noticed that Unity
> was running in low-graphics mode, and YouTube chugs noticably.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: xorg 1:7.7+13ubuntu4
> ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
> Uname: Linux 4.4.0-34-generic x86_64
> .tmp.unity_support_test.1:
>
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
> CompositorRunning: compiz
> CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
> CompositorUnredirectFSW: true
> CurrentDesktop: Unity
> Date: Wed Oct 12 09:57:12 2016
> DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript:
> './xorg_fix_proprietary.py'
> DistroCodename: yakkety
> DistroVariant: ubuntu
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00
> [VGA controller])
> Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd]
> InstallationDate: Installed on 2016-01-21 (264 days ago)
> InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64
> (20150805)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc.
> Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp.
> Bus 001 Device 002: ID 8087:0a2a Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: ASUSTeK COMPUTER INC. T300CHI
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/zsh
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed
> root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
> Renderer: Software
> SourcePackage: xorg
> Symptom: display
> UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)
> dmi.bios.date: 03/18/2015
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: T300CHI.206
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: T300CHI
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: ATN12345678901234567
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:
> svnASUSTeKCOMPUTERINC.:pn...

[Timo Aaltonen (tjaalton)]

and how do you verify it's installed? run 'apt-cache policy libgbm1'

[Nicholas Christian Langkjær Ipsen (ncli)]

I reinstalled the package, no dice. I then looked around for it, and found that it had been renamed to old.libgbm1.so, along with the file it linked to. I renamed both, removing the "old.", and now 3D works. It's definitely still a bug though.

[Nicholas Christian Langkjær Ipsen (ncli)]

Can someone please change this to be about the package containing the do-release-upgrade command?

[Timo Aaltonen (tjaalton)]

why do you think the bug is there?

[Nicholas Christian Langkjær Ipsen (ncli)]

Well, it's certainly a problem which appeared after I did the upgrade. There were no issues before this point.

[Timo Aaltonen (tjaalton)]

Your system was crippled already when it was on 16.04. You probably still have libgbm1-lts-wily or such installed which diverted the lib, because on 14.04.x the original had to be used.

xenial-updates has had libgbm1-lts-$foo transitional packages since early august, see bug #1573190

[Timo Aaltonen (tjaalton)]

the reason why 16.04 worked was that it used the intel X driver which didn't need libgbm1

[Timo Aaltonen (tjaalton)]

you used 14.04.3 media to install the system, so check 'apt-cache policy libgbm1-lts-vivid'

[Nicholas Christian Langkjær Ipsen (ncli)]

% apt-cache policy libgbm1-lts-vivid
N: Unable to locate package libgbm1-lts-vivid

2016-10-12 23:51 GMT+02:00 Timo Aaltonen <email address hidden>:

> apt-cache policy
> libgbm1-lts-vivid
>

[Timo Aaltonen (tjaalton)]

You've manually removed it then, before it got the update for #1572855 which would've un-diverted the file. There's no other way to explain it..