Version-Release number of selected component: xorg-x11-server-Xorg-1.12.3-2.fc17 Additional info: libreport version: 2.0.15 abrt_version: 2.0.14 kernel: 3.5.5-1.fc17.x86_64 backtrace: :0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x4652d6] :1: /usr/bin/Xorg (0x400000+0x47f32) [0x447f32] :2: /usr/bin/Xorg (xf86PostMotionEvent+0xd0) [0x4900a0] :3: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f2630505000+0x5085) [0x7f263050a085] :4: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f2630505000+0x6fa4) [0x7f263050bfa4] :5: /usr/bin/Xorg (0x400000+0x807b7) [0x4807b7] :6: /usr/bin/Xorg (0x400000+0xa4ab0) [0x4a4ab0] :7: /lib64/libpthread.so.0 (0x3a70e00000+0xefe0) [0x3a70e0efe0] :8: /lib64/libc.so.6 (ioctl+0x7) [0x3a702ea2f7] :9: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x3a88c035f8] :10: /lib64/libdrm.so.2 (drmCommandWriteRead+0x1c) [0x3a88c0586c] :11: /lib64/libdrm_radeon.so.1 (0x7f26336ff000+0x1e89) [0x7f2633700e89] :12: /lib64/libdrm_radeon.so.1 (0x7f26336ff000+0x20b4) [0x7f26337010b4] :13: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f2633941000+0xacb4a) [0x7f26339edb4a] :14: /usr/lib64/xorg/modules/libexa.so (0x7f2632ed6000+0xb007) [0x7f2632ee1007] :15: /usr/bin/Xorg (0x400000+0x1604b3) [0x5604b3] :16: /usr/bin/Xorg (0x400000+0xc9d80) [0x4c9d80] :17: /usr/bin/Xorg (0x400000+0xfa90a) [0x4fa90a] :18: /usr/bin/Xorg (0x400000+0x3447a) [0x43447a] :19: /usr/bin/Xorg (0x400000+0x23485) [0x423485] :20: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3a70221735] :21: /usr/bin/Xorg (0x400000+0x2375d) [0x42375d]
Created attachment 623374 [details] File: usr_share_xorg_conf_d.tar.gz
Created attachment 623375 [details] File: Xorg.0.log
Created attachment 623376 [details] File: etc_X11_xorg_conf_d.tar.gz
display becomes flooded with random colourful pixels, able to move the mouse pointer and see a square sample of the random pixels move along with it :S . probably a bug in gallium3d driver support for ati4570 cards. Package: xorg-x11-server-Xorg-1.12.3-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
*** This bug has been marked as a duplicate of bug 861577 ***