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 awesome-git when it wanted me to upgrade ~10 libs/packages which were not available for ubuntu intrepid. I thought I was being obsolete, so I upgraded to ubuntu jaunty, but it was the same issue there as well.. I am sure debian-unstable has all the packages (since jd probably maintains them, and I believe that's his distro of choice). Anyway, it would be really cool if there was a debian repository with all the awesome dependencies to compile awesome-git, that way we people on debian based distros could just use that repo. I know something like this would be possible using the standard debian-unstable repos, but this requires pinning and what not. Anyhow, I understand that awesome-git HAS to be bleeding edge, so no complaints here, just thought I'd share why at least I am not reporting bugs/patches. BTW, just today I manually installed all the xcb shit from source, so I can finally use awesome-git again. I had the same problem some weeks ago, I could not compile git because I didn't want to build all xcb libs myself. Julien was kind enough to share Debian packages for amd64 here: http://naquadah.org/~jd/debian/xcb-util/ While not as comfortable as have them in a repository that helped for the meantime. Now all required libs are in unstable, and I hope this stays like this for some time. Greetings, Frank -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A signature.asc Description: Digital signature
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. But, if you move the array of ordered client to Lua, that'd be as simple as: local cl1idx, cl2idx for k, v in ipairs(ordered_clients) do if v == c1 then cl1idx == k elseif v == c2 then cl2idx == k end if cl1idx and cl2 idx then break end end table.remove(ordered_clients, cl1idx) table.remove(ordered_clients, cl2idx) table.insert(ordered_clients, cl2idx, c1) table.insert(ordered_clients, cl1idx, c2) -- Call a hook for arranging the screen No hook called, unless at the end. So that'd be a lot faster. Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Ferns will rule the world. signature.asc Description: Digital signature
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 table);
+return;
+}
+lua_getfield(L, 1, path);
+if (LUA_TSTRING != lua_type(L, 2)) {
+warn(package.path is not a string);
+lua_pop(L, 1);
+return;
+}
+lua_pushliteral(L, ; AWESOME_LUA_LIB_PATH /?.lua);
+lua_pushliteral(L, ; AWESOME_LUA_LIB_PATH /?/init.lua);
+lua_concat(L, 3); /* concatenate with package.path */
luaA_dostring(L, package.path = package.path .. \;
AWESOME_LUA_LIB_PATH /?.lua\);
luaA_dostring(L, package.path = package.path .. \;
AWESOME_LUA_LIB_PATH /?/init.lua\);
What's the point of letting the 2 luaA_dostring()?
You forget to remove?
Cheers,
--
Julien Danjou
// ᐰ jul...@danjou.info http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
// There is nothing under this line.
signature.asc
Description: Digital signature
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 libc-2.9.so[32a5c0+149000] (Any idea how I can find out what error 4 means? Uhm, ok, so where is this? objdump -S /lib/libc-2.9.so | vim -R - And I let vim search for c7d511 (the last part of the instruction pointer shown): 32a5c7d511: 4d 8b 44 24 10 mov0x10(%r12),%r8 Scrolling up a little revealed that the next visible symbol there is memcpy(): 0032a5c7ced0 memcpy: 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... Cheers, Uli - -- Do you know that books smell like nutmeg or some spice from a foreign land? -- Faber in Fahrenheit 451 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBCAAGBQJKBU3EAAoJECLkKOvLj8sGYYcH/3k6qnEY/TBJIMieqJ6/BloW 3NJgvC2kmcsDuPD6ETJt2ywA/xcCm/p8Li2lYUd1STs3DaML2vrL14HZdFhdU0DR i5gz6HNzWXWx9d1a8544moWg3nsfRbnuRhV75FQtx2U8NN7ZSKgj20ElHKifKItf 2p61xMSNKI0/jlg0NZqcVwUPe6+eexsS1Ouqj5UBftxeTdCFpcNIn0BX0AcW6K9X Cds+QkzcMEhNAZXMM4yafhti94cSXxAKv+4wNAgPTQ5QA+eMYVegxkh8Od+KqAwJ xQpEFwUvq39L0hJd3flrZ199soIKQGQMl5iIRMs7MiOMSZfq1YPsLhIeBqI7F+0= =MbhN -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
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 unlimited before running awesome. At least you'll have a coredump. And if you can reproduce it, recompiling with -O0 -fno-inline can help to have a more complete bt. Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Trust me. signature.asc Description: Digital signature
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 dead. signature.asc Description: Digital signature
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 I can find anything... What I can suggest is to call ulimit -c unlimited before running awesome. At least you'll have a coredump. And if you can reproduce it, recompiling with -O0 -fno-inline can help to have a more complete bt. Cheers, 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? :( ==22611== Invalid read of size 1 ==22611==at 0x4A09F9E: memmove (mc_replace_strmem.c:517) ==22611==by 0x439E24: (within /usr/bin/awesome) ==22611==by 0x430031: (within /usr/bin/awesome) ==22611==by 0x30AAE0CB15: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D028: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE173DB: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D084: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C706: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C784: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE08093: lua_pcall (in /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x41A843: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611== Address 0x8148ed8 is 0 bytes after a block of size 96 alloc'd ==22611==at 0x4A0891E: malloc (vg_replace_malloc.c:207) ==22611==by 0x4A08AA7: realloc (vg_replace_malloc.c:429) ==22611==by 0x41A923: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611==by 0x40DFDC: (within /usr/bin/awesome) ==22611==by 0x32AE607216: ev_loop (in /usr/lib/libev.so.3.0.0) ==22611==by 0x40E8A6: main (in /usr/bin/awesome) ==22611== ==22611== Invalid read of size 1 ==22611==at 0x4A09F90: memmove (mc_replace_strmem.c:517) ==22611==by 0x439E24: (within /usr/bin/awesome) ==22611==by 0x430031: (within /usr/bin/awesome) ==22611==by 0x30AAE0CB15: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D028: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE173DB: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D084: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C706: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C784: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE08093: lua_pcall (in /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x41A843: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611== Address 0x8148ed9 is 1 bytes after a block of size 96 alloc'd ==22611==at 0x4A0891E: malloc (vg_replace_malloc.c:207) ==22611==by 0x4A08AA7: realloc (vg_replace_malloc.c:429) ==22611==by 0x41A923: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611==by 0x40DFDC: (within /usr/bin/awesome) ==22611==by 0x32AE607216: ev_loop (in /usr/lib/libev.so.3.0.0) ==22611==by 0x40E8A6: main (in /usr/bin/awesome) ==22611== ==22611== Invalid write of size 1 ==22611==at 0x4A09F94: memmove (mc_replace_strmem.c:517) ==22611==by 0x439E24: (within /usr/bin/awesome) ==22611==by 0x430031: (within /usr/bin/awesome) ==22611==by 0x30AAE0CB15: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D028: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE173DB: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0D084: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C706: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE0C784: (within /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x30AAE08093: lua_pcall (in /usr/lib/liblua5.1.so.0.0.0) ==22611==by 0x41A843: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611== Address 0x8148ed8 is 0 bytes after a block of size 96 alloc'd ==22611==at 0x4A0891E: malloc (vg_replace_malloc.c:207) ==22611==by 0x4A08AA7: realloc (vg_replace_malloc.c:429) ==22611==by 0x41A923: (within /usr/bin/awesome) ==22611==by 0x3565A00BE8: (within /usr/lib/libxcb-property.so.1.0.0) ==22611==by 0x40DFDC: (within /usr/bin/awesome) ==22611==by 0x32AE607216: ev_loop (in /usr/lib/libev.so.3.0.0) ==22611==by 0x40E8A6: main (in /usr/bin/awesome) ==22611== ==22611== More than 1000 total errors detected. I'm not reporting any more. ==22611== Final error counts will be inaccurate. Go fix your program! ==22611== Rerun with --error-limit=no to disable this cutoff. Note ==22611== that errors may occur in your program without prior warning from ==22611==
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? :( http://naquadah.org/~jd/debian/awesome_3.3~rc2-1_nostrip-debug-noopt_amd64.deb -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // And thinking so much differently. signature.asc Description: Digital signature
[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 awesome for you (as we all know the clients are not put in their previous positions)... But that doesn't solve the point that awesome will still be waiting for something as the timeout never happens. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=510#comment1235 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.
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... What I can suggest is to call ulimit -c unlimited before running awesome. At least you'll have a coredump. And if you can reproduce it, recompiling with -O0 -fno-inline can help to have a more complete bt. Cheers, 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? :( Hi, 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 Mariusz Ceier -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
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 will run awesome in valgrind. Let's see if I can find anything... What I can suggest is to call ulimit -c unlimited before running awesome. At least you'll have a coredump. And if you can reproduce it, recompiling with -O0 -fno-inline can help to have a more complete bt. Cheers, 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? :( Hi, 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 Mariusz Ceier Nope, this debian testing + awesome 3.3* from unstable (which pulled in libxcb-atom1, libxcb-keysyms1 and libxdg-basedir1 from unstable). jd: I guess the debian version doesn't have this... bug? - -- Do you know that books smell like nutmeg or some spice from a foreign land? -- Faber in Fahrenheit 451 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBCAAGBQJKBYjPAAoJECLkKOvLj8sG7PsIAIcCwC5mHNZcpTT+K4amAWVI AfWqK9uWonDcB6ZRJlm19cCoTNb7x56aXXZzyUJwbDxDPhEk7e8UbtTEIGVuZ2JU ObfZczyEmgdIe522nxLpYemSlX8USZLPqSGaxpfCF032CVfSFB7Ezgh7gav/gfZb ijuq+xNf1qChjFJom1QuThMTuLnd8px+fcUEEAqOMu7UpH97AAAlKGJjaw4BAh+p 889QO+lSMyf1Tm1cRSWwC04yOeI7Iil525AagLMLAMpwqnrEQ+8DQ7NPVVXqMo7H hrJvgQoQS+XXNT5d3iXkJoKIA2qdj5tcq8ZOln21eb9g5j777ci8xWztnxRDsmE= =G88D -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
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: Digital signature
[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: Julien Danjou jul...@danjou.info Date: Sat May 9 16:03:41 2009 +0200 awful.startup_notification: unregister events on time out Signed-off-by: Julien Danjou jul...@danjou.info More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=510 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.
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 second I can see it in the top-left corner of the screen in its default size before the screen is arranged. Every new windows start raised. And that's not a choice, that's how X works AFAIK. One solution could be to set the window down the stack in client_manage() and send a configure window request (_if needed_) to trigger the go down before it is mapped later by arrange(). Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Anna Molly! Anna Molly! Anna Molly! signature.asc Description: Digital signature
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, send mail to awesome-devel-unsubscr...@naquadah.org.
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 commit? I think I should ... bugreport: https://bugs.freedesktop.org/show_bug.cgi?id=21644 Mariusz Ceier -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
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 for libs are available in the git repository at: git://git.znc.in/psychon/awesome.git for-jd Uli Schlachter (8): Fix a wrong leading space in gperf.sh's shebang Remove some useless use of cat Fix a bashism in gperf.sh Use 'sh' instead of 'sh -e' Use tr [:lower:] [:upper:] instead of the a-z one Use _LDFLAGS instead of _LIBRARIES Get the shell for spawn_with_shell earlier Don't use obsolete table.foreach() in the default config awesomeConfig.cmake |4 ++-- awesomerc.lua.in | 21 +++-- build-utils/gperf.sh | 17 + lib/awful/util.lua.in |6 ++ 4 files changed, 24 insertions(+), 24 deletions(-) - -- Do you know that books smell like nutmeg or some spice from a foreign land? -- Faber in Fahrenheit 451 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBCAAGBQJKBdDCAAoJECLkKOvLj8sG41oH/26nzj786soKpnocKES+jryK Yrzdq2Goz/fXyI54P35viVsZHy10tmn3PsAzX8Afe7qXLI6MPybfIvEyJLc7CfH8 5B1zNXHtBYK0Cah/sz40QAK8puoiMvZ25ecagobAtnXSUGw3P1FGQyxKwxYrpjZu Vw1DPma6uxt9nXSDP9Kp9lvtD0zcGdaGPhHo3n+BBVM1j6z/JA13mRrJqLOFssnz y2QqHBOiSI1d1wW4smVsMrmZn+xdufnWAsrdKdQdeW5e83S+V/PVepDpSV95YFpb 6/QLpTvlarNKpPFX6hh7+xDIgjI9maSK822Ew6QvW+7tcK1n8r2eUmhY+hx7eyo= =MzQu -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
