Bug 9027

Summary: Virtual keyboard pop up automatically when click Terminal on qemumips64
Product: [Yocto Project Subprojects] Sato Reporter: Yi Zhao <yi.zhao>
Component: satoAssignee: Maxin B. John <maxin.john>
Status: VERIFIED FIXED QA Contact: Yi Zhao <yi.zhao>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, ke.zou, maxin.baby.john, maxin.john, richard.purdie, yi.zhao
Version: 2.1   
Target Milestone: 2.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
qemumips64 none

Description Yi Zhao 2016-02-02 06:59:48 UTC 
Created attachment 2960 [details]
qemumips64

Image location: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc1/machines/qemu/qemumips64

Git rev: master/3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c

On qemumips64, when start Terminal, the virtual keyboard pop up automatically. Please see the attachment.

This issue doesn't exist in 2.1 M1. I simply guess it related with bug 6774 

BTW: There is another bug for qemumips64, When running an application, click 'Home' icon can not back to desktop.
Comment 1 Yi Zhao 2016-02-02 07:03:11 UTC 
Update: This issue also happens on beaglebone sato-sdk image
Comment 2 Maxin B. John (inactive) 2016-02-02 10:24:00 UTC 
Automatic pop up of the virtual keyboard is the default behaviour for machines without physical keyboard. 

If we want to use the physical keyboard instead of the virtual one, we need to specify "HAVE_KEYBOARD=1" in the file:
"/etc/formfactor/machconfig"

At present, we don't have machconfig files for qemumips64 and beaglebone MACHINES in the formfactor package. I will send a patch to fix it.
Comment 3 Maxin B. John 2016-02-02 11:04:56 UTC 
patch sent to the oe-core Mailing List:
http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116648.html
Comment 4 Maxin B. John 2016-02-02 16:53:49 UTC 
Hi,

One review question was whether it is ok to declare that "Beaglebone" board has a physical keyboard and mouse by default or not (In my personal Beaglebone (BBB) board, I generally attach keyboard and mouse) 

http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116652.html

Please let us know if this settings for Beaglebone looks reasonable to you ?

"
HAVE_TOUCHSCREEN=1
HAVE_KEYBOARD=1

DISPLAY_CAN_ROTATE=0
DISPLAY_ORIENTATION=0
DISPLAY_WIDTH_PIXELS=640
DISPLAY_HEIGHT_PIXELS=480
DISPLAY_BPP=16
DISPLAY_DPI=150
"
Comment 5 Yi Zhao 2016-02-03 02:12:53 UTC 
(In reply to comment #4)
> Hi,
> 
> One review question was whether it is ok to declare that "Beaglebone" board
> has a physical keyboard and mouse by default or not (In my personal
> Beaglebone (BBB) board, I generally attach keyboard and mouse) 


Usually I also attach the usb keyboard and mouse for some matchbox desktop testing and I don't have touchscreen.

> 
> http://lists.openembedded.org/pipermail/openembedded-core/2016-February/
> 116652.html
> 
> Please let us know if this settings for Beaglebone looks reasonable to you ?
> 
> "
> HAVE_TOUCHSCREEN=1
> HAVE_KEYBOARD=1
> 
> DISPLAY_CAN_ROTATE=0
> DISPLAY_ORIENTATION=0
> DISPLAY_WIDTH_PIXELS=640
> DISPLAY_HEIGHT_PIXELS=480

Does this mean it will use this fixed resolution even on a large display ?


Thanks,
Yi
 
> DISPLAY_BPP=16
> DISPLAY_DPI=150
> "
Comment 6 Maxin B. John 2016-02-03 09:44:24 UTC 
Hi,

(In reply to comment #5)
> (In reply to comment #4)
> > Hi,
> > 
> > One review question was whether it is ok to declare that "Beaglebone" board
> > has a physical keyboard and mouse by default or not (In my personal
> > Beaglebone (BBB) board, I generally attach keyboard and mouse) 
> 
> 
> Usually I also attach the usb keyboard and mouse for some matchbox desktop
> testing and I don't have touchscreen.

Ok.
 
> > 
> > http://lists.openembedded.org/pipermail/openembedded-core/2016-February/
> > 116652.html
> > 
> > Please let us know if this settings for Beaglebone looks reasonable to you ?
> > 
> > "
> > HAVE_TOUCHSCREEN=1
> > HAVE_KEYBOARD=1
> > 
> > DISPLAY_CAN_ROTATE=0
> > DISPLAY_ORIENTATION=0
> > DISPLAY_WIDTH_PIXELS=640
> > DISPLAY_HEIGHT_PIXELS=480
> 
> Does this mean it will use this fixed resolution even on a large display ?

Yes, It will use "fbset" to update the resolution. We shouldn't update these values (my bad) .. Thanks!

Now, we can update the machconfig for Beaglebone as below:

HAVE_TOUCHSCREEN=0
HAVE_KEYBOARD=1

> 
> Thanks,
> Yi
>  
> > DISPLAY_BPP=16
> > DISPLAY_DPI=150
> > "
Thanks,
Maxin
Comment 7 Maxin B. John 2016-02-03 10:32:49 UTC 
v2 sent to oe-core Mailing list:
http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116830.html
Comment 9 Yi Zhao 2016-02-24 07:58:12 UTC 
Verified on qemumips64 for 2.1 M2 rc3 build. But due to bug 9131, I can't verify it on beaglebone.
Comment 10 Yi Zhao 2016-03-17 01:42:17 UTC 
Verified with 2.1_M3 RC1
git rev: master/8debfea81e69d038bd2d56314b272cb74f5582ed