Bug 9174

Summary: keyboard pop up when clicking terminal icon, on SATO NUC D54250WYK
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Component: coreAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, ross.burton
Version: 2.1   
Target Milestone: 2.1 M4   
Hardware: NUC   
OS: other   
URL: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.1_M2.rc1/machines/
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)

Description Francisco Pedraza 2016-02-25 21:49:27 UTC
A keyboard pop up after clicking on terminal icon on SATO. 
Very simliar to -> Bugzilla: 1101

Prerequisite:
Install intel-corei7-64 on NUC, and boot the yocto image.
Steps to Reproduce.
1. Launch SATO image on NUC.
2. Click on a terminal.

Expected Result:
The terminal should be launched successfully.

Actual Result:
The terminal is displayed with a keyboard at bottom.

AB link: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.1_M2.rc1/machines/
Comment 1 Francisco Pedraza 2016-02-25 21:53:44 UTC
Test Enironment:
NUC D54250WYK.
Comment 2 Ross Burton 2016-02-25 22:20:11 UTC
Presumably a missing formfactor?
Comment 3 Saul Wold 2016-03-01 20:06:35 UTC
This is interesting, Ross is correct about a missing formfactor, it seems that 
meta-intel had never had a formfactor machconfig file (which sets TOUCHSCREEN 
or KEYBOARD info).  I just verified with Jethro that the soft keyboard does NOT 
appear when launching the Sato Terminal.

The change that affected this was the addition of the GTK_IM_MODUE_FILE 
location which enables the the input methods.

Would it make sense to add a check in the formfactor/config script to check for 
a USB HID keyboard IFF HAVE_KEYBOARD is not set, so if it is set we will use 
the soft keyboard regardless of a keyboard attached, but if not set by default 
we can determine by checking.
Comment 4 Ross Burton 2016-03-03 16:58:51 UTC
We decided that this should be fixed in sato directly, so I'll take this.
Comment 5 Ross Burton 2016-03-16 13:54:48 UTC
Fixed in oe-core a82ce3e477a475dccea3837eabacd9e93b873ee6.