<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>509</bug_id>
          
          <creation_ts>2010-10-25 05:28:21 +0000</creation_ts>
          <short_desc>Xorg and matchbox-window will SegFault when there are too many windows</short_desc>
          <delta_ts>2016-01-07 16:29:47 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>1.0</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.0 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Dexuan Cui">dexuan.cui</reporter>
          <assigned_to name="Edwin Zhai">edwin.zhai</assigned_to>
          <cc>bogdanx.a.voiculescu</cc>
    
    <cc>dexuan.cui</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>jiajun.xu</cc>
    
    <cc>ke.yu</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>maxin.john</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>ross.burton</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>Regression (Found by QA test)</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>10794</commentid>
    <comment_count>0</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-25 05:28:21 +0000</bug_when>
    <thetext>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&apos;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 &quot;cat /var/log/Xorg.0.log&quot;, we see 

[3813746.641] (II) UnloadModule: &quot;kbd&quot;
[3813746.850] (II) Qemu Tablet: Close
[3813746.851] (II) UnloadModule: &quot;evdev&quot;
[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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>10796</commentid>
    <comment_count>1</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-10-25 05:46:48 +0000</bug_when>
    <thetext>(In reply to comment #0)
&gt; Using sato image, after booting into X, 
&gt; 1) click the Keyboard program for 3 times and we can see the whole screen is
&gt; covered;
&gt; 2) chick the Connetion Manager&apos;s  About menu, we can see Xorg crashes at once
&gt; -- however, the network is still ok and we can still ssh into target and by
&gt; &quot;cat /var/log/Xorg.0.log&quot;, we see 
&gt; [3813746.641] (II) UnloadModule: &quot;kbd&quot;
&gt; [3813746.850] (II) Qemu Tablet: Close
&gt; [3813746.851] (II) UnloadModule: &quot;evdev&quot;
&gt; [3813746.865]
&gt; Backtrace:
&gt; [3813746.874] 0: /usr/bin/Xorg (xorg_backtrace+0x30) [0x80dbab0]
&gt; [3813746.878] Segmentation fault at address 0x19
&gt; [3813746.879]
&gt; Fatal server error:
&gt; [3813746.879] Caught signal 11 (Segmentation fault). Server aborting
&gt; [3813746.880]
&gt; [3813746.880]
&gt; Please consult the The X.Org Foundation support
&gt;          at http://wiki.x.org
&gt;  for help.
&gt; dmesg shows:
&gt; matchbox-window[1606]: segfault at 0 ip 49095af8 sp bf9dabc8 error 6 in
&gt; libc-2.12.so[49024000+13d000]
&gt; 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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11221</commentid>
    <comment_count>2</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-12-16 18:18:52 +0000</bug_when>
    <thetext>From Edwin:
&quot;root cause is  the wrong behavior of matchbox-keyboard, will fix it soon.&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11234</commentid>
    <comment_count>3</comment_count>
    <who name="Edwin Zhai">edwin.zhai</who>
    <bug_when>2010-12-19 04:22:33 +0000</bug_when>
    <thetext>Matchbox-keyboard is an on screen &apos;virtual&apos; or &apos;software&apos; 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 &quot;lock&quot;. 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 &quot;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 &apos;demand&apos;.&quot; So we can try this way to force end user to use it in specified way.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11297</commentid>
    <comment_count>4</comment_count>
    <who name="Edwin Zhai">edwin.zhai</who>
    <bug_when>2010-12-22 19:08:24 +0000</bug_when>
    <thetext>(In reply to comment #3)
&gt; 2. REAME says &quot;There is an applet and experiemental GTK-IM module included in
&gt; the source for launching the keyboard. The IM module allows for the keyboard to
&gt; automatically mapped / unmapped on &apos;demand&apos;.&quot; So we can try this way to force
&gt; 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 &quot;singleton&quot; 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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11316</commentid>
    <comment_count>5</comment_count>
    <who name="Edwin Zhai">edwin.zhai</who>
    <bug_when>2010-12-26 21:24:46 +0000</bug_when>
    <thetext>Got fixed in poky/master @ 4efbda84392e00829b9619ba4d8c49bdc5128606</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11357</commentid>
    <comment_count>6</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-12-29 18:01:48 +0000</bug_when>
    <thetext>(In reply to comment #4)
&gt; (In reply to comment #3)
&gt; &gt; 2. REAME says &quot;There is an applet and experiemental GTK-IM module included in
&gt; &gt; the source for launching the keyboard. The IM module allows for the keyboard to
&gt; &gt; automatically mapped / unmapped on &apos;demand&apos;.&quot; So we can try this way to force
&gt; &gt; end user to use it in specified way.
&gt; Further investigation showed SCIM is required for this, and even worse, only
&gt; gtk based application can use it. So I switch to &quot;singleton&quot; inside
&gt; matchbox-desktop, who support only one instance of an application and refuse to
&gt; start another if it claim so.
&gt; Patch has already been out.

(In reply to comment #5)
&gt; Got fixed in poky/master @ 4efbda84392e00829b9619ba4d8c49bdc5128606

Now I can only run 1 Keyboard program, so the bug doesn&apos;t exist now. Let me VERIFY the bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57614</commentid>
    <comment_count>7</comment_count>
    <who name="Maxin B. John">maxin.john</who>
    <bug_when>2016-01-07 11:09:50 +0000</bug_when>
    <thetext>[YOCTO #3093]

&quot;
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.
&quot;

https://bugzilla.yoctoproject.org/attachment.cgi?id=2921</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57642</commentid>
    <comment_count>8</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2016-01-07 16:29:47 +0000</bug_when>
    <thetext>Pretty sure this was reopened by accident, closing.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>