Using sato image, after booting into X, 1) click the Keyboard program for 3 times and we can see the whole screen is covered; 2) chick the Connetion Manager's About menu, we can see Xorg crashes at once -- however, the network is still ok and we can still ssh into target and by "cat /var/log/Xorg.0.log", we see [3813746.641] (II) UnloadModule: "kbd" [3813746.850] (II) Qemu Tablet: Close [3813746.851] (II) UnloadModule: "evdev" [3813746.865] Backtrace: [3813746.874] 0: /usr/bin/Xorg (xorg_backtrace+0x30) [0x80dbab0] [3813746.878] Segmentation fault at address 0x19 [3813746.879] Fatal server error: [3813746.879] Caught signal 11 (Segmentation fault). Server aborting [3813746.880] [3813746.880] Please consult the The X.Org Foundation support at http://wiki.x.org for help. dmesg shows: matchbox-window[1606]: segfault at 0 ip 49095af8 sp bf9dabc8 error 6 in libc-2.12.so[49024000+13d000] BTW, the issue also happens to the emenlow image.
(In reply to comment #0) > Using sato image, after booting into X, > 1) click the Keyboard program for 3 times and we can see the whole screen is > covered; > 2) chick the Connetion Manager's About menu, we can see Xorg crashes at once > -- however, the network is still ok and we can still ssh into target and by > "cat /var/log/Xorg.0.log", we see > [3813746.641] (II) UnloadModule: "kbd" > [3813746.850] (II) Qemu Tablet: Close > [3813746.851] (II) UnloadModule: "evdev" > [3813746.865] > Backtrace: > [3813746.874] 0: /usr/bin/Xorg (xorg_backtrace+0x30) [0x80dbab0] > [3813746.878] Segmentation fault at address 0x19 > [3813746.879] > Fatal server error: > [3813746.879] Caught signal 11 (Segmentation fault). Server aborting > [3813746.880] > [3813746.880] > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > dmesg shows: > matchbox-window[1606]: segfault at 0 ip 49095af8 sp bf9dabc8 error 6 in > libc-2.12.so[49024000+13d000] > BTW, the issue also happens to the emenlow image. BTW: after the bug happens, we have to reboot the qemu via ssh, and many icons will become red crosses.
From Edwin: "root cause is the wrong behavior of matchbox-keyboard, will fix it soon."
Matchbox-keyboard is an on screen 'virtual' or 'software' keyboard, so there should be one instance at one time. If starting multiple instances of matchbox-keyboard, they will occupy the whole screen and make X window unhappy. To get the right behavior of matchbox-keyboard, there are 2 options: 1. Make matchbox-keyboard singleton, that is, only one instance can be running at one time. It requires changing source code and compete for some global "lock". I think dbus provides something like it. Unfortunately, matchbox-keyboard is low-level application that rely on only xlib and libfakekey, so depending on dbus is not a good idea. 2. REAME says "There is an applet and experiemental GTK-IM module included in the source for launching the keyboard. The IM module allows for the keyboard to automatically mapped / unmapped on 'demand'." So we can try this way to force end user to use it in specified way.
(In reply to comment #3) > 2. REAME says "There is an applet and experiemental GTK-IM module included in > the source for launching the keyboard. The IM module allows for the keyboard to > automatically mapped / unmapped on 'demand'." So we can try this way to force > end user to use it in specified way. Further investigation showed SCIM is required for this, and even worse, only gtk based application can use it. So I switch to "singleton" inside matchbox-desktop, who support only one instance of an application and refuse to start another if it claim so. Patch has already been out.
Got fixed in poky/master @ 4efbda84392e00829b9619ba4d8c49bdc5128606
(In reply to comment #4) > (In reply to comment #3) > > 2. REAME says "There is an applet and experiemental GTK-IM module included in > > the source for launching the keyboard. The IM module allows for the keyboard to > > automatically mapped / unmapped on 'demand'." So we can try this way to force > > end user to use it in specified way. > Further investigation showed SCIM is required for this, and even worse, only > gtk based application can use it. So I switch to "singleton" inside > matchbox-desktop, who support only one instance of an application and refuse to > start another if it claim so. > Patch has already been out. (In reply to comment #5) > Got fixed in poky/master @ 4efbda84392e00829b9619ba4d8c49bdc5128606 Now I can only run 1 Keyboard program, so the bug doesn't exist now. Let me VERIFY the bug.
[YOCTO #3093] " Bogdan Alexandru Voiculescu 2016-01-07 09:36:54 UTC Created attachment 2921 [details] keyboard screenshot Actually it seems you can open any number of keyboards. I have not found any way of closing them. " https://bugzilla.yoctoproject.org/attachment.cgi?id=2921
Pretty sure this was reopened by accident, closing.