Issue metadata
Sign in to add a comment
|
fedora linux opengl texture problem in software rendering
Reported by
tero.pul...@gmail.com,
Jun 15 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Steps to reproduce the problem: 1. chrome://flags put "override software rendering list" to disabled. i.e. make it use software rendering 2. go to http://meshpage.org/mesh.php?id=GVILK@907 to see 3d scene 3. examine the result What is the expected behavior? two different kinds of textures, one chessboard and another is mandelbrot, rendered in cubes. What went wrong? it only shows the chessboard texture, but fails to show the mandelbrot texture. The mandelbrot cubes have turned to chessboard textures. It picked the wrong texture. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: 10.0 Flash Version: Only happens in fedora linux, software rendered version. Works fine if hardware acceleration is used.
,
Jun 18 2018
Unable to reproduce the issue on chrome reported version 67.0.3396.87 using Ubuntu 14.04, as mentioned in comment#0 by the reporter as the issue only happens on Fedora Linux, ET team doesn't have Fedora Linux to test, forwarding it to Inhouse team for further triaging it, hence adding TE-NeedsTriageFromHYD label. Thanks!
,
Jun 19 2018
Unable to reproduce this issue on Fedora 24 with chrome #67.0.3396.87 as per steps mentioned in the comment #0 tero.pulkkinen.9@ Could you please re-try the same scenario on clean profile with no apps & extensions and let us know your observations
,
Jun 20 2018
Submitter: "override software rendering list" does not do what you think it does. It *disables* the fallback to software rendering in the case that a driver bug workaround would forbid the use of hardware-accelerated OpenGL. The bug template asked for the contents of about:gpu from your system. Please provide that next time. After testing further, this is a duplicate of Issue 852537 . Submitter, starting Chrome from the command line with the flag "--disable-gpu" will work around this bug and have the behavior you intended. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Jun 17 2018