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 0x0000000000412e1a 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=details&task_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.
