Virtual keyboard does not work for some applications, other problems

[AaronL]

Bug detailed description:
--------------------------
I have tried out various GUI applications in both the emulation environment and on the Samsung Q1 Ultra with a Live USB image, and I have discovered four different applications for which the virtual keyboard (VK) doesn't work. These applications are xvncviewer, xtightvncviewer, chimera2 (a Web browser), and axe. I believe that Tight VNC derives from a similar source base as the regular VNC viewer, so the cause of the problem with xvncviewer is probably the same as with xtightvncviewer. Basically, after connecting to a remote desktop with xvncviewer, causing the VK to come up and clicking on the VK doesn't do anything. The same problem occurs for axe and chimera2.

With xvncviewer and xtightvncviewer, there are also additional problems. After hitting F8 (from a hardware keyboard) to cause the pop-up menu to be displayed, click on the show fullscreen menu entry. This will cause the VNC window to disappear, but it can be seen, by using ps from the terminal, that xvncviewer is still running.

Note that all four of these apps aren't recognized by the task bar (when started from mobile-basic-player--if started from an xterm, the task bar notices them). This problem occurs for many different applications, not just these four, and is my understanding that this problem is already known.

Note also that the vast majority of applications work fine with the VK, including Tcl/Tk applications, Qt, Gtk (without hildonization), pure X (such as rdesktop), and more. The problem might be with the four applications and not matchbox, but it's hard to say without doing some debugging. The hardware keyboard works fine for all these apps.

Reproduce steps:
----------------
To reproduce this for any of the four apps, first use apt-get install to install the respective app (i.e. apt-get install xvncviewer). Then either modify the configuration for mobile-basic-player to launch it from the flash app or start up a terminal/xterm window and launch from there. For the steps mentioned in the "detailed description" section above.

Current result:
----------------
VK doesn't work with certain applications, plus the other problems listed above.

Expected result:
----------------
VK works with the applications, plus the other issues are fixed.

Basic root-causing log:
----------------------

[AaronL (aaron-n-levinson)]

Note that the problem can quickly be reproduced by VNCing into a Samsung Q1 Ultra that I have setup with x11vnc, at mobile-4395.jf.intel.com . All four apps are installed, and xvncviewer can be accessed from the mobile-basic-player app.

[Horace (horace-li)]

reassign to Han,Jian on debugging.

[jian (jian-han)]

I see the same issue found by Levinson. I have no ideas to fix it.
But I want to comment some guesses.

In the readme of matchbox-keyboard, I find this:"matchbox-keyboard never wants to get keyboard focus itself, if the window manager gives it focus ( matchbox-keyboard requests the w-m doesn't ), it wont work. "(http://svn.o-hand.com/repos/matchbox/trunk/matchbox-keyboard/README)

I guess the app Levinson mentioned is somehow unique. Matchbox windows manager cannot get the active focus properly. Matchbox-keyboard may get the focus and lead to the issue.

[yanglei (lei-a-yang)]

I reassign owner to Bob because Jian has finished his internship.

[cathyli (cathy-li)]

Checked the issu in latest image on Q1 ultra, Virtual keyboard works well for applications mentioned here: xvncviewer, xtightvncviewer, chimera2 (a Web browser), and axe.
Press F11 in real keyboard to fullscreen, no issues happended on xvncviewer and xtightvncviewer. So I think the issue has been fixed.
But when launch xvncviewer and xtightvncviewer in terminal, the pop-up menu doesn't has title, is it possible to push the minor issue fixed?

[cathyli (cathy-li)]

The issue is fixed. I change status to Fix released.
Pls. change the status to "Fix committed" if it is fixed next time, then I will verify it.

[AaronL (aaron-n-levinson)]

I tested xvncviewer on a Crownbeach system, and the problem is definitely not fixed. Press F8 in xvncviewer to bring up the menu, and then navigate to full-screen. The window disappears.

[cathyli (cathy-li)]

Bob, any updates about the bug? If the bug priority is High, it should be fixed in M9. If you haven't enough time to fix it, suggest to lower the importance.

[cathyli (cathy-li)]

Due the applications are 3rd party software, QA suggest to lower the importance to "Medium", or else, it must be fixed in M9.