On Saturday, June 16, 2012 08:55:12 AM Uli Schlachter wrote: > 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.
I can pretty easily try other versions of Cairo, or patch it for more information. One more piece of information: during the process of trying to get things to build, I ran into this problem: http://www.linuxquestions.org/questions/linux- software-2/pangocairo-no-go-749188/#post3803403 (Cairo wasn't picking up something involving fontconfig so wasn't going to build one of its backends, so Pango wasn't picking up a usable Cairo and wasn't building PangoCairo. Installing Fontconfig helped that.) Here's the ./configure output from both Cairo and Pango: http://pastebin.com/pd3rH3zU And while I'm at it, since Cairo seems to depend on Pango and Pangocairo depends on Cairo, it's correct to build Pango, build Cairo, then build Pango again? > 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. This I can do now: $ DISPLAY=:0 xdpyinfo -ext RENDER | grep "RENDER version" RENDER version 0.10 opcode: 154, base error: 178 > Also, could you install xtrace[0] and run awesome under it? This I think will have to wait until tomorrow or Monday when I'm physically at the machine. Unless you can tell me how to run it remotely. Evan -- To unsubscribe, send mail to [email protected].
