http://bugs.winehq.org/show_bug.cgi?id=17338
--- Comment #11 from Tim Mertens tim@filmchicago.org 2009-02-11 23:15:11 --- Created an attachment (id=19400) --> (http://bugs.winehq.org/attachment.cgi?id=19400) Quicken log with xrender flag
I'm not sure what you mean by debug symbols - I installed the -dev package and the assertion error still looks the same, but I did find these bug reports interesting:
http://bugs.freedesktop.org/show_bug.cgi?id=6019 http://bugs.freedesktop.org/show_bug.cgi?id=13479
And also noticed when I ran Quicken with the flags: WINEDEBUG=+font,+xrender,+xrandr,+synchronous wine qw.exe
immediately prior to the assertion error are the lines: "trace:xrender:UploadGlyph buflen = 393216. Got metrics: 262144x12 adv=0,0 origin=-294912,12 trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph trace:xrender:UploadGlyph "
Where every other instance of UploadGlyph in the log looks like this: "trace:xrender:UploadGlyph buflen = 32. Got metrics: 8x8 adv=12,0 origin=2,10 trace:xrender:UploadGlyph ## ## trace:xrender:UploadGlyph ### ### trace:xrender:UploadGlyph ###### trace:xrender:UploadGlyph #### trace:xrender:UploadGlyph #### trace:xrender:UploadGlyph ###### trace:xrender:UploadGlyph ### ### trace:xrender:UploadGlyph ## ## trace:xrender:X11DRV_XRender_ExtTextOut Writing L"\001f" at 266,18"
Taking a look at the original error, without +synchronous "X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 156 (RENDER) Minor opcode of failed request: 20 (RenderAddGlyphs) Serial number of failed request: 19881 Current serial number in output stream: 20175"
It looks like it's trying to render the Glyphs but it is probably failing to do so. Maybe I'm completely wrong, but as far as I can tell, this appears to be more related to the bugs linked above than the original xcb error we were looking at.
The question then is whether this is something that can be fixed in Wine somehow (maybe there's a font with mixed outlines/bitmaps?) or if it is purely an xlib issue.