THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#1245 - Wibox won't respond minutes after awesome starts User who did this - Uli Schlachter (psychon) ---------- Could you check for error messages from awesome on stderr? To know where error messages from awesome go to, you can use this command: $ ls -l /proc/$(pidof awesome)/fd/2 Where this goes to depends on how you start awesome. Typical places are things like /var/log/gdm.log, slim.log or vt1 if you start your X session from that (on debian it is always ~/,xsession-errors which is so much easier...). ---------- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1245#comment3965 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.
