Bug 1392171 - Garbled graphics in Firefox with Intel graphics and version 4.9 Linux kernel
Summary: Garbled graphics in Firefox with Intel graphics and version 4.9 Linux kernel
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-05 14:34 UTC by Bill Gianopoulos
Modified: 2016-11-16 12:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-16 12:08:17 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot showing the issue (638.33 KB, image/png)
2016-11-05 14:34 UTC, Bill Gianopoulos
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 98402 0 None None None 2016-11-16 12:07:26 UTC

Description Bill Gianopoulos 2016-11-05 14:34:55 UTC
Created attachment 1217566 [details]
Screenshot showing the issue

Under rawhide and a Gnome session under Wayland, the Firefox browser displays garbage with repeated tiles in the Firefox Window.

This does not occur under fedora25 using the same Firefox binary.

This also does not occur under an Xorg Gnome session.

I can only reproduce this on a system with Intel graphics.  AMD graphics systems do not exhibit the issue.

The easiest way to reproduce is to launch Firefox and display your Facebook home page and Maximize and un-maximize the Firefox witdow several times.

Oddly repeatedly hitting the Alt key on the keyboard will eventually fix the display.

Comment 1 Bill Gianopoulos 2016-11-05 15:10:58 UTC
It is no longer clear that this is confined to wayland sessions only.  Doing this under an Xorg session just resulted in a Gnome session crash which is similar to what happens if I do this under a Wayland session using Google Chrome.

It is still true that this does not happen with AMD graphics or under the fedora 25 pre-release with the latest updates applied.

Comment 2 Bill Gianopoulos 2016-11-05 18:33:45 UTC
I also just got a similar garbled screen using Xorg.

Comment 3 Bill Gianopoulos 2016-11-07 14:17:44 UTC
I installed kernel-0:4.8.4-301.fc25.x86_64 on my fedora 26 rawhide system and running that kernel I have, so far, not seen the issue.

Comment 4 Bill Gianopoulos 2016-11-07 15:29:38 UTC
I also can not duplicate the issue using the current fedora26 kernel if I set WaylandEnable=false in /etc/gdm/.custom.conf and run an Xorg Gnome session.

Comment 5 Bill Gianopoulos 2016-11-07 15:31:16 UTC
Here is the output from lshw -class display:

  *-display                 
       description: VGA compatible controller
       product: 2nd Generation Core Processor Family Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:27 memory:fe000000-fe3fffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff

Comment 6 Bill Gianopoulos 2016-11-07 15:51:56 UTC
I should have included the section on the system itself:

rawhide.wg9s.com
    description: Desktop Computer
    product: 1761E4U (To be filled by O.E.M.)
    vendor: LENOVO
    version: ThinkCentre M71z
    serial: MJXCFPN
    width: 64 bits
    capabilities: smbios-2.6 dmi-2.6 smp vsyscall32
    configuration: administrator_password=disabled boot=normal chassis=desktop f
amily=To be filled by O.E.M. keyboard_password=enabled power-on_password=disable
d sku=To be filled by O.E.M. uuid=1C9085CF-1FBB-8653-24CA-867F211C86AB

Comment 7 Bill Gianopoulos 2016-11-10 20:20:12 UTC
Despite my previous comments.  Everything I said about using Wayland in less places perhaps made it less likely to encounter this issue but does not prevent it's occurrence.  The only thing I have tried that seems to resolve this issue is reverting to a version 4.8 kernel.

Comment 8 Bill Gianopoulos 2016-11-15 22:55:26 UTC
This seems better with kernel version 4.9.0-0.rc5.git0.1.fc26.x86_64.  Were there Intel graphics changes between 4.9.0-0.rc4.git3.1.fc26.x86_64 and 4.9.0-0.rc5.git0.1.fc26.x86_64?


Note You need to log in before you can comment on or make changes to this bug.