Comment 28 for bug 61607

I'm still getting the same behaviour with XAA and updating my feisty as
of 1 hr ago. I confirm that radeon says its using XAA, I'm getting the
same stack trace when closing a window and a just black opengl context.

I can provide the code I'm using for testing.

Actually I'll test the ubuntu package of that same software to confirm.

if you do apt-get install puredata gem

Then you can start puredata from terminal like so:

pd -lib Gem

then if you click on "Help" -> "Browser..."

Then click on gem/ -> 01.basic -> 01.redSquare.pd

Then you get a funny graph, just click on "create" which will create the
opengl context, and then "1" to start rendering.

We should see a red square, but we just get a black window. if you press
"0" to stop rendering and "destroy" to close the context, you'll get a
segfault in glXMakeCurrentReadSGI from /usr/lib/libGL.so.1

I'm quite certain its the radeon/mesa/dri causing this issue, but I only
have feisty on one machine, this powerbook5,2 with ati 9600 card.

Shall I get the gem maintainer in on the discussion? I think its Guenter
Geiger, but I don't see any maintainer listed on this page:

http://packages.ubuntulinux.org/feisty/graphics/gem

.b.

b wrote:
> Hi Erik,
>
> I'm updating my machine right now, I already tried changing to XAA
> (before I left the acceleration option unspecified, I guess EXA is the
> default) but my rendering is still black, so I assume that a version of
> xorg that is out there now will fix it. I'll post if I am still unable
> to get things to work with XAA and feisty as of today.
>
> .b.
>
> Erik Chakravarty wrote:
>> Acceleration now works with the current Mesa package in Feisty, however
>> there are severe problems with the EXA acceleration method which causes
>> X to use 100% of the CPU for a long time when doing simple operations
>> (opening firefox, for example).
>>
>> Switching to XAA acceleration fixes this.
>>
>> glxgears reports 1600-1700 FPS when running over Beryl + AIGLX.
>>
>