Bug#719496: freeorion: input textfields doesn't work after a while.

[Yann Dirson]

Hi Markus,

On Sun, Aug 18, 2013 at 05:01:16PM +0200, Markus Koschany wrote:
> Hi Yann and Marius,
> 
> I'm in contact with the developers of FreeOrion and they asked me to relay
> a question to you.
> 
> Quote from http://www.freeorion.org/forum/viewtopic.php?f=25&t=7719
> 
> > This is still easily repeatable for me today, I can open up options, go to the
> > directories page, confirm I can type, alt-tab out, click back in, and then I 
> > cannot type (or rather, it doesn't accept my input, I think it is reading it all
> > as 'alt-a', 'alt-b', etc) until I hit the ALT key again 
> > (has to be the same one I used to alt-tab), and then everything is fine. 
> > The alt-lock does not get initiated just by hitting the alt-key a first time, 
> > it seems to only start by alt-tab. 
> 
> You can switch with ALT-Tab between different windows and FreeOrion and sometimes you
> can't type because this locks your keyboard input. Can you confirm that pressing
> ALT again in this case allows you to type again?

With the workaround I do have Al-TAB issues:

If I try hit Alt-TAB, nothing seems to happen; on second Alt-TAB press
the border of the fullscreen window flashes and I can then use desktop
shortcuts (Here Win-F1 to switch desktop, or simply Alt-TAB).  Eg
Win-F1 is completely ignored unless I hit Alt-TAB first, Alt alone is
not sufficient.  When I get back to the desktop where FreeOrion is
running, I can switch away immediately, as long as I did not click the
game first, after which I'm back into the "locked" mode.

Is that what you meant, or did you mean without the workaround ?

> Another idea:
> 
> > Reading the debian bug about the inconsistent time this problem occurs I would like to
> > know if some notification mechanism snitches away the focus of the window.
> > Maybe that is something your user should test with some x11 event tracing.
> > xtrace or xev maybe show us the relevant hint.
> 
> Can you try reproducing this bug and showing us the output of xtrace?
> 
> xtrace freeorion > xtrace.log
> 
> Perhaps another application interferes with FreeOrion and this might be a way to track
> down the issue.
> 
> Thanks in advance.
> 
> Regards,
> 
> Markus
> 
> 
> 
>