THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#1195 - Awesome crashes on start with second display connected User who did this - Uli Schlachter (psychon) ---------- Thanks a lot for this information! Sadly... I don't know. Fun fact 1: My first idea was wrong and the xtrace looks clean. Fun fact 2: Awesome crashes, tries to print a backtrace for the crash and crashes again while doing so. The relevant problem is this one (all the other warnings from valgrind seem benign): ==24000== Invalid read of size 1 ==24000== at 0x670C03B: xcb_key_symbols_get_keycode (in /usr/lib/libxcb-keysyms.so.1.0.0) ==24000== by 0x421C55: xwindow_grabkeys (xwindow.c:133) ==24000== by 0x41CDDE: luaA_root_keys (root.c:239) [...] ==24000== by 0x71E6360: lua_pcall (in /usr/lib/x86_64-linux-gnu/liblua5.1.so.0.0.0) ==24000== by 0x418ED7: luaA_loadrc (luaa.c:672) ==24000== by 0x41A46E: luaA_parserc (luaa.c:729) ==24000== by 0x40D25E: main (awesome.c:522) ==24000== Address 0x22 is not stack'd, malloc'd or (recently) free'd So your rc.lua is bein parsed during startup and it calls root.keys(). One of these keys seems to break something. Further ideas: - Try valgrind again, but with debug symbols for libxcb-keysms.so (it crashes inside this library and I don't see how awesome could call this invalid data). On debian this would be package libxcb-keysyms1-dev - Make a backup of your config and then remove entries from your globalkeys list. I would suggest starting with an empty table, notice that it does not crash and then re-add entries until it crashes again. Main thing I would like to know: Is there a special key that breaks this or does it die for any key? Oh and: Are you using any "weird" keyboard layout? ---------- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1195#comment3750 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
