[awesome bugs] #1030 - Wine floating windows move to the rightdown by themselves
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1030 - Wine floating windows move to the rightdown by themselves User who did this - Uli Schlachter (psychon) -- Assigning Wine class to floating fixed it for me, What does that mean? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1030#comment3827 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Daniel Hahler (blueyed)
Attached to Project - awesome
Summary - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu
Mono) makes Xorg go nuts
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - High
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I have noticed that when I use a titlebar for the clients/windows in
the awesome window manager and font_name = Ubuntu Mono 12 (size appears to be
irrelevant), LilyTerm misbehaves when I make the client fullscreen: the Xorg
process goes nuts (CPU and memory), and it seems like the LilyTerm window gets
bigger and bigger (according to the scrollbar).
Nothing is visible in the window (just the background, no cursor etc).
With latest master (in contrast to 3.5.2) there might be some flickering
visible for a short time.
When exiting fullscreen, before you would have to kill awesome, the lilyterm
window has a few pages of scrollback, with the prompt being visible at the top
and the bottom, and only blank space inbetween.
This is triggered by using font_name = Ubuntu Mono 12 in LilyTerm, and needs
the titlebars to be enabled in awesome.
*It works as expected with titlebars being off, and can be triggered by
toggling/enabling the titlebar while in fullscreen mode.*
I am using the default titlebar config for awesome (which is just disabled by
default), and toggle it using the following key binding:
awful.key({ modkey, Shift }, t, awful.titlebar.toggle),
This does not happen with gnome-terminal.
This happens with both size_hints_honor = false and unconfigured (should be
true) in awesome's settings.
I have also reported it also for LilyTerm at:
https://github.com/Tetralet/LilyTerm/issues/75
awesome v3.5.2-24-ga546367
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1214
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts User who did this - Daniel Hahler (blueyed) -- xtrace log: maximized LilyTerm, waited a few seconds, un-maximized it. -- One or more files have been attached. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1214#comment3828 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts User who did this - Uli Schlachter (psychon) Reason for closing: Not a bug Additional comments about closing: Let's start with quoting the relevant standard that lilyterm is violating (ICCCM ยง 4.2.4): The response of the client to being resized should be to accept the size it has been given and to do its best with it. Clients must not respond to being resized by attempting to resize themselves to a better size. If the size is impossible to work with, clients are free to request to change to the Iconic state. The bug comes from LilyTerm/src/window.c, function window_size_request() which calls gtk_window_resize(), something that is not allowed from within the size request handler. I do not understand why the code thinks that it has to do this. It might be possible that awesome is calculating the geometry from the size hints incorrectly. However, that still doesn't allow LilyTerm to violate the standard. (Also, I am too lazy to compile LilyTerm and add some printfs to test this and the #ifdef hell in the code already scares me) More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1214 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1215 - Getting invalid color in error log
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Tim Roes (timroes) Attached to Project - awesome Summary - Getting invalid color in error log 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 - I've get the following output in my error log nearly every second some of them: W: awesome: color_parse:58: awesome: error, invalid color 'linear:0,0:0,28:0,#BEBEBE:1,#E' W: awesome: color_init_unchecked:96: awesome: error, invalid color 'linear:0,0:0,28:0,#BEBEBE:1,#E' I have a gradient in my wibox bar and this seem to be cause by the systray. As soon as I remove the systray from the bar or give it - via bg_systray - a solid background color, no error occur (but of course, that's not a solution, since systray is useless on gradient background that way). Also the icons in the systray won't be redrawn correctly (as long as the bar doesn't have a solid background). The previous drawn isn't isn't cleared, the next icon is just drawn over the previous icon, if an icon change (e.g. volume icon): http://tinyurl.com/qxh6k34 According to Uli this is a separate bug ( https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1198#comment3825 ), so I opened an issue for it. If my config is of any relevance for this bug: https://github.com/timroes/awesome-config or more specific the bar part of my config: https://github.com/timroes/awesome-config/blob/master/conf.d/99bar.lua More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1215 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts (Attachment added)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1214 - Fullscreen with LilyTerm, awesome titlebar and specific font (Ubuntu Mono) makes Xorg go nuts User who did this - Uli Schlachter (psychon) -- The attached file (hopefully) models the behavior of LilyTerm. If this is correct, then LilyTerm is even more stupid than I thought: This has nothing to do with size hints. If some magic settings* are enabled, LilyTerm considers itself to be smarter than everyone else. Whenever it is resized to a different size than it wants to be, it just resizes itself to its prefered size. This has nothing to do with the size of characters etc. I don't even see how this could be influenced by your Ubuntu Mono font. *: This is the relevant code. Judge yourself if this is self-explanatory: // [Showing/Hiding tabs bar] and [Change the vte font] won't run the following codes. if (win_data-keep_vte_size0xa94a) -- One or more files have been attached. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1214#comment3829 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1216 - Miscalculated height for maximized client with titlebar (after restart)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Daniel Hahler (blueyed) Attached to Project - awesome Summary - Miscalculated height for maximized client with titlebar (after restart) 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 - A maximized client's height with a titlebar gets miscalculated after restarting awesome: it has the correct height, as if the titlebar were not present; disabling the titlebar results in the correct height. This does not happen with normal/tiled clients. This is likely related to or causing FS#1214, although that is triggered by using fullscreen. Awesome v3.5.2-24-ga546367 More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1216 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
