Description of problem: X crashes when moving a window, there's no kernel oops or a traceback in Xorg.0.log. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.6.99-9.20090706.fc12.x86_64 xorg-x11-drv-ati-6.12.2-19.fc12.x86_64 How reproducible: 100% on the given computer Steps to Reproduce: 1. startx 2. Start gnome-terminal 3. Try to move it Actual results: "The 4 arrows" cursor moves about a pixel or two, then crash. Expected results: No crash, window is moved. Additional info: This is 100% crash on a common operation, right after start, so I was shocked a bit. But I have a different system which runs VESA driver and same Xorg, that one works. I'm attaching yum.log.
Created attachment 354262 [details] Xorg.0.log No traceback, X server exits abrubtly.
Created attachment 354263 [details] yum.log I think I caught this over the last update, July 17.
Created attachment 354264 [details] stderr of startx Looks like it's the new pixman, the error log of startx contains: X: pixman-region.c:457: pixman_region_copy: Assertion `pixman_region_selfcheck (src)' failed. And then the server crashes. Can you guys at least restore the text console when you crash?
Same story with pixman-0.5.16-1.fc12 -- crash on the first move.
Can you get a backtrace with gdb from another machine?
Created attachment 354268 [details] stack trace The stack trace is incomplete, because I haven't all needed debuginfos installed. I'll post better one tomorrow.
David, is this with the latest rawhide X server?
There is nothing to triage here. Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
Updated to xorg-x11-server-Xorg-1.6.99-14.20090715.fc12.x86_64. Problem is gone. Notice, pixman was not updated. It must have been a flag day between X server and pixman.
Same here: bug 513001. Issue can be worked around by adding '"AccelMethod" "xaa"' to xorg.conf.