Comment 10 for bug 401067
Revision history for this message
| Bryce Harrington (bryce) wrote Re: [GM45] 3D application fail to run through Wine and often crash X | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> I also installed a separate karmic with the Xorg edgers PPA for testing, there X actually crashes like before.
Then could we get a backtrace for this crash? And post an Xorg.0.log from this. Let me know exactly what versions of -intel, xserver, kernel, etc. you installed; maybe something in xorg-edgers has gotten out of date.
I'd like to focus this bug report just on the X crash issue, since that is a serious issue, and regardless of what wine does it should not make X crash.
For the other issue, while that sounds bad too, for sake of sanity in tracking I would ask that you establish a separate bug report for that. While there could well be an X fault underlying that, I would appreciate it if you would file it against wine, so they can have a look first, in case it is an issue they already know about. They can reassign to X if they conclude it needs a fix in X.
For some additional background... In some cases GlxBadDrawable errors can sometimes occur due to DRI/GLX not being enabled, although looking at your Xorg.0.log I'm not seeing evidence that this is the case. More generally, these are just client error message due to a failed xserver call (such as if the client was attempting to use an unavailable API). These sorts of errors typically should be handled at the client level - i.e. they are not bugs in X, but rather the client app.
All of the WINED3DFMT... stuff really appears to be error messages particular to wine.
Anyway, again, I'd like to focus just on the X crash.