Performed full-upgrade; Awesome now will not start, crashes X

sugardeath · 2011-06-09 04:24:10

Earlier today I performed a full pacman -Syyu on my laptop and now I cannot get awesome to start, it throws the following errors after it kills the X server:

W: awesome: xcolor_init_reply:264: awesome: error, cannot allocate color 'black'
W: awesome: xcolor_init_reply:264: awesome: error, cannot allocate color 'white'
W: awful: function is deprecated, see timer object
stack traceback:
        /usr/share/awesome/lib/awful/util.lua:39: in function 'deprecate'
        /usr/share/awesome/lib/awful/hooks.lua:59: in function 'register'
        /home/satoshi/.config/awesome/temp.lua:23: in main chunk
        [C]: in function 'require'
        /home/satoshi/.config/awesome/rc.lua:16: in main chunkW: awesome: xerror:809: X error: request=AllocNamedColor, error=BadName
W: awesome: xerror:809: X error: request=AllocNamedColor, error=BadName
E: awesome: signal_fatal:239: dumping backtrace
awesome(backtrace_get+0x40) [0x808a640]
awesome() [0x805359f]
[0xb783d400]
/usr/lib/libxcb.so.1(xcb_setup_roots_length+0x4) [0xb7811bc4]
awesome(systray_refresh+0x23) [0x807e183]
awesome() [0x8053572]
/usr/lib/libev.so.4(ev_invoke_pending+0x51) [0xb73eb541]
/usr/lib/libev.so.4(ev_run+0xeea) [0xb73efefa]
awesome(main+0x98d) [0x805330d]
/lib/libc.so.6(__libc_start_main+0xf3) [0xb71e6103]
awesome() [0x8053435]

I know exactly what the deprecated function errors are referring to, and removing the offending function calls does not change a thing (well, that specific error disappears, but the rest of it is identical).

Openbox works 100% fine.

Running X without a WM works 100%fine.

Awesome is at version 3.4.9-1
Cairo-xcb is at version 1.10.2-2 (don't know if this matters?)
libxcb is at version 1.7-2
libev is at version 4.04-1

This machine does not have a head. Instead I access it remotely via NX/FreeNX. I don't think this would have a hand in it, but I'm putting that out there just in case. I was using it just earlier in the day from work, via NX, and awesome was working just fine. I performed the upgrade when I got home today.. and it's been broken ever since.

I've tried downgrading awesome and cairo-xcb (the only packages I can pull from AUR/repos with older versions, since I was stupid and cleared my cache a while back).

Last edited by sugardeath (2011-06-09 04:24:26)

BaggioKwok · 2011-06-09 04:48:25

Please try to backup your awesome config files and then remove them

sugardeath · 2011-06-09 04:51:25

This is what I get now:

W: awesome: xcolor_init_reply:264: awesome: error, cannot allocate color 'black'
W: awesome: xcolor_init_reply:264: awesome: error, cannot allocate color 'white'
W: awesome: systray_register:119: error getting systray atom
E: awesome: a_xcb_io_cb:231: X server connection broke

XIO:  fatal IO error 0 (Success) on X server ":1019.0"
      after 9 requests (9 known processed) with 0 events remaining.
Error: Can't open display: :1019.0

Last edited by sugardeath (2011-06-09 04:53:52)

BaggioKwok · 2011-06-09 05:05:30

just google-ing

please try to replace black with #000000 in the theme files

Last edited by BaggioKwok (2011-06-09 05:07:27)

sugardeath · 2011-06-09 05:13:54

That is not the issue, every single color definition is in hex.

anonymous_user · 2011-06-09 13:33:53

Try updating/recompiling awesome. Its at 3.4.10 now.

Also what if you use the default rc.lua?

JGC · 2011-06-09 14:09:03

Looking at those color messages, I think you'll need the xorg-rgb package.

sugardeath · 2011-06-09 14:50:38

anonymous_user wrote:

Try updating/recompiling awesome. Its at 3.4.10 now.
Also what if you use the default rc.lua?

I've recompiled awesome several times now, both 3.4.9 and 3.4.10. No luck.

Default rc.lua gives the same problems (minus the deprecated function call, of course).

JGC wrote:

Looking at those color messages, I think you'll need the xorg-rgb package.

I don't see such a package, or anything that looks similar, in the repos or in AUR. Unless you mean xorg-xrdb, which I've got already.

Also, interesting development which makes me believe it's not an issue with the host machine alone: When I got into work this morning, I decided to give it a shot again... and it worked. I can NX in and run awesome just fine from my Win7 machine here at work. It does not work from either of my Arch machines at home, though.. Will look into them when I get back.

Mr.Elendig · 2011-06-09 16:07:20

grab a rgb.txt off google?

s922183t · 2011-06-16 03:05:51

Same here, but, when I exit, doesn't show any error message.

Last edited by s922183t (2011-06-16 03:11:33)

Arch Linux

#1 2011-06-09 04:24:10

Performed full-upgrade; Awesome now will not start, crashes X

#2 2011-06-09 04:48:25

Re: Performed full-upgrade; Awesome now will not start, crashes X

#3 2011-06-09 04:51:25

Re: Performed full-upgrade; Awesome now will not start, crashes X

#4 2011-06-09 05:05:30

Re: Performed full-upgrade; Awesome now will not start, crashes X

#5 2011-06-09 05:13:54

Re: Performed full-upgrade; Awesome now will not start, crashes X

#6 2011-06-09 13:33:53

Re: Performed full-upgrade; Awesome now will not start, crashes X

#7 2011-06-09 14:09:03

Re: Performed full-upgrade; Awesome now will not start, crashes X

#8 2011-06-09 14:50:38

Re: Performed full-upgrade; Awesome now will not start, crashes X

#9 2011-06-09 16:07:20

Re: Performed full-upgrade; Awesome now will not start, crashes X

#10 2011-06-16 03:05:51

Re: Performed full-upgrade; Awesome now will not start, crashes X

Board footer