[awesome bugs] #298 - maximising should not imply windows to hide others
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - martin f. krafft (madduck) Attached to Project - awesome Summary - maximising should not imply windows to hide others Task Type - Feature Request Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - When I maximise a window, it lays on top of all other windows, hiding everything behind, including windows created after the window was maximised. It would be nice if this weren't the case, if maximising did not dictate a z-index, and if I could create new windows that would appear in front of the maximised window. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=298 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 [EMAIL PROTECTED]
[awesome bugs] #298 - maximising should not imply windows to hide others
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#298 - maximising should not imply windows to hide others User who did this - martin f. krafft (madduck) -- Is it possible to push LAYOUT_FLOATING behind LAYOUT_TILED for certain tags? That would solve the problem nicely for my case (when I have a maximised browser window and want a temporary terminal just to quickly try something or run a command). -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=298#comment683 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 [EMAIL PROTECTED]
[awesome bugs] #300 - CMake fails to find lua on FreeBSD
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Jeremy Johnston (jeremyj) Attached to Project - awesome Summary - CMake fails to find lua on FreeBSD Task Type - Bug Report Category - Build system Status - Unconfirmed Assigned To - Operating System - FreeBSD Severity - Critical Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - CMake on FreeBSD seems to complain about LUA_LIBRARIES not being defined. This was a very simple correction, I added set(LUA_LIBRARIES lua) right after set(CURSES_NEED_NCURSES true) in awesomeConfig.cmake. Without this change CMake fails to find lua installed. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=300 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 [EMAIL PROTECTED]
[awesome bugs] #299 - Restarting empties systray
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#299 - Restarting empties systray User who did this - Julien Danjou (jd) -- I don't know. I tested various client and this what I got: - kmix (KDE 4): works perfectly - mail-notification works, sometimes segfault - audacious: sometimes works, sometimes exits - xchat: works perfectly - pidgin: works perfectly - twinkle: does not work on restart And I got roughly the same result with stalonetray. In case of twinkle, I guess that might be a QT3 issue. QT3 is a crap for that since it only respect KDE standard. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=299#comment687 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 [EMAIL PROTECTED]
[awesome bugs] #299 - Restarting empties systray
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#299 - Restarting empties systray User who did this - martin f. krafft (madduck) -- In noticed the following written to stderr by bluetooth-applet when I restart: (bluetooth-applet:17220): Gdk-WARNING **: GdkWindow 0xe0001e unexpectedly destroyed The program 'bluetooth-applet' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 336 error_code 182 request_code 155 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=299#comment689 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 [EMAIL PROTECTED]
[awesome bugs] #299 - Restarting empties systray
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#299 - Restarting empties systray User who did this - Julien Danjou (jd) -- I can't run bluetooth applet. Can you run it in gdb with --sync as args, break on gdk_x_error and give me a full backtrace? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=299#comment690 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 [EMAIL PROTECTED]
[awesome bugs] #297 - keybord is very slow sometimes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#297 - keybord is very slow sometimes User who did this - boyinasuitcase (boyinasuitcase) -- I can confirm. I experience basically the same thing running 2.3.4 Every once and a while after the system has been running for a while, pressing the key does nothing. Mouse works and sometimes if I wait long enough the functionality comes back. nothing in logs to indicate that the key event was missed or even seen. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=297#comment692 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 [EMAIL PROTECTED]
[awesome bugs] #302 - default file with theme configuration shoul be moved to /etc
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Michal Nowak (mnowak) Attached to Project - awesome Summary - default file with theme configuration shoul be moved to /etc Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 3.0-rc5 Due in Version - Undecided Due Date - Undecided Details - /usr/share/awesome/themes/default is config file for awesome-3 theme and because of this should be moved from /usr/share to /etc, where config files usually live. The thing is that installing it in via RPM in normal way, leads to overwriting. If I mark it as config file %config(noreplace) then on update is created file default.rpmnew and user is able to merge changes and delete the .rpmnew file. Problem with this approach is that putting config files (marked via %config) is weird. dhcp-lab-192 SPECS # rpmlint -i awesome.spec /usr/src/redhat/SRPMS/awesome-3.0-0.8.rc6.fc9.src.rpm /usr/src/redhat/RPMS/i386/awesome-3.0-0.8.rc6.fc9.i386.rpm /usr/src/redhat/RPMS/i386/awesome-doc-3.0-0.8.rc6.fc9.i386.rpm /usr/src/redhat/RPMS/i386/awesome-debuginfo-3.0-0.8.rc6.fc9.i386.rpm awesome.i386: E: file-in-usr-marked-as-conffile /usr/share/awesome/themes/default A file in /usr is marked as being a configuration file. Store your conf files in /etc/ instead. 4 packages and 1 specfiles checked; 1 errors, 0 warnings. Please, consider relevant options on fixing this issue. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=302 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 [EMAIL PROTECTED]
[awesome bugs] #307 - awesome.restart() doesn't work
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#307 - awesome.restart() doesn't work User who did this - Gunkhold Wuckbumm (Benjamin) -- Well, looks like I was confused and restarting works just fine. BUT when I specify a configuration file via command line option --config, awesome doesn't use this file anymore after restart. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=307#comment693 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 [EMAIL PROTECTED]
[awesome bugs] #303 - prompt uses wrong keyboard layout
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#303 - prompt uses wrong keyboard layout User who did this - Konstantin Stepanov (kstep) -- My awesome version: awesome (awesome) v3.0-rc6 (Elect The Dead) ⢠Build: Sep 5 2008 15:25:57 for i386 by gcc version 4.2.1 ([EMAIL PROTECTED]) ⢠Image drawing engine: Imlib2 ⢠D-Bus support: â My OS is: FreeBSD 7.0-STABLE #12 -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=303#comment696 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 [EMAIL PROTECTED]
[awesome bugs] #303 - prompt uses wrong keyboard layout (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#303 - prompt uses wrong keyboard layout User who did this - Thomas Green (didumos) -- Attaching my xorg.conf file, and awesome --version: awesome (awesome) v3.0-rc6 (Elect The Dead) • Build: Sep 6 2008 20:12:12 for x86_64 by gcc version 4.3.1 ([EMAIL PROTECTED]) • Image drawing engine: Imlib2 • D-Bus support: ? -- One or more files have been attached. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=303#comment698 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 [EMAIL PROTECTED]
[awesome bugs] #303 - prompt uses wrong keyboard layout
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#303 - prompt uses wrong keyboard layout User who did this - Julien Danjou (jd) -- Can you try to restart awesome to see if it helps it to get the keyboard layout? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=303#comment699 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 [EMAIL PROTECTED]
[awesome bugs] #306 - Cmake won't find lua50
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#306 - Cmake won't find lua50 User who did this - Julien Danjou (jd) Reason for closing: Not a bug Additional comments about closing: It needs lua5.1; cmake prints lua50 but it's a bug in cmake. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=306 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 [EMAIL PROTECTED]
[awesome bugs] #308 - Magnifier layout: Switching windows not bringing windows in front
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Dominik Meister (neptoon) Attached to Project - awesome Summary - Magnifier layout: Switching windows not bringing windows in front Task Type - Bug Report Category - Layouts Status - Unconfirmed Assigned To - Operating System - Linux Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - I'm running the latest git as of this morning. I noticed that switching windows in the magnifier layout does not bring up the focused windows in front anymore. The window gets the focus but doesn't appear in the center of the screen. This has worked before (git from ~ 2 weeks ago). More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=308 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 [EMAIL PROTECTED]
[awesome bugs] #309 - twitterfox popup are not displayed in floating mode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Marc-Andre Lureau (elmarco) Attached to Project - awesome Summary - twitterfox popup are not displayed in floating mode Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Using v3.0-rc6-55-gd30eecd (next) the twitterfox popup are not floating. They used to be with awesome (master), 3.0rc4 or so. I don't know about current master branch, I can check if necessary. How can I give information about window properties? thanks More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=309 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 [EMAIL PROTECTED]
[awesome bugs] #310 - Gnome-do looses keyboard focus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#310 - Gnome-do looses keyboard focus User who did this - Julien Danjou (jd) -- I confirm this for a3. However it is fixed somehow in next branch. :-) -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=310#comment713 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 [EMAIL PROTECTED]
[awesome bugs] #311 - problem after grab server on inizialization
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#311 - problem after grab server on inizialization User who did this - Julien Danjou (jd) -- Do you use a startup script running something else than awesome? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=311#comment717 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 [EMAIL PROTECTED]
[awesome bugs] #313 - Get rid of XML style tags for images/font/colors
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Chris Bannister (Zariel) Attached to Project - awesome Summary - Get rid of XML style tags for images/font/colors Task Type - Feature Request Category - Lua libraries Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Hi, I never understood why xml markup was used in the layouts for setting the colors, WoW (see http://www.wowwiki.com/Widget_API) does it like this. widget:SetTextColor(r, g, b, [a]) etc which in my opinion gives much more flexibility to the widgets in general. Now I dont know C so all I can comment on is the lua side of it, each widget has its own prototype with the widget having it in the __index metatable. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=313 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 [EMAIL PROTECTED]
[awesome bugs] #314 - prompt does not show up, when bg_focus is a transparent color.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - calmar (calmar) Attached to Project - awesome Summary - prompt does not show up, when bg_focus is a transparent color. Task Type - Bug Report Category - Statusbars Status - New Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - with latest git (so I had this quite some time now already - some weeks), but just tracked down to the config file now: So: when I have set in my theme file: bg_focus = #006633aa , the prompt (mod + f1) does not show up. When I have only #006633 without transparency, the prompt works as expected. Cheers More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=314 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 [EMAIL PROTECTED]
[awesome bugs] #314 - prompt does not show up, when bg_focus is a transparent color.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#314 - prompt does not show up, when bg_focus is a transparent color. User who did this - Julien Danjou (jd) Reason for closing: Not a bug Additional comments about closing: Reading stout/err will tell you that this is not a valid Pango color value. You can only use that type of alpha color in background color for general, titlebar or statusbar. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=314 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 [EMAIL PROTECTED]
[awesome bugs] #297 - keybord is very slow sometimes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#297 - keybord is very slow sometimes User who did this - Michal Nowak (mnowak) -- The workaround for this is to run gnome-keyboard-properties and speedup (or slowdown, or both) the Repeat Keys - Delay. Some other X-only tools should do the same trick. Still, never seen it outside of awesome. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=297#comment719 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 [EMAIL PROTECTED]
[awesome bugs] #303 - prompt uses wrong keyboard layout
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#303 - prompt uses wrong keyboard layout User who did this - Julien Danjou (jd) -- Again XKB options are probably not useable by XCB and so by awesome. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=303#comment721 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 [EMAIL PROTECTED]
[awesome bugs] #317 - select window under mouse pointer on tag change
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - martin f. krafft (madduck) Attached to Project - awesome Summary - select window under mouse pointer on tag change Task Type - Feature Request Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - If I switch tags, it would be nice if I could configure awesome to automatically make active the window under the mouse pointer. Otherwise the pointer might well hover over a window which isn't active, which can be confusing and is certainly inconsequential. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=317 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 [EMAIL PROTECTED]
[awesome bugs] #320 - Error setting wallpaper on startup
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#320 - Error setting wallpaper on startup User who did this - Andrey A. Ugolnik (andreyu) -- As i say in may first message it works fine, without any errors. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=320#comment734 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 [EMAIL PROTECTED]
[awesome bugs] #308 - Stacking broken with Zaphod mode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#308 - Stacking broken with Zaphod mode User who did this - Steffen Schulz (pepe) -- +1 on this one. Xinerama is still lacking support e.g. from wallpaper-tools and my 'slim' login manager. Awesome also fails to handle the stupid systray icon of valknut when in xinerama mode. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=308#comment738 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 [EMAIL PROTECTED]
[awesome bugs] #323 - Systray breaks when dynamically changing number of screens
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Lluis (xscript) Attached to Project - awesome Summary - Systray breaks when dynamically changing number of screens Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.0-rc6 Due in Version - Undecided Due Date - Undecided Details - I use the same configuration in two machines, one where I use two monitors and another where I use just one. Whenever I change the number of available displays (using a script wraping xrandr), awesome resets and some of the applications in the systray just die. Sorry, but I don't have further information. Anyway, if you tell me something specific to look for I can give it a try. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=323 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 [EMAIL PROTECTED]
[awesome bugs] #325 - Hiding rhythmbox to the dock does not hide it at all
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Michal Nowak (mnowak) Attached to Project - awesome Summary - Hiding rhythmbox to the dock does not hide it at all Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 3.0 Due in Version - Undecided Due Date - Undecided Details - Run rhythmbox music player on let's say tag 7 - dock it. * the square, indicating that some window is in tag, is present on the tag 7 * when is rhythmbox hidden, moving to another tag, 6, and un-hiding it (click on the icon in dock) does not work I've noticed it runs on with other apps, notably xchat, might be just a rhythmbox fault. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=325 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 [EMAIL PROTECTED]
[awesome bugs] #324 - Awesome doesn't show default promptbox(Mod4+F1) if bg_normal and bg_focus are set with alpha channel
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#324 - Awesome doesn't show default promptbox(Mod4+F1) if bg_normal and bg_focus are set with alpha channel User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: Fixed in git. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=324 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 [EMAIL PROTECTED]
[awesome bugs] #323 - Systray breaks when dynamically changing number of screens
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#323 - Systray breaks when dynamically changing number of screens User who did this - Julien Danjou (jd) Reason for closing: Duplicate Additional comments about closing: Duplicate of FS#299 More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=323 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 [EMAIL PROTECTED]
[awesome bugs] #333 - Floating apps overlap the statusbar on startup
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#333 - Floating apps overlap the statusbar on startup User who did this - calmar (calmar) More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=333 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 [EMAIL PROTECTED]
[awesome bugs] #335 - awful.placement.no_overlap() fails spawn windows in open areas
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#335 - awful.placement.no_overlap() fails spawn windows in open areas
User who did this - Julien Danjou (jd)
Reason for closing: Fixed
Additional comments about closing: -- Configuring awesome-version-internal.h
-- Configuring awesome.doxygen
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/jdanjou/Work/src/awesome/src/.build-cigue-x86_64-linux-gnu-4.3.2
Running make Makefile…
Building…
[ 0%] Built target version_stamp
[ 8%] Built target generated_sources
[ 76%] Built target awesome
[ 85%] Built target awesome-client
[ 86%] Built target luadoc
[100%] Built target man
cigue awesome/src % git diff
diff --git a/awesomerc.lua.in b/awesomerc.lua.in
index 8367a72..6e445ae 100644
1 ---
2 -- @author Julien Danjou lt;[EMAIL PROTECTED]gt;
3 -- @copyright 2008 Julien Danjou
4 -- @release @AWESOME_VERSION@
5 ---
6
7 -- Grab environment we need
8 local ipairs = ipairs
9 local pairs = pairs
10 local math = math
11 local table = table
12 local print = print
13 local capi =
14 {
15 screen = screen,
16 mouse = mouse,
17 }
18 local client = require(awful.client)
19 local layout = require(awful.layout)
20
21 --- Placement module for awful
22 module(awful.placement)
23
24 --- Check if an area intersect another area.
25 -- @param a The area.
26 -- @param b The other area.
27 -- @return True if they intersect, false otherwise.
28 local function area_intersect_area(a, b)
29 return (b.x a.x + a.width
30 and b.x + b.width a.x
31 and b.y a.y + a.height
32 and b.y + b.height a.y)
33 end
34
35 --- Get the intersect area between a and b.
36 -- @param a The area.
37 -- @param b The other area.
38 -- @return The intersect area.
39 local function area_intersect_area_get(a, b)
40 local g = {}
41 g.x = math.max(a.x, b.x)
42 g.y = math.max(a.y, b.y)
43 g.width = math.min(a.x + a.width, b.x + b.width) - g.x
44 g.height = math.min(a.y + a.height, b.y + b.height) - g.y
45 return g
46 end
47
48 function table.reverse(t)
49 local n = {}
50 for k, v in ipairs(t) do
51 n[#t - k + 1] = v
52 end
53 return n
54 end
55
56 --- Remove an area from a list, splitting the space between several area that
57 -- can overlap.
58 -- @param areas Table of areas.
59 -- @param elem Area to remove.
60 -- @return The new area list.
61 local function area_remove(areas, elem)
62 for i = #areas, 1, -1 do
63 -- Check if the 'elem' intersect
64 if area_intersect_area(areas[i], elem) then
65 -- It does? remove it
66 local r = table.remove(areas, i)
67 local inter = area_intersect_area_get(r, elem)
68
69 if inter.x r.x then
70 table.insert(areas, {
71 x = r.x,
72 y = r.y,
73 width = inter.x - r.x,
74 height = r.height
75 })
76 end
77
78 if inter.y r.y then
79 table.insert(areas, {
80 x = r.x,
81 y = r.y,
82 width = r.width,
83 height = inter.y - r.y
84 })
85 end
86
87 if inter.x + inter.width r.x + r.width then
88 table.insert(areas, {
89 x = inter.x + inter.width,
90 y = r.y,
91 width = (r.x + r.width) - (inter.x + inter.width),
92 height = r.height
93 })
94 end
95
96 if inter.y + inter.height r.y + r.height then
97 table.insert(areas, {
98 x = r.x,
99 y = inter.y + inter.height,
100 width = r.width,
101 height = (r.y + r.height) - (inter.y + inter.height)
102 })
103 end
104 end
105 end
105
--- a/awesomerc.lua.in
+++ b/awesomerc.lua.in
@@ -407,6 +407,8 @@ awful.hooks.manage.register(function (c)
awful.client.movetotag(tags[target.screen][target.tag], c)
end
+awful.placement.no_overlap(c)
+
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
diff --git a/lib/awful/placement.lua.in b/lib/awful/placement.lua.in
index 95958a1..b150d68 100644
--- a/lib/awful/placement.lua.in
+++ b/lib/awful/placement.lua.in
@@ -9,6 +9,7 @@ local ipairs = ipairs
local pairs = pairs
local math = math
local table = table
+local print = print
local capi =
{
screen = screen,
@@ -44,22 +45,29 @@ local
[awesome bugs] #335 - awful.placement.no_overlap() fails spawn windows in open areas
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#335 - awful.placement.no_overlap() fails spawn windows in open areas User who did this - Julien Danjou (jd) More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=335 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 [EMAIL PROTECTED]
[awesome bugs] #209 - Systray refresh problem
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#209 - Systray refresh problem User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: This is fixed since 3.0 More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=209 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 [EMAIL PROTECTED]
[awesome bugs] #336 - awesome-menu no longer lets you edit things that have completions
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#336 - awesome-menu no longer lets you edit things that have completions User who did this - Mike Kelly (pioto) -- Okay, If I get the time to this weekend, I might try a git bisect to try and track down where this bug came in. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=336#comment766 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 [EMAIL PROTECTED]
[awesome bugs] #336 - awesome-menu no longer lets you edit things that have completions (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#336 - awesome-menu no longer lets you edit things that have completions User who did this - Hannes Schueller (mr_creosote) -- Here's another patch which makes the autocompletion behaviour configurable (autocomplete = true|false in the menu part of the config file). This includes the previous patch, so do NOT apply both. Take either, depending on what you'd like to achieve. -- One or more files have been attached. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=336#comment768 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 [EMAIL PROTECTED]
[awesome bugs] #337 - Wibox won't adhere to height/width arguments when not on the top
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#337 - Wibox won't adhere to height/width arguments when not on the top User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit a6f2fce9495c6c253b26065f19d321b0a89a3b35 Author: Julien Danjou [EMAIL PROTECTED] Date: Fri Oct 3 08:56:13 2008 +0200 wibox: handle position on new correctly We do not need to call setposition since we are not attached. We just need to set orientation and position_update to get the right coords. Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=337 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 [EMAIL PROTECTED]
[awesome bugs] #339 - Error while building awesome-3.0
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Alexandrov Anton (alant) Attached to Project - awesome Summary - Error while building awesome-3.0 Task Type - Bug Report Category - Build system Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.0 Due in Version - Undecided Due Date - Undecided Details - Cannot build awesome. The error is follows: Running cmake… -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- cat - /usr/bin/cat -- ln - /usr/bin/ln -- grep - /usr/bin/grep -- git - /usr/bin/git -- hostname - /bin/hostname -- gperf - /usr/bin/gperf -- asciidoc - /usr/bin/asciidoc -- xmlto - /usr/bin/xmlto -- gzip - /usr/bin/gzip -- lua - /usr/local/bin/lua -- luadoc - /usr/local/bin/luadoc -- Looking for doxygen... -- Looking for doxygen... - found /usr/local/bin/doxygen -- Looking for dot tool... -- Looking for dot tool... - found /usr/local/bin/dot -- Looking for wsyncup in /usr/lib/libcurses.so -- Looking for wsyncup in /usr/lib/libcurses.so - found -- Found Curses: /usr/lib/libcurses.so -- Found Lua51: /usr/local/lib/liblua.a;/usr/lib/libm.so -- checking for module 'xcb' -- found xcb, version 1.0 -- checking for modules 'glib-2.0;cairo;pango;pangocairo;xcb-randr;xcb-xinerama;xcb-event=0.3.0;xcb-aux=0.3.0;xcb-atom=0.3.0;xcb-keysyms=0.3.0;xcb-icccm=0.3.0;cairo-xcb;xproto=7.0.11;imlib2' -- found glib-2.0, version 2.12.12 -- found cairo, version 1.7.6 -- found pango, version 1.16.4 -- found pangocairo, version 1.16.4 -- found xcb-randr, version 1.0 -- found xcb-xinerama, version 0.9.92 -- found xcb-event, version 0.3.0 -- found xcb-aux, version 0.3.0 -- found xcb-atom, version 0.3.0 -- found xcb-keysyms, version 0.3.0 -- found xcb-icccm, version 0.3.0 -- found cairo-xcb, version 1.7.6 -- found xproto, version 7.0.13 -- found imlib2, version 1.4.1 -- checking for module 'dbus-1' -- found dbus-1, version 1.0.2 -- Configuring lib/awful/screen.lua -- Configuring lib/awful/beautiful.lua -- Configuring lib/awful/placement.lua -- Configuring lib/awful/util.lua -- Configuring lib/awful/prompt.lua -- Configuring lib/awful/client.lua -- Configuring lib/awful/tag.lua -- Configuring lib/awful/hooks.lua -- Configuring lib/awful/layout.lua -- Configuring lib/awful/widget.lua -- Configuring lib/awful/completion.lua -- Configuring lib/awful/titlebar.lua -- Configuring lib/awful/init.lua -- Configuring lib/beautiful.lua -- Configuring lib/tabulous.lua -- Configuring config.h -- Configuring awesomerc.lua -- Configuring themes/default -- Configuring awesome-version-internal.h -- Configuring awesome.doxygen -- Configuring done -- Generating done -- Build files have been written to: /home/alant/soft/awesome-current/awesome/.build-alant-i486-slackware-linux-4.1.2 Running make Makefile… Building… CMake Error: The current CMakeCache.txt directory /home/alant/soft/awesome-current/awesome/.build-alant-i486-slackware-linux-4.1.2/CMakeCache.txt is different than the directory /home/alant/soft/awesome-current/awesome/.build-alant-i486-slackware-linux-4.1.2 where CMackeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt CMake Error: The source /home/alant/soft/awesome-current/awesome/CMakeLists.txt does not match the source /home/alant/soft/awesome-current/awesome/CMakeLists.txt used to generate cache. Re-run cmake with a different source directory. make[1]: *** [cmake_check_build_system] Error 1 make: *** [cmake-build] Error 2 --- Additional information: [EMAIL PROTECTED]:~/soft/awesome-current/awesome$ cmake --version cmake version 2.6-patch 1 More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=339 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 [EMAIL PROTECTED]
[awesome bugs] #339 - Error while building awesome-3.0
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#339 - Error while building awesome-3.0 User who did this - Alexandrov Anton (alant) -- Unfortunately, it doesn't help... -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=339#comment772 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#338 - awesome freezes via awesome-client and piping into it
User who did this - calmar (calmar)
--
so, with git it's the same.
What I have is a broken-pipe message on the 'terminal' (where I started x) like;
W:awesome luaA_cb:911 can't send back to client via domain socket: pipe broken
additonally I tried to send a single line into awesome-client:
[EMAIL PROTECTED]:~/packets/awesome$ while true; do nr=$(( $RANDOM % 100)); echo 'pb_diskfree:bar_data_add(root, '${nr}')' | awesome-client; sleep 0.1 ; done
?^[W: awesome: sockets_reconnect:82: connection lost, reconnecting…
W: awesome: sockets_reconnect:82: connection lost, reconnecting…
W: awesome: sockets_reconnect:82: connection lost, reconnecting…
W: awesome: sockets_reconnect:82: connection lost, reconnecting…
it does not freeze like this so.
It does freeze on this setup (using a staedy pipe or so):
while true; do nr=$(( $RANDOM % 100)); echo 'pb_diskfree:bar_data_add(root,
'${nr}')'; echo ; sleep 0.1 ; done | awesome-client
--
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338#comment773
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 [EMAIL PROTECTED]
[awesome bugs] #339 - Error while building awesome-3.0
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#339 - Error while building awesome-3.0 User who did this - Julien Danjou (jd) -- Not a cmake export but well it build everywhere else… -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=339#comment774 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#338 - awesome freezes via awesome-client and piping into it User who did this - Julien Danjou (jd) -- It does not here, so I guess there's something wrong in your configuration file. Can you try with the standard one? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338#comment775 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 [EMAIL PROTECTED]
[awesome bugs] #339 - Error while building awesome-3.0
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#339 - Error while building awesome-3.0 User who did this - Julien Danjou (jd) Reason for closing: Not a bug More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=339 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#338 - awesome freezes via awesome-client and piping into it User who did this - calmar (calmar) -- so far a bisect: as expected (since that was about the big change there, or similar): 37f4fbfe39aa5f9b1832acd1f55dc7ea17ff1da3 is first bad commit commit 37f4fbfe39aa5f9b1832acd1f55dc7ea17ff1da3 Author: Nathan Weizenbaum [EMAIL PROTECTED] Date: Thu Sep 18 21:48:55 2008 -0700 awesome-client, socket, lua: make awesome-client into a true REPL After recieving a command from awesome-client, awesome will send the result of that command in return and awesome-client will print it out. Signed-off-by: Nathan Weizenbaum [EMAIL PROTECTED] Signed-off-by: Julien Danjou [EMAIL PROTECTED] :100644 100644 3af9c87b4093a0b3a5f20c5af6dc1724bfdf38d2 b608ea56bd2118a7e026717305c59c554e9389a4 M awesome-client.c :04 04 fd7c2ec139e5d192e6e27903bf0b8fd66d99519d 54efc5225c3bfc92a7b1071230817d023ffee1fc M common :100644 100644 0e49393a67ac08158d87a9d54d35206255ff28d6 7c8329b80fb84d65f76c979ddacd4ee11136a893 M lua.c -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338#comment780 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#338 - awesome freezes via awesome-client and piping into it User who did this - calmar (calmar) -- about the strace, what I did (and I have no idea if this is what you want), strace -p pid-of-awesome. the interesting part is this: http://www.calmar.ws/tmp/typescript.txt (or see attachment - what is the same) -- One or more files have been attached. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338#comment781 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 [EMAIL PROTECTED]
[awesome bugs] #340 - Broken focus on windows without an input focus hint.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Micha? Kazior (kazik) Attached to Project - awesome Summary - Broken focus on windows without an input focus hint. Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Hello, A few days ago I noticed I can't focus StepMania (in windowed mode) anymore. A few Java VM applications seem to suffer too. The windows actually pop out in the taskbar, and can be somewhat accessed, but awesome doesn't even mark them as focused. I managed to track the commit that broke the previous behaviour: -- snip -- commit 506a4200c69e652214c5c2f1438fdf3952c846d0 Author: Julien Danjou [EMAIL PROTECTED] Date: Wed Sep 3 16:51:46 2008 +0200 client: support input focus hints Signed-off-by: Julien Danjou [EMAIL PROTECTED] -- /snip -- This created a `nofocus' variable which gets set to true for the mentioned windows. I noticed these don't have the Client accepts input or input focus: True hint set at all - shouldn't it be assume it's True by default ? However, I'm not the one to speak, because I don't know the EWMH standards. Nevertheless the current behaviour seems to be somewhat broken, as other WMs handle the mentioned windows quite nicely. It should be at the very least possible to override the setting manually via lua interface, not ? More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=340 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 [EMAIL PROTECTED]
[awesome bugs] #340 - Broken focus on windows without an input focus hint.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#340 - Broken focus on windows without an input focus hint. User who did this - Paul Bonser (pib) -- The same problem occurs with DosBox in windowed mode. It gets input fine in fullscreen mode, but doesn't respond to any input in windowed mode. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=340#comment786 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 [EMAIL PROTECTED]
[awesome bugs] #340 - Broken focus on windows without an input focus hint.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#340 - Broken focus on windows without an input focus hint. User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 09686f3f3ef71dfbcc6f1ee09bfcf0b50079fc0f Author: Julien Danjou [EMAIL PROTECTED] Date: Sat Oct 11 09:52:03 2008 +0200 property: check input flag set (FS#340) Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=340 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#338 - awesome freezes via awesome-client and piping into it User who did this - Julien Danjou (jd) -- Okay, I was able to reproduce it too. It blocks on sendto(), obviously. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338#comment787 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 [EMAIL PROTECTED]
[awesome bugs] #338 - awesome freezes via awesome-client and piping into it
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#338 - awesome freezes via awesome-client and piping into it User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit bc5569ab94a0c82d316686212e5f984ea945f637 Author: Julien Danjou [EMAIL PROTECTED] Date: Mon Oct 13 11:17:30 2008 +0200 luaa: send back but do not block (FS#338) Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=338 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 [EMAIL PROTECTED]
[awesome bugs] #341 - wine windows loose keyboard focus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#341 - wine windows loose keyboard focus User who did this - Julien Danjou (jd) Reason for closing: Fixed More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=341 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 [EMAIL PROTECTED]
[awesome bugs] #329 - too hard to un-snap windows from edges
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#329 - too hard to un-snap windows from edges User who did this - Dale P. Smith (dsmith) -- This is *very* annoying. To get the accel up enough to start moving the window, you move the mouse fairly far. Sometimes this move is far enough over that it then snaps to something else, and you end up never actually able to move the window. Ugh! -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=329#comment788 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 [EMAIL PROTECTED]
[awesome bugs] #329 - too hard to un-snap windows from edges
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#329 - too hard to un-snap windows from edges
User who did this - Paul Bonser (pib)
--
You could try different values of snap passed to mouse_move in your rc.lua.
According to the docs it defaults to 8 pixels.
button({ modkey }, 1, function (c) c:mouse_move({snap = 4}) end),
Or you could add a line to be able to move windows without snapping at all:
button({ modkey, Shift }, 1, function (c) c:mouse_move({snap = 0}) end),
What would be really nice is if there was a way to turn snap on and off
depending on what keys were held down, so you could let go of shift when you
got close to the edge you wanted to snap to, and it would then snap to it.
--
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=329#comment789
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 [EMAIL PROTECTED]
[awesome bugs] #329 - too hard to un-snap windows from edges
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#329 - too hard to un-snap windows from edges User who did this - Dale P. Smith (dsmith) -- Heh. I've done exactly that. It doesn't solve the problem however. On a related note, I'd like to adjust the snap when dragging the window by the titlebar, but I can't figure out how to get to the titlebar text widget from the client object. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=329#comment790 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 [EMAIL PROTECTED]
[awesome bugs] #343 - unable to set a border on wiboxes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#343 - unable to set a border on wiboxes User who did this - Andrei Thorp (garoth) -- As a general border idea -- it'd be nice to be able to set borders per side, like in HTML. As a use case example for wiboxes, I could have a horizontal stripe on top and bottom for decoration, but not on the sides. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=343#comment796 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 [EMAIL PROTECTED]
[awesome bugs] #343 - unable to set a border on wiboxes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#343 - unable to set a border on wiboxes User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 96c23ad5cb28d8eeb280f2e0de54bb7b7b923d08 Author: Julien Danjou [EMAIL PROTECTED] Date: Tue Oct 14 17:31:27 2008 +0200 wibox: initialize wibox borders correctly (FS#343) Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=343 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 [EMAIL PROTECTED]
[awesome bugs] #341 - wine windows loose keyboard focus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#341 - wine windows loose keyboard focus User who did this - Julien Danjou (jd) More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=341 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 [EMAIL PROTECTED]
[awesome bugs] #341 - wine windows loose keyboard focus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#341 - wine windows loose keyboard focus User who did this - koniu (koniu) -- Nope, re-focusing with keyboard gets the window highlighted, but no keyboard input. From what I've experienced so far, clicking the client is the only way to use it again. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=341#comment795 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 [EMAIL PROTECTED]
[awesome bugs] #329 - too hard to un-snap windows from edges
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#329 - too hard to un-snap windows from edges User who did this - Dale P. Smith (dsmith) -- I have a vague idea of what the problem is, but not yet exactly how to fix it. Basically, the window will not move if the difference between the current mouse position and the previous position is less than snap. So if you move the mouse slowly, the delta from position to position will *never* be larger than snap, so the window will never move. Depends on how fast mouse updates come in I guess. Probably what needs to be done is to compare the current position with the last snapped position. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=329#comment797 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 [EMAIL PROTECTED]
[awesome bugs] #344 - unable to set width of imagebox
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#344 - unable to set width of imagebox User who did this - Julien Danjou (jd) Reason for closing: Implemented Additional comments about closing: commit 6ee617e77744f26bd307d6180bab30560154f386 Author: Julien Danjou [EMAIL PROTECTED] Date: Tue Oct 14 17:37:39 2008 +0200 image: add crop_and_scale() method Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=344 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 [EMAIL PROTECTED]
[awesome bugs] #345 - wine toolobox windows stay on all tags and always on top
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - David Hájek (dante4d) Attached to Project - awesome Summary - wine toolobox windows stay on all tags and always on top Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - I'm using Guitar Pro 5 under wine with awesome. It has two toolbox windows (can't recall the right name - these windows have special flag passed to CreateWindowEx API - they have smaller titlebar and only close (X) button. They dock into titlebar). They are always shown on all tags and always on top of all other windows when undocked from the toolbar, plus don't have awesome's borders and can't be moved/resized with mouse (actually, they sometimes somehow fall under other windows, but I can't replicate it now). However, other undocked toolbar windows behave alright. Here's a screenshot: http://www.dante4d.cz/gp.png xprop of the fretboard window: _NET_WM_NAME(UTF8_STRING) = 0x46, 0x72, 0x65, 0x74, 0x62, 0x6f, 0x61, 0x72, 0x64 WM_ICON_NAME(STRING) = Fretboard WM_NAME(STRING) = Fretboard WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. bitmap id # to use for icon: 0x120faff bitmap id # of mask for icon: 0x120fafe window id # of group leader: 0x189 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x4, 0x0, 0x32f744, 0x7e086648 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG WM_NORMAL_HINTS(WM_SIZE_HINTS): program specified location: 52, 173 program specified minimum size: 638 by 127 program specified maximum size: 638 by 127 window gravity: Static WM_TRANSIENT_FOR(WINDOW): window id # 0x189 XdndAware(ATOM) = ATOM _NET_WM_PID(CARDINAL) = 6021 WM_LOCALE_NAME(STRING) = en_US.utf8 WM_CLIENT_MACHINE(STRING) = alpha WM_CLASS(STRING) = GP5.exe, Wine WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, _NET_WM_PING, WM_TAKE_FOCUS More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=345 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 [EMAIL PROTECTED]
[awesome bugs] #341 - wine windows loose keyboard focus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#341 - wine windows loose keyboard focus User who did this - Julien Danjou (jd) -- Can you paste me the result of xprop on one of the guilty window? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=341#comment792 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 [EMAIL PROTECTED]
[awesome bugs] #346 - Apps running from awful.spawn have niceness 5
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Andre Ramaciotti (andre.ramaciotti) Attached to Project - awesome Summary - Apps running from awful.spawn have niceness 5 Task Type - Bug Report Category - awful Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.0 Due in Version - Undecided Due Date - Undecided Details - If I run an application using awful.spawn, its niceness is set to 5 (either if it was started by typing in the Run: prompt or if it was started with a custom keybindig). If I run the command by any other way (e.g. the commands on .xinit before awesome), it has a niceness of 0. I searched the source for something related and I couldn't find anything. I copied a_exec() into a C file, compiled, and it ran the app with niceness set to 0, so I think it's something before the calling of a_exec(), but I can't find where. I'm running awesome 3.0 on Archlinux, kernel 2.6.27 and my shell is /bin/zsh. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=346 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 [EMAIL PROTECTED]
[awesome bugs] #346 - Apps running from awful.spawn have niceness 5
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#346 - Apps running from awful.spawn have niceness 5 User who did this - Julien Danjou (jd) -- Is awesome it self niced? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=346#comment798 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 [EMAIL PROTECTED]
[awesome bugs] #346 - Apps running from awful.spawn have niceness 5
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#346 - Apps running from awful.spawn have niceness 5 User who did this - Julien Danjou (jd) -- You use zsh, don't you? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=346#comment800 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 [EMAIL PROTECTED]
[awesome bugs] #347 - awesome: xerror: 139
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - melo (melo) Attached to Project - awesome Summary - awesome: xerror: 139 Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Hi, I use linux GNU/debian 'lenny' just updated from etch. I installed awesome (ver 2.3.3-1) by aptitude but it doesn't work. I found the following error in ~/xsession after I did put 'set -x' into '/etc/gdm/Xsession': ++ exec /usr/bin/dbus-launch --exit-with-session awesome W: awesome: xerror:139: fatal error: request code=1, error code=2 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x0 Serial number of failed request: 156 Current serial number in output stream: 476 thx melo. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=347 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 [EMAIL PROTECTED]
[awesome bugs] #346 - Apps running from awful.spawn have niceness 5
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#346 - Apps running from awful.spawn have niceness 5 User who did this - Julien Danjou (jd) -- Well, I think that this is caused by: BG_NICE (-6) C Z Run all background jobs at a lower priority. This option is set by default. from zsh. If you modify a_exec to always use /bin/sh (if it's not /bin/zsh) it should fix it. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=346#comment802 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 [EMAIL PROTECTED]
[awesome bugs] #153 - New graph style: bars
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#153 - New graph style: bars User who did this - melo (melo) -- very very nice -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=153#comment804 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 [EMAIL PROTECTED]
[awesome bugs] #347 - awesome: xerror: 139
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#347 - awesome: xerror: 139 User who did this - melo (melo) -- I did discovery that this king if error are due at something wrong about video's driver. I used ati driver and I got a problem. Now I'm using vesa driver and awesome start fine -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=347#comment805 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 [EMAIL PROTECTED]
[awesome bugs] #347 - awesome: xerror: 139
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#347 - awesome: xerror: 139 User who did this - Julien Danjou (jd) Reason for closing: Not a bug More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=347 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client. (Attachment added)
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) -- The attached file generally fixes the bug. Bug there're following strange things: [EMAIL PROTECTED]:p2~/pkg/xcb/awesome% echo 'promptbox.text = Test text...' | awesome-client W: awesome: sockets_reconnect:82: connection lost, reconnecting⦠But it works fine (promptbox widget is filled with Test text... text. But when I run command with some returned value: [EMAIL PROTECTED]:p2~/pkg/xcb/awesome% echo 'return 2+2;' | awesome-client 4 Everything's fine, no errors at all. -- One or more files have been attached. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment806 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: destroy code goes out of sync with index
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - koniu (koniu)
Attached to Project - awesome
Summary - naughty: destroy code goes out of sync with index
Task Type - Bug Report
Category - Lua libraries
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - To reproduce:
for i=1,10 do naughty.notify({text=i,timeout=3}) end
Solution:
I'm migrating from using indexes to objects.
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350
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 [EMAIL PROTECTED]
[awesome bugs] #351 - Mouse warping causes strange behaviour when moving mouse between windows
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#351 - Mouse warping causes strange behaviour when moving mouse between windows User who did this - Nigel McNie (nigel) -- Gaah, and there I was thinking that textbox with all the wording in it was just like a license agreement :/ Anyway, the problem I am having is that while the mouse pointer warps fine when I shift focus using the keyboard, behaviour is very erratic when moving the mouse around the window. I really don't want the mouse to warp at all when I'm actually moving it. To duplicate, start three or four windows, then move the mouse slowly in and out of the windows/the gaps between them. The mouse ends up warping to the top left of windows you move into (though only sometimes). What I find most confusing is that the warping code is part of hook_arrange, I wouldn't have thought that moving the mouse would cause such an event, but I guess that's just me not knowing how it should work. The only way I could think of to fix it is to know _how_ the window got focus - either by keyboard event or mouse. Would it be possible/make sense to hack hook_focus to report this information? Or if it does, change the default config to use it? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=351#comment807 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 [EMAIL PROTECTED]
[awesome bugs] #351 - Mouse warping causes strange behaviour when moving mouse between windows
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nigel McNie (nigel) Attached to Project - awesome Summary - Mouse warping causes strange behaviour when moving mouse between windows Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.0 Due in Version - Undecided Due Date - Undecided Details - You are about to report a bug. PLEASE: - Search through this bug tracking system if the bug has been already reported ; - If you see a bug in an application and you think it's awesome, test it with another window manager before reporting it ; - If you can, try to reproduce this on the latest git version available since this bug may be already fixed. If you still want to report this, write here as much information as you can. A clear explanation on how to reproduce your problem step by step is mandatory if you want your bug or request being processed. Please, make en effort to chose a correct category also. If you are running development version, please indicate the version you use (git describe). More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=351 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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) -- Thanks Konstantin. I'd prefer a patch with a cmake check for SOCK_SEQPACKET however. Anyone? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment808 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: destroy code goes out of sync with index
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 - Julien Danjou (jd) -- FWIW, you can use otable() if you want to use objects as indexes. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350#comment809 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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) -- The problem is SOCK_SEQPACKET is defined in FreeBSD, but it looks like it's not compatible with AF_UNIX, so simple check for SOCK_SEQPACKET existance is not enough to fix the bug. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment810 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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) -- So with what is it compatible?!? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment811 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: destroy code goes out of sync with index
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) -- OK, the buggy behavior is fixed in current naughty branch @ git.mercenariesguild.net. http://git.mercenariesguild.net/?p=awesome.git;a=commit;h=25a2c4cb2c6b95ae3f59a3ba518333ac5b62f05d (+ following commit to fix whitespaces). The code should be good to go upstream but it still relies on the index being passed with notification in notify() and re-set by arrange(). I'm not sure how to use otable() tbh but anyway I think I'd like to get rid of linear indexing altogether, so I will be looking into this further. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350#comment812 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: destroy code goes out of sync with index
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 - Julien Danjou (jd) -- 00:45 @jd_ koniu_: you need a serious rebase on master I think 00:46 @jd_ koniu_: the diff between master and your naughty branch starts at import commit which has been merged try this after updating master to an up to date copy of my master branch: git checkout naughty git rebase master To reapply all your patch on my new master branch and drop the ones that have been imported into master. Currently git log master..naughty has spurious commmit. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350#comment813 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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 = socket(AF_UNIX, SOCK_SEQPACKET, 0); +#else +csfd = socket(PF_UNIX, SOCK_STREAM, 0); +#endif AF_UNIX = PF_UNIX (or even PF_LOCAL, which is better according man socket, as PF_UNIX is deprecated), SOCK_SEQPACKET = SOCK_STREAM. And here: +#ifndef __FreeBSD__ if(send(csfd, msg, msg_len, MSG_NOSIGNAL | MSG_EOR) == -1) +#else +if(send(csfd, msg, msg_len, MSG_NOSIGNAL | MSG_EOF) == -1) +#endif MSG_EOR = MSG_EOF, there's illegal parameters error when send()'ing. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment814 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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 flag via SOCK_STREAM socket. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment815 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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 SOCK_STREAM. But I can test some variants later this evening: I've got Debian at work, my FreeBSD notebook is at home. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment817 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 [EMAIL PROTECTED]
[awesome bugs] #349 - Protocol not supported error while operating with Awesome via awesome-client.
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 SOCK_SEQPACKET in freebsd ? :) -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=349#comment816 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: destroy code goes out of sync with index
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: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350#comment819 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 [EMAIL PROTECTED]
[awesome bugs] #350 - naughty: popups are referenced by index rather than object
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 fixed in current git master. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=350 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 [EMAIL PROTECTED]
[awesome bugs] #352 - imagebox doesn't allow scaling images
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - koniu (koniu) Attached to Project - awesome Summary - imagebox doesn't allow scaling images Task Type - Bug Report Category - Core Status - New Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - OK, so I've been trying to do icon scaling in naughty but I can't get the image to scale properly. 1st of all image:crop_and_scale(), for scaling only, requires original w,h which I can't see how to get in Lua. I patched image.c to implement image:scale(dest_w,dest_h) and pushed it to image_scale branch on the git mirror: http://git.mercenariesguild.net/?p=awesome.git;a=commitdiff;h=0391fd6a94058ee74fb70925b99cbf8ebb055e9e Now the image is scaled, but it still fills up the imagebox which is automatically streched to available wibox size and doesn't react to imagebox.width. To better illustrate: http://img157.imageshack.us/my.php?image=200810202100311024x768sut9.png More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=352 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 [EMAIL PROTECTED]
[awesome bugs] #352 - imagebox doesn't allow scaling images
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#352 - imagebox doesn't allow scaling images User who did this - Julien Danjou (jd) Reason for closing: Implemented Additional comments about closing: commit 5e96e21c2c54f24ec664f063b56ef3264842a0b7 Author: Julien Danjou [EMAIL PROTECTED] Date: Tue Oct 21 18:29:02 2008 +0200 image: add width and height attributes Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=352 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 [EMAIL PROTECTED]
[awesome bugs] #352 - imagebox doesn't allow scaling images
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#352 - imagebox doesn't allow scaling images User who did this - koniu (koniu) More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=352 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 [EMAIL PROTECTED]
[awesome bugs] #352 - imagebox always resizes to the wibox height
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#352 - imagebox always resizes to the wibox height
User who did this - koniu (koniu)
--
image.width and image.height were added, which makes image:scale() redundant. Cool!
The remaining problem is that imagebox always scales to maximum available
height. Example: if imagebox is in a wibox 32px high and the image in it is in
fact 16x16, the image will get scaled up to 32x32 and thus become blurry. See
screenshot.
While autoscaling is nice, it would also be nice to be able to have control
over it. It could work somewhat like this:
-- 1. a pixmap is loaded into image object at its original size
img = image('path')
-- 2. image is loaded into an imagebox, which expands its canvas to the wibox
height but the pixmap is not automatically scaled.
imgbox = widget({ type = imagebox, name = imgbox })
imgbox.image = img
-- 3. if wibox.height image.height, the image should by default be vertically aligned
top. this could be changeable:
imgbox.valign = center
-- 4. to allow image to adapt to the wibox size, autoscaling could be enabled
(current default behavior)
imgbox.scale = true
I'll try to code this now. If I'm not done by tomorrow it means that I've given
up due to C not being my best friend.
--
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=352#comment820
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 [EMAIL PROTECTED]
[awesome bugs] #297 - keybord is very slow sometimes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#297 - keybord is very slow sometimes User who did this - OttoAllmendinger (OttoA) -- I have just noticed the same thing. The top command shows me that the Xorg process CPU load spikes to 20% or 30% every 5 seconds or so. I guess that might have something to do with it. When I kill xcompmgr it only spikes to 8%, but that is still too much in my opinion. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=297#comment821 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 [EMAIL PROTECTED]
[awesome bugs] #353 - Taglist doesn't have specified color when not using bautifull and no squares.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Marc (rhaamo)
Attached to Project - awesome
Summary - Taglist doesn't have specified color when not using bautifull and no
squares.
Task Type - Bug Report
Category - Tags
Status - Unconfirmed
Assigned To -
Operating System - FreeBSD
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Im' not using bautiful or wicked.
There is my taglist widget section:
mytaglist = {}
mytaglist.buttons = { button({ }, 1, awful.tag.viewonly),
button({ modkey }, 1, awful.client.movetotag),
button({ }, 3, function (tag) tag.selected = not
tag.selected end),
button({ modkey }, 3, awful.client.toggletag),
button({ }, 4, awful.tag.viewnext),
button({ }, 5, awful.tag.viewprev) }
[...]
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist.new(s, awful.widget.taglist.label.all,
mytaglist.buttons)
[...]
My colors (at the start of the config):
[...]
bg_normal = #11aa
bg_focus= #11
bg_urgent = #A1
fg_normal = #C0C189
fg_focus= #EA4C59
[...]
The problem:
There is no {back,fore}ground change, it give normals colors and don't change...
There is no squares except while the mouse is on a screen, it just view a
square for the current screen,tag.
Screenshot: http://omploader.org/vdXh4
Strangely in the screenshot irssi/web have square but music no and it contain a
term too
Config file: http://paste.sangor.net/yes/one/26
More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=353
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 [EMAIL PROTECTED]
[awesome bugs] #354 - no keyboard shortcuts after closing window
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Steffen Schulz (pepe) Attached to Project - awesome Summary - no keyboard shortcuts after closing window Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Valknut is a graphical p2p file sharing tool that also has some kind of 'systray icon' When valknut is closed and no more windows reside on the current desktop or when the virtual deskop is switched from valknut to an empty desktop, no keyboard shortcuts work anymore. I have to use the mouse to open a window, focus the other screen or do some other action with awesome to get the normal shortcuts working again. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=354 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 [EMAIL PROTECTED]
[awesome bugs] #297 - keybord is very slow sometimes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#297 - keybord is very slow sometimes User who did this - Michal Nowak (mnowak) -- Otto: What distro is it? I am on Fedora Rawhide and don't have xcompmgr, but will definitely check whether is there the 20-30% spinning. -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=297#comment822 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 [EMAIL PROTECTED]
[awesome bugs] #356 - There are two close buttons if you use window titlebars
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#356 - There are two close buttons if you use window titlebars User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 3005196d6440d9fe68007959610a76cbbc609834 Author: Julien Danjou [EMAIL PROTECTED] Date: Thu Oct 23 11:22:58 2008 +0200 awful.titlebar: use pairs instead of ipairs Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=356 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 [EMAIL PROTECTED]
[awesome bugs] #346 - Apps running from awful.spawn have niceness 5
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#346 - Apps running from awful.spawn have niceness 5 User who did this - Julien Danjou (jd) Reason for closing: Not a bug Additional comments about closing: Not a real bug, depends on the shell configuration. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=346 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 [EMAIL PROTECTED]
[awesome bugs] #357 - git-awesome leaks memory
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#357 - git-awesome leaks memory User who did this - Julien Danjou (jd) -- Hum, a quick look with valgrind did not reveal anything suspicious so far. Any bigger chance on your side? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment824 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 [EMAIL PROTECTED]
[awesome bugs] #358 - naughty: no screen height limit handling
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - koniu (koniu) Attached to Project - awesome Summary - naughty: no screen height limit handling Task Type - Bug Report Category - Core Status - New Assigned To - koniu Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Yeah, right now new popups will be displayed off screen if its all of available height is occupied by previous notifications. This is an issue most likely to occur with multiline IM notifications or with very limited screen sizes. I'm implementing premature destroy() unless the popup is sticky (ie. timeout = 0) to have the popups scroll as they come. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=358 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 [EMAIL PROTECTED]
[awesome bugs] #353 - Taglist doesn't have specified color when not using bautifull and no squares.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#353 - Taglist doesn't have specified color when not using bautifull and no squares. User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 9f8773ddfaf09ee6e3a5d7fd69a08f75b6c62469 Author: Julien Danjou [EMAIL PROTECTED] Date: Thu Oct 23 17:55:38 2008 +0200 awful.widget: fix taglist label without beautiful (FS#353) Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=353 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 [EMAIL PROTECTED]
[awesome bugs] #358 - naughty: no screen height limit handling
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#358 - naughty: no screen height limit handling User who did this - koniu (koniu) -- basic implementation: http://git.mercenariesguild.net/?p=awesome.git;a=commit;h=d68347faa3fabbbc7dee3999647bd60d8a3d51bc TODO: sticky handling -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=358#comment826 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 [EMAIL PROTECTED]
[awesome bugs] #357 - git-awesome leaks memory
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#357 - git-awesome leaks memory User who did this - Hannes Schulz (hannes) -- I'll try to figure it out, but I'm not quite proficient regarding valgrind. The problem, however, persists, I'm back to 18% RAM usage now (htop). -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=357#comment827 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 [EMAIL PROTECTED]
