LIBGL_DRI3_DISABLE=1 not needed anymore (?)

Bug #1722086 reported by Mikhail Novosyolov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

From /usr/bin/chromium-browser:
# Work around crbug.com/415681
lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1

As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev]
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Sun Oct 8 18:41:30 2017
InstallationDate: Installed on 2017-09-08 (29 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
SourcePackage: chromium-browser
ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.chromium-browser: [deleted]

Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :
Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Cherrytrail)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.2.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

I run Chromium with custom flags, from chrome://gpu:

/usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version --enable-pinch --ignore-gpu-blacklist --enable-experimental-canvas-features --enable-accelerated-2d-canvas --force-display-list-2d-canvas --force-gpu-rasterization --enable-fast-unload --enable-accelerated-vpx-decode --enable-tcp-fastopen --javascript-harmony --enable-checker-imaging --v8-cache-options=code --v8-cache-strategies-for-cache-storage=aggressive --enable-zero-copy --ui-enable-zero-copy --enable-native-gpu-memory-buffers --enable-webgl-image-chromium --flag-switches-begin --enable-accelerated-mjpeg-decode --enable-accelerated-video --force-gpu-rasterization --use-simple-cache-backend=on --enable-tcp-fastopen --enable-zero-copy --ignore-gpu-blacklist --v8-cache-options=code --v8-cache-strategies-for-cache-storage=aggressive --enable-features=SharedArrayBuffer --flag-switches-end

Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

I've ran https://web.bsemark.com benchmark with and without LIBGL_DRI3_DISABLE=1, and thr results are the same
https://web.basemark.com/result/?4HOntFuD
https://web.basemark.com/result/?4HOoWD6P

Revision history for this message
Olivier Tilloy (osomon) wrote :

This is not in the official packages from the ubuntu archive.
Please report the issue at https://github.com/saiarcot895/chromium-ubuntu-build/issues. Thanks!

Changed in chromium-browser (Ubuntu):
status: New → Invalid
Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

Done. https://github.com/saiarcot895/chromium-ubuntu-build/issues/24
(I thought that you package the PPA...)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.