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 )
STATUS: FAILED
Created attachment 3026 [details] genericx86-64 on NUC
Created attachment 3027 [details] genericx86 on Minnow MAx 32 bit
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
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.
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