Hi,
On 16.06.2012 02:29, Evan Driscoll wrote:
> On 06/15/2012 03:07 AM, Uli Schlachter wrote:
>> Since you are already building awesome yourself, could you apply the attached
>> patch and show us the new output from where you did "startx"? Please also
>> include the output from "xdpyinfo -queryExtensions | grep opcode" (or
>> "DISPLAY=:0 xdpyinfo -queryExtensions | grep opcode", if you can't run this
>> from
>> a terminal inside the X11 server).
>
> Both are included. You've got the output of 'startx -- :1' with an
> immediate ctrl-alt-backspace, then the 'xdpyinfo' thing. (This gives the
> same input from both X sessions.)
>
> If I'm guessing what you are looking for, it's "RENDER". :-)
"W: awesome: xerror:811: X error: request=(null)" together with " RENDER
(opcode[K: 154, base error: 178)" decodes to "RenderCompositeGlyphs8 (= show
text) failed with error BadPicture". Which raises the question "which of the two
pictures involved was bad?".
With the default config, the source picture should just be a solid color and the
destination picture is the picture that the rest of the drawing goes to, too.
Neither of which is an obvious candidate. However, the rest of the drawing goes
to the same destination picture and since only the text is failing, something
must be wrong with the text color's picture, I guess.
But there is no other error, so apparently this isn't because allocating the
color's solid picture failed...
>> Also, which cairo version do you have?
>
> 1.12.2.
This sounds like a bug in cairo. Sadly, I'm cairo upstream for the xcb backend,
so this is still something that I am supposed to look into.
> Also, just in case anything else rings any alarm bells I've attached my
> .xsession and a directory listing of a couple places I have my custom
> libraries built.
[...]
Cairo is the only thing which should be rendering text here. (Before someone
asks: Pango does lots of magic and finally calculates the position of each
character ("glyph") and then hands this off to cairo so that cairo can do the
actual rendering).
Since I don't have any good ideas what to do about this, let's try some more
random things:
Could you get me the output of 'xdpyinfo -ext RENDER'? I'm only really
interested in which version of RENDER you have, so 'xdpyinfo -ext RENDER | grep
RENDER\ version' would be enough.
Also, could you install xtrace[0] and run awesome under it? I assume that the
last thing in your .xsession is something like "exec awesome". Turn that into
"exec xtrace --relative-timestamps --outfile /tmp/xtrace_output awesome". This
tool dumps all of awesome's X11 requests and all replies from the server into a
text file. Expect lots of output, so please don't do too much stuff in awesome
(e.g. use ctrl+c, a key binding or ctrl-alt-backspace instead of the menu to
close it). I'd be interested in the resulting xtrace_output file.
Cheers,
Uli
[0] http://xtrace.alioth.debian.org/
--
Bitte nicht mit dem verbleibenden Auge in den Laser gucken.
- Vincent Ebert
--
To unsubscribe, send mail to [email protected].
