FS#47945 - [awesome] Crash on startup

Attached to Project: Community Packages
Opened by Max (silverhammermba) - Friday, 29 January 2016, 23:14 GMT
Last edited by Levente Polyak (anthraxx) - Wednesday, 20 July 2016, 09:25 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Awesome immediately crashes on startup. stderr output:

W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#000000'
W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#535d6c'
W: awesome: luaA_dofunction:78: error while running function
stack traceback:
[C]: in function 'error'
/usr/share/awesome/lib/gears/debug.lua:23: in function 'gears.debug.assert'
/usr/share/awesome/lib/wibox/drawable.lua:64: in upvalue 'do_redraw'
/usr/share/awesome/lib/wibox/drawable.lua:247: in function </usr/share/awesome/lib/wibox/drawable.lua:244>
error: /usr/share/awesome/lib/gears/debug.lua:23: Assertion failed: 'Cairo context entered error state: WRITE_ERROR'
stack traceback:
/usr/share/awesome/lib/gears/debug.lua:23: in function 'gears.debug.assert'
/usr/share/awesome/lib/wibox/drawable.lua:64: in upvalue 'do_redraw'
/usr/share/awesome/lib/wibox/drawable.lua:247: in function </usr/share/awesome/lib/wibox/drawable.lua:244>
W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#222222'
W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#535d6c'
W: awesome: luaA_dofunction:78: error while running function
stack traceback:
[C]: in function 'error'
/usr/share/awesome/lib/gears/debug.lua:23: in function 'gears.debug.assert'
/usr/share/awesome/lib/wibox/drawable.lua:64: in upvalue 'do_redraw'
/usr/share/awesome/lib/wibox/drawable.lua:247: in function </usr/share/awesome/lib/wibox/drawable.lua:244>
error: /usr/share/awesome/lib/gears/debug.lua:23: Assertion failed: 'Cairo context entered error state: WRITE_ERROR'
stack traceback:
/usr/share/awesome/lib/gears/debug.lua:23: in function 'gears.debug.assert'
/usr/share/awesome/lib/wibox/drawable.lua:64: in upvalue 'do_redraw'
/usr/share/awesome/lib/wibox/drawable.lua:247: in function </usr/share/awesome/lib/wibox/drawable.lua:244>
E: awesome: main:472: cannot open display (error 1)

Additional info:
* running using startx (no login manager)
* version 3.5.7-1
* using default config and theme
* fully up-to-date system
This task depends upon

Closed by  Levente Polyak (anthraxx)
Wednesday, 20 July 2016, 09:25 GMT
Reason for closing:  No response
Additional comments about closing:  seems to be resolved
Comment by Marius (groundz) - Saturday, 30 January 2016, 08:55 GMT
Can confirm that i have the same error.
Comment by Marius (groundz) - Saturday, 30 January 2016, 09:47 GMT
Update:
I disabled compton in my rc.lua and i could thens
start awesome.

-- Run Compton
-- awful.util.spawn_with_shell("compton &")
Comment by Levente Polyak (anthraxx) - Saturday, 30 January 2016, 15:44 GMT
have you tried reporting this issue upstream?
Comment by Koundinya Vajjha (weurdo) - Sunday, 31 January 2016, 04:52 GMT
Confirming the same issue here as well. Also Marius' suggestion of disabling compton works.
Comment by Max (silverhammermba) - Monday, 01 February 2016, 20:58 GMT
It does seem to be the compositor. I disabled xcompmgr and the error went away for me.

I also tried bumping the version to 3.5.8 and rebuilding but the error persists.

I reported upstream: https://github.com/awesomeWM/awesome/issues/661
Comment by Max (silverhammermba) - Tuesday, 02 February 2016, 16:32 GMT
Marius and Koundinya, I only have the bug with xcompmgr -- switching to compton fixes it for me. Another user on the awesome mailing list also fixed it by switching from xcompmgr to compton. Can you confirm that you still crash with awesome 3.5.8 and compton?
Comment by Koundinya Vajjha (weurdo) - Saturday, 06 February 2016, 16:14 GMT
Max, I can confirm that it still crashes for me. Running awesome version 3.5.8 and compton. Attaching my Xorg log.
   Xorg.log (7.1 KiB)
Comment by Max (silverhammermba) - Saturday, 06 February 2016, 18:37 GMT
We're thinking it might be an Intel bug now, but I haven't looked into reporting it upstream yet. Another workaround that people are reporting is that starting the compositor after awesome is running (e.g. just running it manually from a shell) works.
Comment by Uli Schlachter (psychon) - Monday, 29 February 2016, 19:02 GMT
I'm lazy, hence:

@weurdo: Your crash is in the modesetting driver. Could you run 'echo _init+0x365e | eu-addr2line -e modesetting_drv.so.debug' (No idea where you get debug info for the modesetting driver from nor if arch even provides this) to figure out where the crash actually happens?

@silverhammermba: Your backtrace on https://github.com/awesomeWM/awesome/issues/661 is different. For you the interesting stuff would be 'echo _init+0x56141 | eu-addr2line -e intel_drv.so.debug' and the same with '_init+0x58576'.

(Assuming the backtraces provided are still up to date; If one wants to be nice and helpful, the same thing can be done with every other entry in the backtrace to figure out where the crash *actually* occurs.)
Comment by Levente Polyak (anthraxx) - Saturday, 18 June 2016, 16:12 GMT
Any news on this one? I'm about to close this as it does not seem to be within awesome itself.
Comment by Max (silverhammermba) - Sunday, 19 June 2016, 17:08 GMT
I think this can be closed. It doesn't seem to be awesome's fault and has possibly been resolved with later package updates.

Loading...