*grin* Ok, so maybe it's not life threatening or anything but it's really frustrating.

This is what the output is:

Anyone have any ideas?

*grin* Sometimes I wish privateer had a journal function - that would be really useful!

Perhaps the jerky-ness is more to do with my aging 2.4Ghz CPU.....

Nope, just upgraded to a 3.4Ghz P4 Extreme Edition and privateer is still jerky with Beryl active.

Oh well, never mind.

Even with Beryl enabled and using the latest Feisty stuff, Neverwinter Nights (along with it's Movies) are playing fine here, though I didn't play it for all that long to see if it crashed, but the performance seemed very fast.

It's been so long since I played it, I can't remember even what I'm supposed to do. Good thing it has a Journal

Leech

Thanks for that Ryba,

Yeah - I noticed the updated libx11 packages come through last night (NZ time) but haven't had a chance to fiddle yet. I'm glad they have fixed the problem for you though - that's awesome news!

What I did to get around the problem was to run privateer remake in a window instead of fullscreen and it ran fine. I, too, also switch back to metacity (from beryl) before playing privateer so as to stop the play being jerky. Never had it crash or anything, just cause a lot of lag.

If only the switch user functionality would go back to how it used to be ...... perhaps it will before release!

Looks like yesterday they put up a version of libx11-6 and libx11-data which "fix" the problem correctly. Try using that. I did and my games work great again.

Another thing to notice, my games work perfectly when *not* in the 3d effects mode or beryle.

for some reason my games act wierd and sometimes lockup the screen or crash the x-server but only when i'm playing full screen 3d games inside of the 3d desktop.

I just switch to a non-3d desktop cause i'd rather have a functional system.

Ooops - posted too soon. After playing for a bit fine and exiting, X restarted and logged me off.

Now when I (or any other user) run privateer, X restarts back to the login screen.

I upgraded those packages again which stops the X restarts but puts me back at the same original error again.

Any other ideas? Anyone?

Yes I also get this problem with Neverwinter Nights and Unreal Tournament 2003/2004 games.

I'm guessing pretty much any commercial game has this problem.

The way *I* solved this problem was to cheat and *downgraded* the libx11-6 and libx11-data files to the 1.0.3 version (grabbed off of edgy repository).

Once I did that, everything seemed to work just fine. I seriously do hope that feisty fixes their assertion check or removes that assertion all together before releasing. Tons of stuff break because of their checks.

Woooohoooo - that did the trick! Off to the WC Universe for a bit of escapism again post-feisty.