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
Opened by Max (silverhammermba) - Friday, 29 January 2016, 23:14 GMT
Last edited by Levente Polyak (anthraxx) - Wednesday, 20 July 2016, 09:25 GMT
|
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
Wednesday, 20 July 2016, 09:25 GMT
Reason for closing: No response
Additional comments about closing: seems to be resolved
I disabled compton in my rc.lua and i could thens
start awesome.
-- Run Compton
-- awful.util.spawn_with_shell("compton &")
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
@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.)