Re: [ANNOUNCE] awesome 3.3-rc2 released

Hi, nice to have a new rc, thanks to all the developers for their hard work! rc-1 has worked very good so far, I suppose it won't take long to have a final 3.3. On Fri 2009-05-08 10:48, Alex Cornejo acorn...@gmail.com proclaimed: As a related sidenote.. I have to admit I've stopped using

Re: Speeding up awful.client.setslave() / tasklist

At 1241828865 time_t, Gregor Best wrote: For example, is it really neccessary to swap with each visible client? Wouldn't swapping the client with the first slave client to the trick? No, the purpose of the function is to put the client as the latest slave, so this is the only way to do it.

Re: [PATCH] luaA_init: use Lua C API to add paths to package.path

Hi Ali, At 1241818438 time_t, Ali Polatel wrote: Ah, I've played with this piece of code, that's sad it is replaced. :) /* add Lua lib path (/usr/share/awesome/lib by default) */ +lua_getglobal(L, package); +if (LUA_TTABLE != lua_type(L, 1)) { +warn(package is not a

3.3-rc1 crash bug (?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, no idea what exactly just happened, but awesome crashed when I pressed ctrl-q in konqueror. Syslog says: May 9 10:49:21 psytux kernel: [ 8809.790642] awesome[4487]: segfault at 257a000 ip 0032a5c7d511 sp 7fffbd55e868 error 4 in

Re: 3.3-rc1 crash bug (?)

At 1241861577 time_t, Uli Schlachter wrote: I have no idea what caused this and it doesn't seem reproducible which is why I won't open a bug report. I'm updating to rc2 now and I will run awesome in valgrind. Let's see if I can find anything... What I can suggest is to call ulimit -c

Re: [PATCH] luaA_init: use Lua C API to add paths to package.path

At 1241856836 time_t, Ali Polatel wrote: Oops, i forget to remove them :) Attached is the updated patch. Thanks. Pushed. Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // In the Sixth Sense, Bruce Willis is

Re: 3.3-rc1 crash bug (?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Julien Danjou wrote: At 1241861577 time_t, Uli Schlachter wrote: I have no idea what caused this and it doesn't seem reproducible which is why I won't open a bug report. I'm updating to rc2 now and I will run awesome in valgrind. Let's see if

Re: 3.3-rc1 crash bug (?)

At 1241874772 time_t, Uli Schlachter wrote: Well, I went with valgrind and now got this backtrace (man, I miss debugging symbols... btw I still can't compile awesome due to some missing dependencies). Anyone got some ideas what's going on? Proposals how to get my beloved debug symbols? :(

[awesome bugs] #510 - Cursor stuck on waiting with startup notification

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#510 - Cursor stuck on waiting with startup notification User who did this - anrxc (anrxc) -- You could also reset the cursor with: $ xsetroot -cursor_name left_ptr If it's tedious to restart

Re: 3.3-rc1 crash bug (?)

Uli Schlachter pisze: Julien Danjou wrote: At 1241861577 time_t, Uli Schlachter wrote: I have no idea what caused this and it doesn't seem reproducible which is why I won't open a bug report. I'm updating to rc2 now and I will run awesome in valgrind. Let's see if I can find anything...

Re: 3.3-rc1 crash bug (?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mariusz Ceier wrote: Uli Schlachter pisze: Julien Danjou wrote: At 1241861577 time_t, Uli Schlachter wrote: I have no idea what caused this and it doesn't seem reproducible which is why I won't open a bug report. I'm updating to rc2 now and I

Re: 3.3-rc1 crash bug (?)

At 1241876690 time_t, Uli Schlachter wrote: jd: I guess the debian version doesn't have this... bug? Should not. -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // My root password is signature.asc Description:

[awesome bugs] #510 - Cursor stuck on waiting with startup notification

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#510 - Cursor stuck on waiting with startup notification User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 70dffba6b1f33ba83be4362d8c80d920e3e7c753 Author:

Re: premature raise() somewhere?

At 1241879154 time_t, koniu wrote: Somewhere there's an implicit raise() or something which in some situations causes flicker when a client is being managed. The most common situation I see this in is when in max layout and having 1 urxvt window open, I spawn another one and for a split

Re: 3.3-rc1 crash bug (?)

 Do you have git version of xcb-proto ? If yes revert commit fe7b12db4fc0e95f3eef038581bf2154e1727c7a, Correct the length calculation for the value field of GetPropertyReply. ... and rebuild libxcb and xcb-util ... :p Shouldn't you get it reverted if it's a bad commit? -- To unsubscribe,

Re: 3.3-rc1 crash bug (?)

Maarten Maathuis pisze: Do you have git version of xcb-proto ? If yes revert commit fe7b12db4fc0e95f3eef038581bf2154e1727c7a, Correct the length calculation for the value field of GetPropertyReply. ... and rebuild libxcb and xcb-util ... :p Shouldn't you get it reverted if it's a bad

Pull request - random build stuff and some minor config cleanup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 jd just showed me git request-pull. Since I think it's a nice command, I just had to try it. ;) Here's the result: The following changes since commit 0a1bf94036aaa4201d7b2f0f869afe321088de9d: Julien Danjou (1): build: remove useless check