A very weird hard to reproduce bug
OK, I have this issue with icedvoe, the debian version of thunderbird. I start it from .xsession, sometimes (about 5 out of 6 times), when I log in, I get a sound notification of a new message and awesome crash bringing me to the login screen. this does not happen if I start icedove after awesome starts. It does not write to any log I can see, just crash. I use awesome v3.4-775-gc4a7f80 but it happened of some older versions too. for the time being I removed it from xsession and start it manually. Any ideas? thanks, Yussi. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: A very weird hard to reproduce bug
On 24.11.2012 18:49, Yussi wrote: OK, I have this issue with icedvoe, the debian version of thunderbird. I start it from .xsession, sometimes (about 5 out of 6 times), when I log in, I get a sound notification of a new message and awesome crash bringing me to the login screen. this does not happen if I start icedove after awesome starts. It does not write to any log I can see, just crash. If it crashes, it should print some stuff to its stderr. I use awesome v3.4-775-gc4a7f80 but it happened of some older versions too. for the time being I removed it from xsession and start it manually. Any ideas? Well, run awesome under gdb, valgrind or some other tool and see what it says? For example: (echo run ; echo bt full) | gdb --args awesome /tmp/gdb-output.txt Also, read http://awesome.naquadah.org/wiki/Debugging. Uli -- my $key = \x49\x03\x93\x08\x19\x94\x96\x94\x28\x93\x83\x04\x68\x28\xa8\xf5. \x0a\xb9\x94\x02\x45\x81\x93\x1f\xbc\xd7\xf3\xad\x93\xf5\x32\x93; my $cipher = Crypt::Rijndael-new( $key, Crypt::Rijndael::MODE_ECB() ); my $plain = $ciper-decrypt($daten); -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Thanks for you constant effort - it is greatly appreciated! Regards, David -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 25 November 2012 1:48 AM To: awesome-devel list; awesome Subject: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, On 11.09.2009 14:05, Julien Danjou wrote: With a good month late, here comes 3.4-rc1. With a good two years late, here comes 3.5-rc1. There's an amazing number of changes, but many are internals ones, so you won't notice them.[...] There's an astonishing number of changes. Also, we did some changes to make awesome future-proof. With lua 5.2, module() was deprecated in lua. Awesome no longer uses this function. However, this has user-visible effects. You now need to explicitly assign modules to global variables: local awful = require(awful) Some things from the default rc.lua have been moved into awful to ease the configuration file management. The default rc.lua is 110 lines lighter now. The rc.lua is 50 lines longer now. 40 lines of that is due to a titlebar rewrite. Instead of forcing some kind of titlebars on the user, titlebars are now configured similar to wiboxes. The new widget layout system is also in place. Everyone will hate me for replacing the widget system again, but I do like the result. Due to this, everything works differently now. On the plus side, you won't need to use mywidget.widget ever again. :-) There's obviously a number of changes all over the place. I don't have the list in mind of course, so feel free to dig into the changelog. [...] The same applies to this release, too! Again, there is a wiki page for documenting some changes that affect configurations. Feel free to update it with any kind of information which you would have hoped to find here, but had to figure out the hard way (= asking me). http://awesome.naquadah.org/wiki/Awesome_3.4_to_3.5 As always, we all here at breaking-your-config-WMs would like to thank all contributors. Without your bug reports, patches, ideas and good questions, this window manager would suck a lot more than it already does. One thing I want to highlight: A total of 77 different people wrote patches for this release! Have fun! Uli awesome version 3.5-rc1 has been released. It is available from: tar.xz: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.xz md5: 42b76ed6a60ca376e1e0afb859986645 sha1: 2ab103a0a9675468f1dafc35e3df756e3d31b20b tar.bz2: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.bz2 md5: 1be1cb43adbc7242a6c53d3cc01a62bd sha1: 8c9b558cfa9293453fb1befda9ac06b365e15df2 number of changes - - 820 number of commiters - --- 77 shortlog - Uli Schlachter (444): wibox: Set a proper back pixel Set a wibox' bit gravity to NorthWest. wibox: make sure no garbage is painted to the screen wibox: check if a wibox' window exists before modifying it Wibox: Check if a window exists before changing it Fix a invalid pointer crash bug image: Use imlib2's image cache Make it easier to change the default layout Implement the GetCapabilities call in naughty Handle synthetic UnmapNotify events Revert Handle synthetic UnmapNotify events Handle synthetic UnmapNotify events *correctly* client_focus_update(): Balance the lua stack property.c: Don't leave stuff on the lua stack Check for UNMAPPED instead of UNVIEWABLE Use WM_STATE_NORMAL as default awesome.spawn(): Return the PID Update API docs for recent change to spawn Check for xwininfo before using it awful.menu.clients: Raise the newly focused client Tasklist: Add some missing parentheses Remove _NET_WM_DESKTOP when client got no tags Handle _NET_WM_DESKTOP more intelligently Remove invalid variable usage Update the tasklist when a client's icon changes xwindow_set_state(): Use uint32_t instead of long Reorder some code for fullscreening windows Tasklist: Listen to the correct signals Add systray windows to the save-set Don't reparent systray windows on exit Add all managed client windows to the safe set Don't manually unban all windows on exit Handle errors in the config better Read a textbox' text correctly textbox: Throw a lua error on invalid markup Naughty: Catch invalid markup in notifications Clear a draw_text_context_t during wipe() Move wibox_systray_kickout() up Kick out the systray when wiping a wibox Add a comment to XCB_NONE for sibling Avoid some flickering when a new window opens Split up screen_scan() Screen: Only use Xrandr if it provides data Ignore size hints on fullscreen windows Minor cleanup Fix a minor ICCCM incompatibility Fix some
Eminent status
Hi list, hi Lucas. I am currently migrating from Awesome 3.4 to master, and the Eminent library is not working with the last version. It appears that Shifty can do the same things, but it requires a lot more configuration, and Eminent does the job nicely for me. Also, the french version of the Shifty wiki page[1] states that Eminent is now obsolete (« Eminent est maintenant considérée obsolète. ») but I can't find this statement anywhere else. So I'm wondering, what is the current status of Eminent, and will it be updated before the 3.5 release? [1] http://awesome.naquadah.org/wiki/Shifty/fr -- Benoît Zugmeyer
Re: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Thanks a lot guys :)
Re: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Hi guys, it's never too late to release ;) Anyway: can someone prepare a debian package? Thanks and kind regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Patch to fix the luadoc build, with lua 5.1.
Without this you get a nil error out of luadoc.
Signed-off-by: Robin H. Johnson robb...@gentoo.org
--- ../awesome-3.5-rc1/lib/naughty.lua.in.orig 2012-11-24 05:51:33.0
-0800
+++ ../awesome-3.5_rc1/lib/naughty.lua.in 2012-11-24 13:17:14.025201211
-0800
@@ -55,7 +55,6 @@
-- @field low The preset for notifications with low urgency level
-- @field normal The default preset for every notification without a preset
that will also be used for normal urgency level
-- @field critical The preset for notifications with a critical urgency level
--- @class table
naughty.config.presets = {
normal = {},
low = {
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee Infrastructure Lead
E-Mail : robb...@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Thanks for you constant effort - it is greatly appreciated! Regards, David -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 25 November 2012 1:48 AM To: awesome-devel list; awesome Subject: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, On 11.09.2009 14:05, Julien Danjou wrote: With a good month late, here comes 3.4-rc1. With a good two years late, here comes 3.5-rc1. There's an amazing number of changes, but many are internals ones, so you won't notice them.[...] There's an astonishing number of changes. Also, we did some changes to make awesome future-proof. With lua 5.2, module() was deprecated in lua. Awesome no longer uses this function. However, this has user-visible effects. You now need to explicitly assign modules to global variables: local awful = require(awful) Some things from the default rc.lua have been moved into awful to ease the configuration file management. The default rc.lua is 110 lines lighter now. The rc.lua is 50 lines longer now. 40 lines of that is due to a titlebar rewrite. Instead of forcing some kind of titlebars on the user, titlebars are now configured similar to wiboxes. The new widget layout system is also in place. Everyone will hate me for replacing the widget system again, but I do like the result. Due to this, everything works differently now. On the plus side, you won't need to use mywidget.widget ever again. :-) There's obviously a number of changes all over the place. I don't have the list in mind of course, so feel free to dig into the changelog. [...] The same applies to this release, too! Again, there is a wiki page for documenting some changes that affect configurations. Feel free to update it with any kind of information which you would have hoped to find here, but had to figure out the hard way (= asking me). http://awesome.naquadah.org/wiki/Awesome_3.4_to_3.5 As always, we all here at breaking-your-config-WMs would like to thank all contributors. Without your bug reports, patches, ideas and good questions, this window manager would suck a lot more than it already does. One thing I want to highlight: A total of 77 different people wrote patches for this release! Have fun! Uli awesome version 3.5-rc1 has been released. It is available from: tar.xz: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.xz md5: 42b76ed6a60ca376e1e0afb859986645 sha1: 2ab103a0a9675468f1dafc35e3df756e3d31b20b tar.bz2: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.bz2 md5: 1be1cb43adbc7242a6c53d3cc01a62bd sha1: 8c9b558cfa9293453fb1befda9ac06b365e15df2 number of changes - - 820 number of commiters - --- 77 shortlog - Uli Schlachter (444): wibox: Set a proper back pixel Set a wibox' bit gravity to NorthWest. wibox: make sure no garbage is painted to the screen wibox: check if a wibox' window exists before modifying it Wibox: Check if a window exists before changing it Fix a invalid pointer crash bug image: Use imlib2's image cache Make it easier to change the default layout Implement the GetCapabilities call in naughty Handle synthetic UnmapNotify events Revert Handle synthetic UnmapNotify events Handle synthetic UnmapNotify events *correctly* client_focus_update(): Balance the lua stack property.c: Don't leave stuff on the lua stack Check for UNMAPPED instead of UNVIEWABLE Use WM_STATE_NORMAL as default awesome.spawn(): Return the PID Update API docs for recent change to spawn Check for xwininfo before using it awful.menu.clients: Raise the newly focused client Tasklist: Add some missing parentheses Remove _NET_WM_DESKTOP when client got no tags Handle _NET_WM_DESKTOP more intelligently Remove invalid variable usage Update the tasklist when a client's icon changes xwindow_set_state(): Use uint32_t instead of long Reorder some code for fullscreening windows Tasklist: Listen to the correct signals Add systray windows to the save-set Don't reparent systray windows on exit Add all managed client windows to the safe set Don't manually unban all windows on exit Handle errors in the config better Read a textbox' text correctly textbox: Throw a lua error on invalid markup Naughty: Catch invalid markup in notifications Clear a draw_text_context_t during wipe() Move wibox_systray_kickout() up Kick out the systray when wiping a wibox Add a comment to XCB_NONE for sibling Avoid some flickering when a new window opens Split up screen_scan() Screen: Only use Xrandr if it provides data Ignore size hints on fullscreen windows Minor cleanup Fix a minor ICCCM incompatibility Fix some
[awesome bugs] #762 - mozplugger freezes desktop (works in wmii)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#762 - mozplugger freezes desktop (works in wmii) User who did this - Dan Forest-Barbier (dpanth3r) -- Same here, still getting freezes (have to switch to tty/ssh to kill the embedded pdf reader). Debian (sid, AMD64), Awesome 3.4.13-1, Firefox 17.0 (from LinuxMint import repository), evince/xpdf/acroread:i386 all cause the bug. I think this issue should at least get the “confirmed” status :) -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=762#comment3238 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.
[awesome bugs] #1056 - Setting titlebar colors doesn't work as expected
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Björn Åström (bjoast)
Attached to Project - awesome
Summary - Setting titlebar colors doesn't work as expected
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I am running the latest git master and, according to the
documentation, titlebar background colors can be set with the arguments
bg_normal and bg_focus like in the example below:
awful.titlebar(c, { bg_normal = #c2c2c2, bg_focus = #828282 })
That works until you move the client at which point the titlebar reverts to the
default theme color. This however does work:
awful.titlebar(c, { bg = #c2c2c2 })
But there is no way to set the focus color unfortunately :-)
The same is true for fg_normal and fg.
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1056
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.
[awesome bugs] #1056 - Setting titlebar colors doesn't work as expected
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1056 - Setting titlebar colors doesn't work as expected User who did this - Björn Åström (bjoast) -- A small correction: bg_focus can be set but there is another problem: The titlebar gets set to bg_focus only when you _move_ the client. Shifting focus doesn't affect the background color, but every client you have moved now has the bg_focus color set and will continue having that color set until you restart awesome. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1056#comment3239 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.
