Random graphics glitch [nvidia 349.16; 680GTX]

piotrk22 · 2015-05-19 00:26:40

Hello,

I've been experiencing some very weird graphical problems that seem to pop up usually when I'm launching a game or waking my computer from suspend.

Here's how it looks and keeps shifting around and stays distorted:

http://imgur.com/a/OBdEh

I thought this was called screen tearing and tried to the solution for that on the wiki (https://wiki.archlinux.org/index.php/NV … ries_cards).

Unfortunately, that didn't solve the issue. Any help would be much appreciated.

I'm running:
OS: Arch Linux
Kernel: 4.0.2-1-ARCH
GPU: GeForce GTX 680
CPU: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
Driver: NVIDIA 349.16
Desktop environment: KDE Plasma 5 (plasma-desktop-5.3.0-3)

I was able to log into another tty session (ctrl+alt+f2) and was able to start a new X session using `startx`.
Here's some output I was able to get from various commands:

Output from `xrandr -q`:

Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1600x1200     60.00  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
   1920x1080     60.00*+  59.94    29.97    23.97    60.05    60.00  
   1360x768      60.02  
   1280x1024     60.02  
   1280x768      59.87  
   1280x720      60.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x480       59.94  
   640x480       59.95    59.94    59.93  
DP-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1600x1200     60.00  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
DP-1 disconnected (normal left inverted right x axis y axis)

`/var/log/Xorg.0.log` has this message:

[  5204.149] (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0},                                         DVI-D-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"                                                           
[  5204.458] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon                                                                   
[  5204.458] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  5204.458] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  5204.458] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  5204.458] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  5204.458] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  5204.458] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  5204.458] (II) NVIDIA(0):     Config Options in the README.

and then hundreds of the following messages:

[  5204.470] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.470] (**) NVIDIA(0):     device Ancor Communications Inc VE247 (DFP-3) (Using EDID
[  5204.470] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[  5204.502] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.502] (**) NVIDIA(0):     device LG Electronics LG TV (DFP-1) (Using EDID
[  5204.502] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[  5204.510] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.510] (**) NVIDIA(0):     device Ancor Communications Inc VE247 (DFP-0) (Using EDID
[  5204.510] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[  5204.637] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.637] (**) NVIDIA(0):     device Ancor Communications Inc VE247 (DFP-3) (Using EDID
[  5204.637] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[  5204.672] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.672] (**) NVIDIA(0):     device LG Electronics LG TV (DFP-1) (Using EDID
[  5204.672] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[  5204.685] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[  5204.685] (**) NVIDIA(0):     device Ancor Communications Inc VE247 (DFP-0) (Using EDID
[  5204.685] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)

Under `top`, it looks like the `kwin_x11` process is using 100% of one of my CPU cores.

Here's the output of `gdb` on the `kwin_x11` process following the instructions at https://bugs.kde.org/show_bug.cgi?id=340294

https://gist.github.com/anonymous/b785ef896c1a82b6bc80

Are the refresh rates being changed to an incorrect value leading to a corrupted image being displayed?

Any help with resolving this issue would be much appreciated. Thanks!

Malkymder · 2015-05-19 03:01:55

under kwin desktop effects, disable the magic lamp effect "optional, turn off Desktop effects completely"

Sounds weird but try it see if it happens again

See this bug report https://bugs.kde.org/show_bug.cgi?id=339030

Last edited by Malkymder (2015-05-19 03:26:08)

piotrk22 · 2015-05-19 03:35:44

Thanks for the suggestions.

The magic lamp effect was already disabled and disabling all desktop effects doesn't seem to make a difference.

I think I adding the following to ~/.config/kwinrc (as suggested https://bugs.kde.org/show_bug.cgi?id=347360) may have helped a little:

[Compositing]
RefreshRate=60

It seems like whenever this glitch occurs I need to ctrl+alt+f2 and kill the kwin_x11 process and restart it in tty1

Malkymder · 2015-05-19 03:49:46

Do you use plymouth ?

piotrk22 · 2015-05-19 04:02:00

No, I don't use plymouth.

When I had all of the desktop effects disabled I could consistently reproduce the bug after resuming from suspend.

Switching to tty2 would also set off the bug.

Re-enabling the default desktop effects seems to make it a little better.

When I was running kwin_x11 in a terminal, I say the following messages when I tried to load up a game:

kwin_core: User timestamp, final: 'ID: 41943051 ;WMCLASS: "ck2" : "ck2" ;Caption: "Crusader Kings II" ' : 1830997
kwin_core: Activation: No client active, allowing
kwin_core: screens:  3 desktops:  3
kwin_core: Done.
kwin_core: screens:  3 desktops:  3
kwin_core: Done.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2315, resource id: 41943051, major code: 42 (SetInputFocus), minor code: 0
kwin_core: Initializing OpenGL compositing
kwin_core: Choosing GLXFBConfig 0x115 X visual 0x2b depth 24 RGBA 8:8:8:0 ZS 0:0
OpenGL vendor string:                   NVIDIA Corporation
OpenGL renderer string:                 GeForce GTX 680/PCIe/SSE2
OpenGL version string:                  3.1.0 NVIDIA 349.16
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver:                                 NVIDIA
Driver version:                         349.16
GPU class:                              Unknown
OpenGL version:                         3.1
GLSL version:                           1.40
X server version:                       1.17.1
Linux kernel version:                   4.0.2
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
Direct rendering: true 

kwin_core: Initializing fences for synchronization with the X command stream
kwin_core: Color correction: false
kwin_core: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use SYSTEM HEAP memory as the source for buffer object operations.
kwin_core: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast).
kwin_core: OpenGL 2 compositing successfully initialized
kwin_core: Vertical Refresh rate  60 Hz
kf5.kservice.sycoca: Trying to open ksycoca from "/home/peter/.cache/ksycoca5"
Using FBConfig 0x1a8 for visual 0xc4
kwin_core: 0x20071: Buffer detailed info: Buffer object 2 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
Using FBConfig 0x119 for visual 0x2d
Using FBConfig 0x119 for visual 0x2d
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2626, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2627, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2628, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2629, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2630, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2631, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2632, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2633, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2636, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2637, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2638, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2639, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2640, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2641, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2642, resource id: 0, major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2643, resource id: 0, major code: 14 (GetGeometry), minor code: 0
kwin_core: screens:  3 desktops:  3
kwin_core: Done.
Using FBConfig 0x1a8 for visual 0xc4
Using FBConfig 0x119 for visual 0x2d
kwin_core: Successfully loaded built-in effect:  "blur"
kwin_core: Successfully loaded built-in effect:  "contrast"
kwin_core: Session path: "/org/freedesktop/login1/session/c2"
kwin_core: Successfully loaded built-in effect:  "dashboard"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_dialogparent"
kwin_core: Successfully loaded built-in effect:  "desktopgrid"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_fade"
kwin_core: Successfully loaded built-in effect:  "highlightwindow"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_windowaperture"
kwin_core: Successfully loaded built-in effect:  "kscreen"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_maximize"
kwin_core: Successfully loaded built-in effect:  "logout"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_login"
kwin_core: Successfully loaded built-in effect:  "presentwindows"
kwin_core: Successfully loaded scripted effect:  "kwin4_effect_translucency"
kwin_core: Successfully loaded built-in effect:  "screenedge"
kwin_core: Successfully loaded built-in effect:  "screenshot"
kwin_core: Successfully loaded built-in effect:  "slide"
kwin_core: Successfully loaded built-in effect:  "slidingpopups"
kwin_core: Successfully loaded built-in effect:  "startupfeedback"
kwin_core: Successfully loaded built-in effect:  "zoom"
Segmentation fault (core dumped)
[peter@peter_arch ~]$ kwin_core: Raising, compared: 1835493 : 1820922 : true 

kwin_core: Raising, compared: 1835493 : 1820922 : true 

kwin_core: Raising, compared: 1835493 : 1820922 : true 

kwin_core: Raising, compared: 1835493 : 1820922 : true 

kwin_core: screens:  3 desktops:  3
kwin_core: Done.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 7580, resource id: 41943051, major code: 15 (QueryTree), minor code: 0
kwin_core: Triple buffering detection: "NOT available"  - Mean block time: 9.9669 ms
kwin_core: 
It seems you are using the nvidia driver without triple buffering
You must export __GL_YIELD="USLEEP" to prevent large CPU overhead on synced swaps
Preferably, enable the TripleBuffer Option in the xorg.conf Device
For this reason, the tearing prevention has been disabled.
See https://bugs.kde.org/show_bug.cgi?id=322060

It looks like kwin_x11 segfaults when the game is launched.

The following comment from the bug report you posted describes perfectly the bug I'm experiencing https://bugs.kde.org/show_bug.cgi?id=339030#c2
Though I don't just experience the bug when resuming from suspend.

Malkymder · 2015-05-19 04:22:32

when you get the corrupted screen if you toggle Desktop effects off/on with Alt+Shift+F12 does this fix your display without killing the kwin.

Could try another NVIDIA driver versions ... aside from opening a ticket with upstream i'm out of ideas

Another idea would be to use a different compositor like xrender or a different OpenGL version with Kwin

Last edited by Malkymder (2015-05-19 04:24:39)

smirky · 2015-05-19 06:17:03

I have the same issue with my NVIDIA 450 GTS and I think it's not really specific of the NVIDIA GPU model. My workaround for this was always toggling the effects. The most easy way to reproduce it is to switch to another tty and back to plasma/kde. Doesn't happen every time but it sure does happen frequently. It's an ancient bug.

Last edited by smirky (2015-05-19 06:17:20)

Svenstaro · 2015-05-19 09:23:32

Update your driver.

Roken · 2015-05-19 20:06:37

Latest LightDM screws it up - if that's what you use, drop back a version

Buddlespit · 2015-05-19 20:18:34

Svenstaro wrote:

Update your driver.

That doesn't fix it. It appears to be a kwin/plasma5 issue. I can make it happen with your new driver, with your old driver and with the nouveau driver. Changing tty or applying a change in nvidia-settings usually sets it off. I just disable/enable compositing (alt+shift+f12) to fix it.

To add insult to injury, about 1 in 8 boots will make my dual monitors mirror. So I have to go into nvidia-settings, change the monitor settings to two different monitors (or one big 3200x900, however you want to look at it), disable compositing, re-enable compositing and keep my fingers crossed on the next reboot.

Malkymder · 2015-05-19 20:41:28

post your /etc/default/grub ?

piotrk22 · 2015-05-20 04:11:01

@Malkymder - I'll try using a different compositor or different version of OpenGL like you suggested

@Svenstaro - I updated to the 352.09 NVIDIA driver and I still experiece the same issues like @Buddlespit. I'll have to try using the alt+shift+f12 disable/enable compositing fix next time I encounter the bug. I can't consistently reproduce either and seems to pop up randomly.

@Roken - no I don't have LightDM installed.

@Buddlespit - It definitely looks like a KWin/KDE issue. Have you tried "Save to X Configuration File" under nvidia-settings to maybe prevent your settings from changing?

@Malkymder - here's my /etc/default/grub:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

#GRUB_SAVEDEFAULT="true"

Thanks for the suggestions guys! I'm just glad that I can easily recover from this bug without rebooting.

Buddlespit · 2015-05-20 11:03:49

piotrk22 wrote:

@Buddlespit - It definitely looks like a KWin/KDE issue. Have you tried "Save to X Configuration File" under nvidia-settings to maybe prevent your settings from changing?

Yeah, I've tried /etc/X11/xorg.conf.d/20-nvidia.conf and just a plain ol' /etc/X11/xorg.conf. I've let nvidia handle it and I've used my own configs. I've stood on one leg, waving a feather in an opposite hand while chanting 'Nam-myoho-renge-kyo'. This didn't start until kwin was updated about a month, maybe a month and a half ago and it only happens in maybe one-in-eight boots. I really don't reboot unless an update forces me to.

piotrk22 · 2015-05-23 23:54:02

Just an update, I "solved" the issue by uninstalling KDE and Plasma and installing XFCE instead.

It doesn't look quite as nice, but I haven't had an issue yet.

arneko · 2015-05-27 18:38:29

Roken wrote:

Latest LightDM screws it up - if that's what you use, drop back a version

My glitch looked different than OP's, but that (changing from lightdm->gdm) did the trick for me, thanks!

Roken · 2015-06-03 21:29:57

You don't need to switch. Downgrading LightDM, or better, re-doing the lightdm config (it's changed a lot) would do it.

Arch Linux

#1 2015-05-19 00:26:40

Random graphics glitch [nvidia 349.16; 680GTX]

#2 2015-05-19 03:01:55

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#3 2015-05-19 03:35:44

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#4 2015-05-19 03:49:46

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#5 2015-05-19 04:02:00

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#6 2015-05-19 04:22:32

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#7 2015-05-19 06:17:03

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#8 2015-05-19 09:23:32

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#9 2015-05-19 20:06:37

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#10 2015-05-19 20:18:34

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#11 2015-05-19 20:41:28

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#12 2015-05-20 04:11:01

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#13 2015-05-20 11:03:49

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#14 2015-05-23 23:54:02

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#15 2015-05-27 18:38:29

Re: Random graphics glitch [nvidia 349.16; 680GTX]

#16 2015-06-03 21:29:57

Re: Random graphics glitch [nvidia 349.16; 680GTX]

Board footer