Bug 9254

Summary: Mismatch between genericx86 and genericx86-64 keyboards
Product: [Build System, Metadata & Runtime] BSPs Reporter: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Component: bsps-runtimeAssignee: Saul Wold <sgw>
Status: RESOLVED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium CC: ross.burton, yp.kernel.watcher, yp.watcher
Version: 2.1   
Target Milestone: 2.1 M4   
Hardware: MinnowBoard Max   
OS: x86   
URL: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M3.rc1/machines/genericx86/core-image-sato-sdk-genericx86.hddimg
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Found by QA test)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
genericx86-64 on NUC
none
genericx86 on Minnow MAx 32 bit none

Description Francisco Pedraza 2016-03-14 19:49:22 UTC 
STATUS: PASSED
BUILD: 2.1_M3.RC1: 8debfea81e69d038bd2d56314b272cb74f5582ed
ENVIRONMENT: genericx86-64 on NUC
STEPS TO REPRODUCE: 
1. launch Keyboard from SATO UI.

Note: The case is for sato image only.

EXPECTED OUTCOME: 1. user should launch the keyboard properly.
ACTUAL OUTCOME: There is a mismatch between genericx86 and genericx86-64 

poky : 8debfea81e69d038bd2d56314b272cb74f5582ed 
Core-image-sato-sdk ( genericx86 )
Comment 1 Francisco Pedraza 2016-03-14 19:50:19 UTC 
STATUS: FAILED
Comment 2 Francisco Pedraza 2016-03-14 19:51:37 UTC 
Created attachment 3026 [details]
genericx86-64 on NUC
Comment 3 Francisco Pedraza 2016-03-14 19:52:10 UTC 
Created attachment 3027 [details]
genericx86 on Minnow MAx 32 bit
Comment 4 Saul Wold 2016-03-14 20:17:12 UTC 
Possibly a difference in resolution of the 2 machines, I will try here also, 
this might move to Ross or someone in the user space to deal with
Comment 5 Saul Wold 2016-03-16 18:30:08 UTC 
This might be a matchbox issue with resolution differences between hardware, I 
was able to reproduce this using a 32bit NUC and a 64bit NUC and the 
genericx86* BSP, I was also able to reproduce this issue with intel-core* BSPs, 
so it might be related to 32 vs 64 bits issues, not hardware resolution.
Comment 6 Saul Wold 2016-03-22 14:23:14 UTC 
This issue was a 32bit vs 64bit in X and handling of return values.  The fix 
was in matchbox-keyboard along with an update to the SRCREV

Matchbox-keyboard fix: 

http://git.yoctoproject.org/cgit/cgit.cgi/matchbox-keyboard/commit/?id=3ddfdf3f86833417b0d08cc458c961d84b13f1e5

SRCREV Update:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2f2f784727a1617c2b9ce0bb86730ba301238e06