Buggy video driver or compositor (just run gnome-box with Windows 10 and steam) Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQdjBMdUZnRzJiTFU/view?usp=sharing $ uname -r 4.0.0-1.fc22.x86_64+debug $ lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41) 05:00.0 Audio device: Creative Labs SB Recon3D (rev 01)
Please attach Xorg.0.log so I have a rough idea of the versions involved.
Created attachment 115229 [details] journalctl -e _COMM=gdm-x-session --no-pager > Xorg.log
Looks like a Present bug. Can you test, either echo -e 'Section "Device"\n\tIdentifier "igfx"\n\tOption "DRI" "2"\nEndSection> /etc/X11/xorg.conf.d/20-dri2.conf or echo LIBGL_DISABLE_DRI3=1 > /etc/environment #untested You can confirm dri3 being enabled/disabled with xf86-video-intel/tools/dri3info
Chris, I don't understand where located dri3info. After applying echo LIBGL_DISABLE_DRI3=1 > /etc/environment #untested needed reboot?
/etc/environment is supposed to be evaluated at login time, but I wonder if daemons use it at all? Reboot to be sure. dri3info is part of xf86-video-intel: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/tools/dri3info.c (and now includes standalone compilation instructions!)
1.I can confirm that issue still present also after DRI3 disabling. Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQVEl5WTdycW9tdGM/view?usp=sharing 2. echo LIBGL_DISABLE_DRI3=1 > /etc/environment #untested This is not disable DRI3 [mikhail@localhost ~]$ ./dri3info Display ':0' Connected to DRI3, using fd 4 which matches /dev/dri/renderD128, driver i915 Primary refresh rate: 60/1 (60.0Hz) echo LIBGL_DISABLE_DRI3=1 > /etc/environment #untested ----- reboot ----- [mikhail@localhost ~]$ ./dri3info Display ':0' Connected to DRI3, using fd 4 which matches /dev/dri/renderD128, driver i915 Primary refresh rate: 60/1 (60.0Hz) echo -e 'Section "Device"\n\tIdentifier "igfx"\n\tOption "DRI" "2"\nEndSection'> /etc/X11/xorg.conf.d/20-dri2.conf ----- reboot ----- [root@localhost ~]# /home/mikhail/dri3info Display ':0' Unable to connect to DRI3 Primary refresh rate: 60/1 (60.0Hz)
Hi Chris Wilson, might you follow the this bug from the last comment. Thanks
Mikhail, is this still an issue with latest kernel and userspace?
(In reply to Jani Nikula from comment #8) > Mikhail, is this still an issue with latest kernel and userspace? yes $ uname -r 4.5.2-302.fc24.x86_64 $ rpm -qa | grep intel xorg-x11-drv-intel-2.99.917-22.20160119.fc24.x86_64 $ rpm -qa | grep mesa mesa-libGLU-9.0.0-10.fc24.x86_64 mesa-libOSMesa-11.2.0-1.20160414.fc24.i686 mesa-libOSMesa-11.2.0-1.20160414.fc24.x86_64 mesa-dri-drivers-11.2.0-1.20160414.fc24.i686 mesa-filesystem-11.2.0-1.20160414.fc24.x86_64 mesa-dri-drivers-11.2.0-1.20160414.fc24.x86_64 mesa-libxatracker-11.2.0-1.20160414.fc24.x86_64 mesa-libEGL-11.2.0-1.20160414.fc24.i686 mesa-libEGL-11.2.0-1.20160414.fc24.x86_64 mesa-libOpenCL-11.2.0-1.20160414.fc24.x86_64 mesa-libglapi-11.2.0-1.20160414.fc24.i686 mesa-libgbm-11.2.0-1.20160414.fc24.x86_64 mesa-libOpenCL-11.2.0-1.20160414.fc24.i686 mesa-libGL-11.2.0-1.20160414.fc24.x86_64 mesa-filesystem-11.2.0-1.20160414.fc24.i686 mesa-libgbm-11.2.0-1.20160414.fc24.i686 mesa-libwayland-egl-11.2.0-1.20160414.fc24.x86_64 mesa-debuginfo-11.2.0-1.20160414.fc24.x86_64 mesa-libGLU-9.0.0-10.fc24.i686 mesa-libglapi-11.2.0-1.20160414.fc24.x86_64 mesa-libGL-11.2.0-1.20160414.fc24.i686
Mikhail - sorry about this looong delay until getting back to you. The last retest is from a year back, so please restest with the latest components (kernel and userspace). If problem still persist then mark status REOPENED, otherwise as RESOLVED.
Closing bug as invalid due to lack of activity, if the problem still persist with latest configuration please open a new bug
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.