You are not logged in.
http://img32.imageshack.us/img32/4461/awesomewmrend.png
Apparently, awesome is getting screen output of programs running. That should be pidgin's output (the window appears fine).
I noticed the text does not fade at all on all awesome(wm) GUI parts.
I installed a theme package from AUR and copied "wombat" to my homefolder and changed the corresponding location of the theme.lua in rc.lua.
EDIT: It seems every single theme I have has the same issue, except the default one.
Last edited by normal2 (2011-07-02 14:51:13)
Implode.
Offline
I have isolated the cause of this:
Deliberate addition of unnecessary characters?
Anyho, the theme.bg_* has problem with last two characters, they are unnecessary.
theme.bg_normal = "#1c1d1c88"
theme.bg_focus = "#0c0d0c88"
theme.bg_urgent = "#34353488"
becomes
theme.bg_normal = "#1c1d1c"
theme.bg_focus = "#0c0d0c"
theme.bg_urgent = "#343534"
I punched first values into GIMP html tag and got nothing.
Lua is insane to debug.
Implode.
Offline
They aren't unnecessary, they represent the alpha channel for transparency. Just for future reference.
Offline
They aren't unnecessary, they represent the alpha channel for transparency. Just for future reference.
Then shouldn't xcompmgr be a dependency of the theme package?
Implode.
Offline
No, since an Awesome theme consists of a single text file, and those two characters can easily be removed just as you removed theme. Theme packages only add wallpapers and (possibly) icons, which are typically supposed to be defined by the user since absolute paths are usually involved. All the theme package does is collect all these things together for convenience; if either xcompmgr or cairo-compmgr were a dependency, someone else would expect that to be removed, and the themes can easily be used without either.
Offline