https://bugzilla.novell.com/show_bug.cgi?id=257830 ------- Comment #18 from eich@novell.com 2007-03-27 12:03 MST ------- This problem has nothing to do with the fireglx driver. It's purely client side. the assertions have been added to xcb to help debug broken applications (or toolkit libs) but also broken libraries. If the problem is gone on a post 10.2 system it's a good sign as it indicates that a bug in an application library or application has been fixed. I don't recommend to run xcb on a production syustem on 10.2. That the problem goes away with a different form of X forwarding is not hard to explain: with the -Y forwarding the client uses the credentials of a secure X application while with -X it doesn't have access to certain resources and even extensions. Thus the client library needs to take different code paths ie. perform different actions (unless it fails completely). Most modern toolkits however are able to run without certain extensions - these code paths are however less tested. Thus it is possible that such a code path triggers the problem. The difference in performance can also be explained: usually the fallback code paths are slower. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.