Bug 512551

Summary: Crash at moving a window
Product: [Fedora] Fedora Reporter: Pete Zaitcev <zaitcev>
Component: pixmanAssignee: Adam Jackson <ajax>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: ajax, jfrieben, mcepl, mcepl, sandmann, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-20 16:43:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg.0.log
none
yum.log
none
stderr of startx
none
stack trace none

Description Pete Zaitcev 2009-07-19 01:05:18 UTC
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.

Comment 1 Pete Zaitcev 2009-07-19 01:06:42 UTC
Created attachment 354262 [details]
Xorg.0.log

No traceback, X server exits abrubtly.

Comment 2 Pete Zaitcev 2009-07-19 01:08:30 UTC
Created attachment 354263 [details]
yum.log

I think I caught this over the last update, July 17.

Comment 3 Pete Zaitcev 2009-07-19 01:11:00 UTC
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?

Comment 4 Pete Zaitcev 2009-07-19 01:34:36 UTC
Same story with pixman-0.5.16-1.fc12 -- crash on the first move.

Comment 5 Søren Sandmann Pedersen 2009-07-19 04:00:03 UTC
Can you get a backtrace with gdb from another machine?

Comment 6 David Tardon 2009-07-19 05:33:13 UTC
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.

Comment 7 Søren Sandmann Pedersen 2009-07-19 16:14:15 UTC
David, is this with the latest rawhide X server?

Comment 8 Matěj Cepl 2009-07-20 08:07:51 UTC
There is nothing to triage here.

Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.

Comment 9 Pete Zaitcev 2009-07-20 16:43:36 UTC
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.

Comment 10 Joachim Frieben 2009-07-22 08:59:08 UTC
Same here: bug 513001. Issue can be worked around by adding '"AccelMethod" "xaa"' to xorg.conf.