Intel P530 graphics (default SNA acceleration) producing undesirable artifacts on all UI elements
Reported by
synth...@gmail.com,
Jul 5 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome in Arch Linux with Intel P530 graphics. 2. Browse websites and observe frequent artifacts on the screen similar to attachment. What is the expected behavior? No artifacts. What went wrong? Since what feels like two weeks ago, Chromium has been displaying graphics like this about 1/5 of the time something loads. Oddly enough, if I hover or a link or something, the artifacting goes away. Chromium's menus do this as well. And this is a little strange, but when taking a screenshot with scrot, the graphics clear right up prior to taking the screenshot (hence the attached potato cam of my screen; it gets the point across). Slack also has the same issue, but I believe that Slack uses Electron for its UI, which uses the Chromium engine, too. This is on a Lenovo P50 laptop with Optimus graphics, although I'm not using optirun (to utilize the Nvidia card) with Chromium, so this shouldn't matter. I'm also using no Xorg configuration, so everything should be the defaults. Here are the graphics cards I'm running: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics P530 (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev ff) Here's some package versions and what not: linux 4.11.7-1 chromium 59.0.3071.115-1 xf86-video-intel 1:2.99.917+777+g6babcf15-1 nvidia 381.22-3 xorg-server 1.19.3-2 Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: Arch Linux Flash Version: n/a
,
Jul 6 2017
Just found a workaround thanks to a kind stranger! Chromium seems to want to use the Nvidia card by default for some reason, needless to say, outside of Optimus. By passing these flags to chromium on the CLI, I can force it to switch to my Intel card: chromium --gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x191d The vendor and device IDs are found in the GPU1 row in chrome://gpu. I also found that these settings seem to persist when ran once. I imagine the real long-term fix would be to properly detect which graphics card is in use. This would probably fix Slack as well, since it uses the Chromium engine and also exhibits the artifacts displayed in the attached tC4aFgE.jpg.
,
Jul 7 2017
Unable to test the issue as we don't have Arch Linux with Intel P530 graphics machine here with India team. Hence requesting MTV team for further triage of the issue. Thanks!!
,
Jul 9
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by synth...@gmail.com
, Jul 5 2017