On 06/18/2012 01:45 PM, Uli Schlachter wrote:
Uhm. Could you triple check if this really is cairo 1.12? This cannot happen.
:-/
I checked 'ldd' of 'awesome', and then checked '/proc/awesome/map' when
it was actually running to confirm that the only libcairo loaded is the
one I built, which c
On 06/15/2012 07:29 PM, Evan Driscoll wrote:
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. I don't really expect you to look at them (or really
spend all that much time
On 06/15/2012 07:29 PM, 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 -
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 -queryEx
OK, so I spent much of the day trying to get Awesome set up on my work
computer. It's an RHEL5 platform and I don't have root, so it was a bit
of an adventure.
I'm running 3.4.12 with the default rc.lua.
I rebuild all the dependencies and got it to the point where it runs and
mostly works, bu
On 06/14/2012 10:37 AM, Uli Schlachter wrote:
Uhm, works fine here. I didn't actually try your config, but instead I copied
over your config. Then I added the call to move_clients_from_other_screens() to
the wrong keybinding (whoops!) and thus added some extra diagnostics (how can
you live with p
Hi all,
For various reasons I'm moving back to Awesome after a couple years of
Xmonad. Unfortunately, having used both models for a while, I rather
prefer the Xmonad approach of sharing the tagset between monitors. (It's
rather more flexible at the cost of increasing the number of keys you
need. F
