Comment 37 for bug 71913

Just a "me too" here. I'm also using Kubunto with Compiz, but didn't try switching Compiz off yet.

I don't have a clue what's going on here, but it seems like it has something to do with the CPU or I/O load. Currently I've got a RAID resync running and a large rsync operation and I've encountered four crashes during these operations. Yesterday I had no crashes at all with my computer being almost idle.

I've got two almost identical backtraces from my X-logs:
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
> 1: [0xffffe420]
> 2: /usr/bin/X [0x817e39d]
> 3: /usr/bin/X [0x817a9ef]
> 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
> 5: /usr/bin/X [0x8168f19]
> 6: /usr/bin/X [0x8164315]
> 7: /usr/bin/X [0x815754e]
> 8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
> 9: /usr/bin/X(main+0x495) [0x8076f05]
> 10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d5e050]
> 11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]
>
> Fatal server error:
> Caught signal 11. Server aborting

And:
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
> 1: [0xffffe420]
> 2: /usr/bin/X [0x817e39d]
> 3: /usr/bin/X [0x817a9ef]
> 4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
> 5: /usr/bin/X [0x8168f19]
> 6: /usr/bin/X [0x8164315]
> 7: /usr/bin/X [0x815754e]
> 8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
> 9: /usr/bin/X(main+0x495) [0x8076f05]
> 10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7df9050]
> 11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]
>
> Fatal server error:
> Caught signal 11. Server aborting

I'm using the latest Kubuntu (Gutsy Gibbon) and the latest NVidia drivers (v100.14.23). Apart from the NVidia-drivers, all software on my system is installed from packages.