Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48831 - [xf86-video-intel] Firefox rendering tile mayhem after driver update

Attached to Project: Arch Linux
Opened by Sigalas Alexandros (alxarch) - Thursday, 07 April 2016, 07:28 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 16 April 2016, 18:57 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

After upgrading to the latest (2.99.917+604) version of xf86-video-intel firefox page rendering has many tiling artifacts (see screenshot) on images. I haven't seen issues on other software yet but it's driver related because when I downgraded to 2.99.917+587 image rendering was normal again.

I have a Skylake i7 6600U and it has many issues with screen flickering etc.

Running on 4.6rc2

Additional info:
* package version(s) 2.99.917+604
* config and/or log files etc.

Here is my /etc/X11/xorg.conf.d/20-intel-graphics.conf:

Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "3"
# Option "DRI" "false"
# Option "AccelMethod" "glamor"
EndSection

This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 16 April 2016, 18:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  xf86-video-intel 1:2.99.917+631+gf2a4645-1
Comment by Andreas Radke (AndyRTR) - Thursday, 07 April 2016, 17:48 GMT
Report such regressions upstream and leave the url here...
Comment by John Lindgren (jlindgren) - Thursday, 14 April 2016, 05:13 GMT Comment by John Lindgren (jlindgren) - Saturday, 16 April 2016, 17:32 GMT
I can't speak for the original reporter, but the latest upstream commit (f2a46458a257) fixes the issue for me.

Loading...