protonscr

Fedora 20 - Graphic glitch in Metro: Last Light

steamclosed
ValveSoftware/steam-for-linux#3208 · opened 2014-03-15 by NTMan · updated 2014-03-17 · 2 comments · github
NNTMan 2014-03-15 github

Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQcjNiYlNmSERyd0U/edit?usp=sharing

Processor Information:
Vendor: GenuineIntel
CPU Family: 0x6
CPU Model: 0x3c
CPU Stepping: 0x3
CPU Type: 0x0
Speed: 3900 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported

Network Information:
Network Speed:

Operating System Version:
"Fedora release 20 (Heisenbug)" (64 bit)
Kernel Name: Linux
Kernel Version: 3.13.6-200.fc20.x86_64
X Server Vendor: Fedora Project
X Server Release: 11404000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime-release_2014-02-05

Video Card:
Driver: Intel Open Source Technology Center Mesa DRI Intel(R) Haswell Desktop

Driver Version:  3.0 Mesa 10.0.3
OpenGL Version: 3.0
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID:  0x8086
DeviceID:  0x412
Number of Monitors:  1
Number of Logical Video Cards:  1
Primary Display Resolution:  1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20,04" x 11,26"  (22,95" diag)
                                        50,9cm x 28,6cm  (58,3cm diag)
Primary VRAM Not Detected

Sound card:
Audio device: Intel Haswell HDMI

Memory:
RAM: 31123 Mb

Miscellaneous:
UI Language: English
LANG: en_US.utf8
Microphone: Not set
Total Hard Disk Space Available: 2816556 Mb
Largest Free Hard Disk Block: 160809 Mb

Installed software:

Recent Failure Reports:
Thu Mar 13 17:26:59 2014 GMT: file ''/tmp/dumps/crash_20140313225631_1.dmp'', upload no: ''Failure when receiving data from the peer''
Thu Mar 13 18:38:47 2014 GMT: file ''/tmp/dumps/crash_20140314003838_14.dmp'', upload no: ''Failure when receiving data from the peer''

NNTMan 2014-03-15 github

rpm -qa | grep mesa
mesa-libgbm-10.0.3-2.20140206.fc20.i686
mesa-dri-drivers-10.0.3-2.20140206.fc20.i686
mesa-filesystem-10.0.3-2.20140206.fc20.x86_64
mesa-libgbm-10.0.3-2.20140206.fc20.x86_64
mesa-libEGL-10.0.3-2.20140206.fc20.i686
mesa-libglapi-10.0.3-2.20140206.fc20.x86_64
mesa-libGLU-9.0.0-4.fc20.i686
mesa-libwayland-egl-10.0.3-2.20140206.fc20.x86_64
mesa-libglapi-10.0.3-2.20140206.fc20.i686
mesa-libGL-10.0.3-2.20140206.fc20.i686
mesa-filesystem-10.0.3-2.20140206.fc20.i686
mesa-dri-drivers-10.0.3-2.20140206.fc20.x86_64
mesa-libEGL-10.0.3-2.20140206.fc20.x86_64
mesa-libGL-10.0.3-2.20140206.fc20.x86_64
mesa-libGLU-9.0.0-4.fc20.x86_64
mesa-libxatracker-10.0.3-2.20140206.fc20.x86_64

NNTMan 2014-03-17 github

This problem gone after mesa update.

$ rpm -qa | grep mesa
mesa-libgbm-10.0.4-1.20140312.fc20.x86_64
mesa-libEGL-10.0.4-1.20140312.fc20.x86_64
mesa-libglapi-10.0.4-1.20140312.fc20.i686
mesa-libgbm-10.0.4-1.20140312.fc20.i686
mesa-filesystem-10.0.4-1.20140312.fc20.x86_64
mesa-libxatracker-10.0.4-1.20140312.fc20.x86_64
mesa-libGLU-9.0.0-4.fc20.i686
mesa-libGL-10.0.4-1.20140312.fc20.x86_64
mesa-libEGL-10.0.4-1.20140312.fc20.i686
mesa-filesystem-10.0.4-1.20140312.fc20.i686
mesa-dri-drivers-10.0.4-1.20140312.fc20.x86_64
mesa-libwayland-egl-10.0.4-1.20140312.fc20.x86_64
mesa-libGL-10.0.4-1.20140312.fc20.i686
mesa-libGLU-9.0.0-4.fc20.x86_64
mesa-libglapi-10.0.4-1.20140312.fc20.x86_64
mesa-dri-drivers-10.0.4-1.20140312.fc20.i686

Nothing extracted yet.