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 - Vova Zoubritsky (vogrez) ---------- I've removed any "weird" layouts (I had 3 and cycling with capslock) before the start. libxcb-keysyms1-dev was installed, but it seems like it doesn't provide a .so file - it's just a symlink. Removing the call to root.keys / or calling it with an empty table progresses further, but still quits with output. The xtrace for this run is longer. W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#000000' W: awesome: color_init_reply:137: awesome: error, cannot allocate color '#222222' W: awesome: systray_register:89: error getting systray atom E: awesome: a_xcb_io_cb:210: X server connection broke Adding just a single key (tried a couple different ones) goes back to crashing on xcb_key_symbols_get_keycode. ---------- One or more files have been attached. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1195#comment3751 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.
