[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) -- Yes it does, closing the bug. Thank you very much! -- More

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) Reason for closing: Fixed More information can be found at the following URL:

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Daniel Hahler (blueyed) -- There is a pull request to fix this now:

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) -- Thanks for your comment. The problem I initially reported can be

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) -- Any fix at all for this bug? As of Debian, Awesome 3.5 is still in

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Uli Schlachter (psychon) -- Nope, no idea and no time -- More information can be found at

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Daniel Hahler (blueyed) -- Arnaud, there have been some fixes in this regard. Can you still

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Daniel Hahler (blueyed) -- Uli asked me to leave this here. This is what I am using to detect

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Uli Schlachter (psychon) -- Possible duplicate: #1101 (oh and that one is even older than this bug!)

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Patrick (fusgho) -- Besides my remarks mentioned in FS#1209, today I found the following behaviour:

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Uli Schlachter (psychon) -- FS#1209 is a duplicate of this (and is quite an interesting read

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been re-opened: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) More information can be found at the following URL:

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Arnaud Fontaine (arnau) -- I'm reopening this bug as I still have the same issue with Debian package

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Arnaud Fontaine (arnau) Attached to Project - awesome Summary - Windows not managed after changing resolution through RandR in 3.5.1 Task Type - Bug Report Category - Core

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Uli Schlachter (psychon) -- Well, the first two commits look trivially correct (just some

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1 User who did this - Uli Schlachter (psychon) -- Uhm, just the default config, no changes? Then how does the client end