THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#349 - Protocol not supported error while operating with Awesome via
awesome-client.
User who did this - Konstantin Stepanov (kstep)
--
In patch:
+#ifndef __FreeBSD__
csfd =
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#349 - Protocol not supported error while operating with Awesome via
awesome-client.
User who did this - Konstantin Stepanov (kstep)
--
* i mean illegal params error when send()ing with MSG_EOR
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#349 - Protocol not supported error while operating with Awesome via
awesome-client.
User who did this - Konstantin Stepanov (kstep)
--
Actually I've never succeed using it. Always ended up with
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#349 - Protocol not supported error while operating with Awesome via
awesome-client.
User who did this - Julien Danjou (jd)
--
That was not my initial question in fact. It was : how do you use
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#350 - naughty: destroy code goes out of sync with index
User who did this - koniu (koniu)
--
rebased
--
More information can be found at the following URL:
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#350 - naughty: popups are referenced by index rather than object
User who did this - koniu (koniu)
Reason for closing: Fixed
Additional comments about closing: The buggy destroy behavior reported above is
now
Hello,
I updated to current git and re-did my config to use tables instead of
functions checking against the updated default rc.lua. Now, as soon as
I open a client awesome segfaults. This doesn't happen if I comment
out the line inserting the tasklist into a wibox. Same thing occurs
when I try
