337.12 beta + kde 4.11 fail

After running the new beta for about 24 hours, a random mouse gesture that was somewhat spastic crashed, partly, kde. I still had mouse movement, but nothing was active on the desktop, couldn’t click anything, and hidden taskbars didn’t appear on hover. Never seen this particular issue so have to assume it may be related to the new beta plus kde.

inxi -bxxx
System:    Host: yawn Kernel: 3.13-9.dmz.1-liquorix-686 i686 (32 bit gcc: 4.8.2) 
           Desktop: KDE 4.11.3 (Qt 4.8.6) info: plasma-desktop dm: kdm Distro: sidux-20070102-d:1 
Machine:   Mobo: ASRock model: A770DE+ Bios: American Megatrends v: P1.70 date: 09/07/2010
CPU:       Dual core AMD Athlon 64 X2 5000+ (-MCP-) clocked at 1800 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 chip-ID: 10de:0a65
           Display Server: X.Org 1.14.4 driver: nvidia Resolution: 1280x1024@75.0hz, 1280x1024@60.0hz
           GLX Renderer: GeForce 210/PCIe/SSE2/3DNOW! GLX Version: 3.3.0 NVIDIA 337.12 Direct Rendering: Yes
Network:   Card: Intel 82574L Gigabit Network Connection
           driver: e1000e v: 2.3.2-k port: c800 bus-ID: 01:00.0 chip-ID: 8086:10d3
Drives:    HDD Total Size: 810.2GB (76.2% used) 
Info:      Processes: 273 Uptime: 4:17 Memory: 3769.4/6078.7MB 
           Init: SysVinit v: 2.88 runlevel: 3 default: 3 Gcc sys: 4.8.2 alt: 4.0/4.2/4.4/4.5/4.6/4.7 
           Client: Shell (bash 4.2.451 running in konsole) inxi: 2.1.20

Attached bug gz file, can you fix these forums to make attaching files easier on first thread posting? I cant’ see anyway to do it except first creating the posting, then using the attach icon, that seems kind of poorly done.

The gz was generated out of X while the failure was active.
nvidia-bug-report-337.12-kde-locks-up.gz (79.7 KB)

I’m reporting the same issue, but my bug report was generated outside of the crash window (after X was restarted).

System:    Host: damentz64 Kernel: 3.13-9.dmz.1-liquorix-amd64 x86_64 (64 bit gcc: 4.8.2) 
           Desktop: KDE 4.12.4 (Qt 4.8.6) info: plasma-desktop dm: kdm 
           Distro: siduction 13.1.0 Firestarter - kde - (201305211844) 
Machine:   Mobo: System76 model: Bonobo Extreme v: bonx6 Bios: American Megatrends v: 4.6.5 date: 11/13/2012
CPU:       Quad core Intel Core i7-3630QM CPU (-HT-MCP-) clocked at 1200 MHz
Graphics:  Card: NVIDIA GK104M [GeForce GTX 670MX] bus-ID: 01:00.0 chip-ID: 10de:11a1
           Display Server: X.Org driver: nvidia Resolution: 1920x1080@60.0hz, 1920x1080@60.0hz
           GLX Renderer: GeForce GTX 670MX/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 337.12 Direct Rendering: Yes
Network:   Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter
           driver: ath9k bus-ID: 05:00.0 chip-ID: 168c:0032
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 04:00.2 chip-ID: 10ec:8168
Drives:    HDD Total Size: 3500.7GB (31.3% used) 
Info:      Processes: 274 Uptime: 18:00 Memory: 1821.8/7950.0MB 
           Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 4.8.2 alt: 4.6/4.7 
           Client: Shell (bash 4.3.81 running in konsole) inxi: 2.1.20

Also, not sure if this was related, but chrome stopped repainting with two windows open, one playing a video from youtube, the others just regular pages.
nvidia-bug-report.log.gz (192 KB)

Just as an update, I have not managed to crash the desktop again, though I think I am noticing some lags in painting and other subtle behaviors, but it’s hard to really know for sure. But the bug in my case did not repeat yet, probably because I did not repeat the spastic mouse movement. I believe steven-liquorix’s however was more severe, and made the beta non usable for him.


I run 337.12 with KDE 4.11.5 just fine on OpenSUSE 13.1 with a Geforce 210M mobile chip, 64 Bit Linux.