{"action":"created","issue":{"url":"https://api.github.com/repos/awesomeWM/awesome/issues/892","repository_url":"https://api.github.com/repos/awesomeWM/awesome","labels_url":"https://api.github.com/repos/awesomeWM/awesome/issues/892/labels{/name}","comments_url":"https://api.github.com/repos/awesomeWM/awesome/issues/892/comments","events_url":"https://api.github.com/repos/awesomeWM/awesome/issues/892/events","html_url":"https://github.com/awesomeWM/awesome/issues/892","id":154230886,"number":892,"title":"Clients on the second screen cover the wibox status bar","user":{"login":"aroig","id":1743143,"avatar_url":"https://avatars.githubusercontent.com/u/1743143?v=3","gravatar_id":"","url":"https://api.github.com/users/aroig","html_url":"https://github.com/aroig","followers_url":"https://api.github.com/users/aroig/followers","following_url":"https://api.github.com/users/aroig/following{/other_user}","gists_url":"https://api.github.com/users/aroig/gists{/gist_id}","starred_url":"https://api.github.com/users/aroig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aroig/subscriptions","organizations_url":"https://api.github.com/users/aroig/orgs","repos_url":"https://api.github.com/users/aroig/repos","events_url":"https://api.github.com/users/aroig/events{/privacy}","received_events_url":"https://api.github.com/users/aroig/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-05-11T12:26:07Z","updated_at":"2016-05-11T18:54:16Z","closed_at":null,"body":"I just noticed this. Clients on my second screen cover the status bar, while on the first screen they do work just fine (whatever it means first and  second, since screens just come and go now...). Besides that, the tiling is ok, according to the layout.\r\n\r\nI can reproduce it with the default configuration (no custom rc.lua). It started happening as a result of a commit in the last week or two.\r\n\r\nWhen I get the time I can try to narrow it down a bit more, but I thought I'd just report it, in case you already know where to look!"},"comment":{"url":"https://api.github.com/repos/awesomeWM/awesome/issues/comments/218555073","html_url":"https://github.com/awesomeWM/awesome/issues/892#issuecomment-218555073","issue_url":"https://api.github.com/repos/awesomeWM/awesome/issues/892","id":218555073,"user":{"login":"Elv13","id":340384,"avatar_url":"https://avatars.githubusercontent.com/u/340384?v=3","gravatar_id":"","url":"https://api.github.com/users/Elv13","html_url":"https://github.com/Elv13","followers_url":"https://api.github.com/users/Elv13/followers","following_url":"https://api.github.com/users/Elv13/following{/other_user}","gists_url":"https://api.github.com/users/Elv13/gists{/gist_id}","starred_url":"https://api.github.com/users/Elv13/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Elv13/subscriptions","organizations_url":"https://api.github.com/users/Elv13/orgs","repos_url":"https://api.github.com/users/Elv13/repos","events_url":"https://api.github.com/users/Elv13/events{/privacy}","received_events_url":"https://api.github.com/users/Elv13/received_events","type":"User","site_admin":false},"created_at":"2016-05-11T18:54:16Z","updated_at":"2016-05-11T18:54:16Z","body":"Hello,\n\nCan you try https://github.com/awesomeWM/awesome/pull/878 ? (I didn't test\nyet with multiple screens, so I have no clue if it's going to fix your\nissue or make it worst)\n\nThanks\n\nOn 11 May 2016 at 14:38, Abdó Roig-Maranges <notifications@github.com>\nwrote:\n\n> You already use the \"don't restart on RandR changes\"-stuff?\n>\n> Yes, I updated to current master this morning to make sur it still\n> happens.\n>\n> It actually works? :-)\n>\n>\n>    - I tried on my laptop (1 screen) before the weekend and seemed to\n>    work.\n>    - When I tested it today on my desktop (two screens plugged in from\n>    the begining), it mostly worked except from what I reported.\n>    - I haven't tested changing screens dynamically yet.\n>\n> Does it happen to all clients or just some special one?\n>\n> All of them on one one of the screens.\n>\n> Could you run echo 'local res = \"\" ; for s=1, screen.count() do res = res\n> .. tostring(s) .. \": \" .. require(\"gears.debug\").dump_return({geometry =\n> screen[s].geometry, workarea = screen[s].workarea}) .. \"\\n\" end return res'\n> | awesome-client and tell us if the output is what you expect (and actually\n> show us the output)? Geometry is the size of the screen, workarea is the\n> part that clients are layouted on.\n>\n> 1: table: 0x1389c60\n>   geometry : table: 0x1389d30\n>     height : 1080 (number)\n>     y : 0 (number)\n>     x : 0 (number)\n>     width : 1920 (number)\n>   workarea : table: 0x1e956e0\n>     height : 1062 (number)\n>     y : 18 (number)\n>     x : 0 (number)\n>     width : 1920 (number)\n> 2: table: 0x1ae4f20\n>   geometry : table: 0x1ae4f60\n>     height : 1080 (number)\n>     y : 0 (number)\n>     x : 1920 (number)\n>     width : 1920 (number)\n>   workarea : table: 0x1ae4fa0\n>     height : 1080 (number)\n>     y : 0 (number)\n>     x : 1920 (number)\n>     width : 1920 (number)\n>\n> The workarea of screen 2 is wrong. it should be height: 1062 like the\n> first one.\n>\n> If the workarea is actually wrong, does echo 'client.focus:struts{ top =\n> 4, bottom = 4, left = 4, right = 4}' | awesome-client fix things? (This\n> kind-of breaks the currently focused client. You should close it\n> afterwards. This is just a cheap hack to force the C code to re-compute\n> workareas)\n>\n> Yes it does.\n>\n> Thanks for your time on this!\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly or view it on GitHub\n> <https://github.com/awesomeWM/awesome/issues/892#issuecomment-218550469>\n>\n"}}