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
Status - New
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.5.1
Due in Version - Undecided
Due Date - Undecided
Details - After upgrading from Awesome 3.4.15 to 3.5.1, I have a strange issue 
when using two monitors with RandR. At the beginning, everything is fine, then 
when I change the resolution (for example through ``xrandr --output VGA1 --mode 
1920x1080 --above LVDS1''), Awesome restarts but some windows (such as urxvt or 
Firefox) are not managed anymore (they are mapped but not displayed in the 
titlebar anymore). Moreover, when I try to change tag on the first screen 
(LVDS1) using the mouse, these windows are mapped/unmapped on the tag of the 
second screen (VGA1).

Killing Awesome while using the same X server process exhibits the same issue 
so I'm guessing this is coming from Window properties. The only difference 
between "normal" and these windows seems to be the Map State as it is 
IsUnmapped for its frame and IsUnviewable for the window itself.

I tried to investigate by trying Awesome at different revisions while leaving 
the X server running. It seems to come from 1e418cb..8348d4, before 1e418cb, 
everything works well. I must admit that I don't know the LUA code at all so I 
got stuck there.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1155

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].

Reply via email to