[awesome bugs] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event User who did this - rawoul (rawoul) -- I'm not sure it's the same bug but I get similar behaviour with a recent chrome and awesome 3.4.15. The Chrome window pops up on top of other windows on a different tab (on the same screen), after receiving the following event: ConfigureNotify event, serial 24, synthetic NO, window 0x1e0003e, event 0x1e0003e, window 0x1e0003e, (0,22), width 1278, height 1576, border_width 1, above 0x240036f, override NO -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275#comment4091 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] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event User who did this - rawoul (rawoul) -- Ignore my previous comment, chrome works fine with awesome 3.5.5. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275#comment4092 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] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event User who did this - rawoul (rawoul) -- The bug seems to be related to GPU drivers (see https://code.google.com/p/chromium/issues/detail?id=350522), sorry for the noise. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275#comment4094 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] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event User who did this - Uli Schlachter (psychon) -- After much foobar-ism, I managed to track this down to withcurrent being called by an xcb_generic_event at #3 0x00412e1a in event_handle_configurerequest (ev=0x1d93bd0) at /home/kde-devel/kde/src/awesome/event.c:345 You mean awful.tag.withcurrent, right? So firefox gives us a specific position for its window in a ConfigureRequest, we obey and put it at that position (which happens to be on another screen than what it is on currently) and awful.tag.withcurrent gets called due to the resulting property::screen signal. Hm. Why am I not allowed to blame firefox here? :( We could change event_handle_configurerequest() to just emit request::x, y, width, height, border_width etc signals, but (a) this would mean we would violate ICCCM (we have to take special action if we ignore the configure request) and (b) I don't see how this really helps with clients moving themselves to another screen during startup. Also, I don't see *why* firefox does this at all. If it wants to restore some saved window position, then there is a proper, non-flickering approach for doing that. So it must be doing something else...? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275#comment4080 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] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event User who did this - Emmanuel Lepage Vallee (Elv13) -- On top of that, we then ignore the x, y, width and height arguments as it is added to a tag layout and resized anyway, so the only thing that happen is the window going into a random tag with no way to enforce the rules (well, Tyrannical rules). So, the possible solutions are: 1) Add the request x, y, width and height as suggested (+ convert the x,y ones into ::screen, as they are the only ones that really affect the user of those bugus softwares) 2) Add a new client properties to disable those events, something like ignore_external_resize. This wont generally solve the problem, but there is not that many clients like that Pick one and I will send a patch. In general this should not happen, but I saw it a few time and this is the first time I digg into this. As always, my opinion is that there should be a way to prevent clients from skipping the rule system and doing whatever they want. This was the whole point of the request:: system. But leave the current behavior as the default one. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275#comment4083 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] #1275 - Unwanted accidental screen changes caused by bogus xcb_generic_event
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Emmanuel Lepage Vallee (Elv13) Attached to Project - awesome Summary - Unwanted accidental screen changes caused by bogus xcb_generic_event 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 - Ok, that one was long to debug... Long story short, I open firefox on screen 1, it flicker then move on screen 2, in the selected tag instead of the www one. Great... Why? After much foobar-ism, I managed to track this down to withcurrent being called by an xcb_generic_event at #3 0x00412e1a in event_handle_configurerequest (ev=0x1d93bd0) at /home/kde-devel/kde/src/awesome/event.c:345 if added this to client_resize_do printf(\n WINID %d From resize %d %d x %d %d w %d %d\n,c-window,screen_get_index(c-screen),screen_get_index(new_screen),old_geometry.x,geometry.x,old_geometry.width,geometry.width); and got: HERE C Mozilla Firefox TAG Internet WINID 41943231 From resize 1 1 x 1920 1920 w 1918 1918 WINID 41943231 From resize 1 1 x 1920 1920 w 1918 1918 TSTBrowser::restoreTree level = 1 tabsToRestore = 1 WINID 41943231 From resize 1 1 x 0 1920 w 1918 1918 WINID 41943231 From resize 1 2 x 1920 0 w 1918 1918 TSTBrowser::restoreTree level = 1 tabsToRestore = 1 TSTBrowser::restoreTree level = 1 tabsToRestore = 64 restoring member tabs = 64 HERE WITHCURRENT INVALID SCREEN CHANGE! sorry for all the prints with useless names, but at some point, you can see that the screen change when firefox restore the session do you think we should first check that in event.c before calling resize to prevent accidental screen changes? Or is it better to add a request::screen as suggested before to avoid this situation? More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1275 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.
