Bug 6774 - Daisy 1.6.1 - matchbox-keyboard doesn't "pop up" automatically any more
Summary: Daisy 1.6.1 - matchbox-keyboard doesn't "pop up" automatically any more
Status: RESOLVED FIXED
Alias: None
Product: Matchbox
Classification: Yocto Project Subprojects
Component: matchbox (show other bugs)
Version: 2.1
Hardware: All arm
: Medium normal
Target Milestone: 2.1
Assignee: Maxin B. John
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-29 09:20 UTC by flavio.suligoi
Modified: 2016-02-02 11:16 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description flavio.suligoi 2014-09-29 09:20:28 UTC 
With the old Dylan 1.4 the matchbox-keyboard works perfectly and pops up automatically when I open a terminal window, or a web browser, or the notes application, etc.

But now, with Daisy 1.6.1 I can use the matchbox-keyboard __ONLY__ if I click manually on the keyboard icon on the matchbox-panel title-bar. It is a big problem in full screen applications (as a web browser in a "kiosk mode", for example).

It seems as the "matchbox-keyboard -d" doesn't receive any more messages from the matchbox windows manager when an application starts.

I'm using a custom i.MX53 ARM board, but the problem can be replicated using a core-image-sato (adding the matchbox-keyboard) with another standard ARM board.

Flavio
Comment 1 Tobias Andersson 2015-11-12 09:45:56 UTC 
Im having the same problem, but on the fido branch. Some tips would be helpfull
Comment 2 Maxin B. John 2015-11-12 10:28:48 UTC 
Hi,

(In reply to comment #1)
> Im having the same problem, but on the fido branch. Some tips would be
> helpfull

Is it possible to share the contents of "/etc/formfactor/machconfig" from your target rootfs ?

Maxin
Comment 3 Tobias Andersson 2015-11-12 11:01:48 UTC 
(In reply to comment #2)
> Hi,
> 
> (In reply to comment #1)
> > Im having the same problem, but on the fido branch. Some tips would be
> > helpfull
> 
> Is it possible to share the contents of "/etc/formfactor/machconfig" from
> your target rootfs ?
> 
> Maxin

No, thats not the problem. Tried running matchbox-keyboard -d from my own startscript, also tried remove HAVE_KEYBOARD from machconfig with no success
Comment 4 Maxin B. John 2015-11-12 12:13:36 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > Hi,
> > 
> > (In reply to comment #1)
> > > Im having the same problem, but on the fido branch. Some tips would be
> > > helpfull
> > 
> > Is it possible to share the contents of "/etc/formfactor/machconfig" from
> > your target rootfs ?
> > 
> > Maxin
> 
> No, thats not the problem. Tried running matchbox-keyboard -d from my own
> startscript, also tried remove HAVE_KEYBOARD from machconfig with no success

Ok, Thanks for checking it.
Comment 5 Maxin B. John 2016-01-04 15:21:25 UTC 
Sent fix for review to oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2016-January/114760.html
Comment 7 Maxin B. John 2016-02-02 11:16:15 UTC 
[YOCTO #9027]-Virtual keyboard pop up automatically when click Terminal on qemumips64

says that this patch causes the keyboard to popup if we haven't defined physical keyboard in machconfig.

However 
[YOCTO #8957] - gtk3 apps segfault after im module location fix

means, this fix causes segfault for gtk3 apps.

So, sending another fix to the oe-core Mailing List:
http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116647.html