Bug 308

Summary: [qemux86-64] keyboard pop up when clicking terminal icon
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Edwin Zhai <edwin.zhai>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, kevin.tian, kunwei.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, xianchao.zhang
Version: 0.9   
Target Milestone: 0.9 M4   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Jiajun Xu 2010-09-10 08:32:43 UTC
Testing Env:    
Host: Ubuntu 10.04.1 LTS
Kernel: Linux vt-dp4 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC
2010 x86_64 GNU/Linux
Poky gitinfo(used to build qemu-native):
6c3df3a7a02986d21ca09a9e914ffb2a64548752
(ssh://git@git.pokylinux.org/poky-contrib.git:remotes/origin/builds/milestone)
All images file from http://autobuilder.pokylinux.org/milestone/20100909-1/.

The phenomenon is strange, that when I click terminal icon in qemux86-64 image, keyboard will pop up with terminal. It only happens the first time I click the terminal icon and won't happen again after that even I click terminal icon several time. To reproduce the issue again, I need to reboot the image.

The issue does not exist on qemux86 or netbook/e-Menlow as I know.

Reproduce Steps:
1. Download x86-64 images from autobuilder
2. Startup images and click terminal icon
Comment 1 Edwin Zhai 2010-09-13 18:08:56 UTC
/etc/X11/Xsession.d/80matchboxkeyboard.shbg will start matchbox-keyboard as daemon, if $HAVE_KEYBOARD = "0". It's reasonable, as we need a software keyboard if the machine doesn't have physical keyboard.

These type of env var are set in /etc/formfactor/machconfig, then parsed by /etc/formfactor/config.

Root cause of this bug is that "machconfig" is missing on qemux86-64, so that matchbox-keyboard is always started as daemon after assuming $HAVE_KEYBOARD = "0".

Fix will be out soon.
Comment 2 Edwin Zhai 2010-09-20 00:21:26 UTC
Got fixed @ 8e9caafd0b94016568d.
Comment 3 Jiajun Xu 2010-09-21 09:51:40 UTC
Verified with 20100920 build, the bug is fixed. commit info, 03d9669cbcc35a49120b9cc277723bccd93f4cf3.