<?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>8192</bug_id>
          
          <creation_ts>2015-08-21 08:53:40 +0000</creation_ts>
          <short_desc>python3.4.3 os.fork and os.waitpid (prelink related)</short_desc>
          <delta_ts>2016-12-15 16:25:26 +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>OE-Core</product>
          <component>devtools / tool chain</component>
          <version>unspecified</version>
          <rep_platform>Other</rep_platform>
          <op_sys>x86</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>9131</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>2.3 M2</target_milestone>
          <dependson>9131</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter>multisosnooley</reporter>
          <assigned_to name="Plauchu Edwin">edwin.plauchu.camacho</assigned_to>
          <cc>alejandro.hernandez</cc>
    
    <cc>anibal.limon</cc>
    
    <cc>benjamin.esquivel</cc>
    
    <cc>bjorn.bosell</cc>
    
    <cc>leonardo.sandoval.gonzalez</cc>
    
    <cc>luke.smith</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>richard.purdie</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <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>53309</commentid>
    <comment_count>0</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-21 08:53:40 +0000</bug_when>
    <thetext>Target platform: amd geode
oe-core from master

Layers:
meta
meta-yocto
meta-yocto-bsp
meta-cpc304 (https://github.com/pohmelie/meta-cpc304)

Distro: poky
BB version: 1.27.1

Build and run just fine. When I try to install something (that required compilation (!) with gcc) with &quot;python3 -m pip&quot; or &quot;python3 setup.py install&quot; then I get &quot;No child processes&quot; error. I have found the &quot;bad&quot; part: it is in distutils os.waitpid. So, I wrote simple script to reproduce the bug.

root@cpc304:~# cat yoba.py
import os 
pid = os.fork()
if pid: 
    print(&quot;parent&quot;)
    os.waitpid(pid, 0)
else:
    print(&quot;child&quot;)                                                                        
root@cpc304:~# python yoba.py                                                              
parent
child
root@cpc304:~# python3 --version
Python 3.4.3
root@cpc304:~# python3 yoba.py
parent
Traceback (most recent call last):
  File &quot;yoba.py&quot;, line 8, in &lt;module&gt;
    os.waitpid(pid, 0)
ChildProcessError: [Errno 10] No child processes
root@cpc304:~#

And it works on python2 just fine, but fails on python3.4.3. Probably it&apos;s because some patches are 3.4.2 oriented (https://github.com/openembedded/oe-core/blob/master/meta/recipes-devtools/python/python3/python-3.3-multilib.patch for example), but version is 3.4.3.

Anyway right now I&apos;m building absolutely same image but for x86_64 and will try it out with virtualbox.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53310</commentid>
    <comment_count>1</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-21 08:56:32 +0000</bug_when>
    <thetext>Oh, code was cutted out.
http://pastebin.com/Ui0Rwmfn
http://pastebin.com/cvc3TKQV</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53327</commentid>
    <comment_count>2</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-21 14:16:30 +0000</bug_when>
    <thetext>Bug does not reproduced with x86_64 build with virtualbox. Also there is some strange behaviour with multiprocessing lib. Again, only on my board and not with virtualbox.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53330</commentid>
    <comment_count>3</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-21 14:44:11 +0000</bug_when>
    <thetext>c code with fork works just fine http://pastebin.com/kJQemSzE</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53332</commentid>
    <comment_count>4</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-21 14:45:16 +0000</bug_when>
    <thetext>So, it definetly something &quot;python-side&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53352</commentid>
    <comment_count>5</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-08-24 13:54:46 +0000</bug_when>
    <thetext>python 3.3.3 from &quot;fido&quot; branch works just fine on my geode board.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53985</commentid>
    <comment_count>6</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-09-11 18:43:23 +0000</bug_when>
    <thetext>I can confirm this isn&apos;t working, while I still don&apos;t exactly know what the problem is, I know its not related to python3 entirely, I was able to track the issue down to the Glibc upgrade from 2.21 to 2.22 on (which makes sense):

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cb7368c110553dcb972480abc4a59b975677f7df

I will keep digging.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54115</commentid>
    <comment_count>7</comment_count>
      <attachid>2734</attachid>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-09-15 21:38:00 +0000</bug_when>
    <thetext>Created attachment 2734
strace_log_before_glibc_upgrade</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54116</commentid>
    <comment_count>8</comment_count>
      <attachid>2735</attachid>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-09-15 21:39:58 +0000</bug_when>
    <thetext>Created attachment 2735
strace_log_after_glibc_upgrade</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54117</commentid>
    <comment_count>9</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-09-15 21:40:32 +0000</bug_when>
    <thetext>Following up on this issue; as it is shown on the attachments (trimmed strace logs before and after the upgrade) when using gilbc 2.22 the clone() syscall is never executed, hence why the waitpid() fails afterwards, I quickly skimmed through the modified patches, but didn&apos;t see anything at first sight that could be causing this behavior, so it might be something that changed upstream on glibc.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54119</commentid>
    <comment_count>10</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-09-15 21:52:45 +0000</bug_when>
    <thetext>(In reply to comment #9)
Wow, awesome work! I have no experience with strace and such level of debugging, so I can&apos;t help, but I&apos;m glad you can.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54235</commentid>
    <comment_count>11</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-09-17 17:57:58 +0000</bug_when>
    <thetext>I&apos;m still trying!, so this also seems to be x86 specific, I tested it on my local PC using Arch Linux (x86-64) with python 3.4 and glibc 2.22 and it worked!, so I also tested it on poky x86-64 and it worked just fine, ARM works fine too, which also may indicate that its something that changed upstream, since glibc implements fork in assembly and its architecture specific.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54907</commentid>
    <comment_count>12</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-10-01 17:22:41 +0000</bug_when>
    <thetext>I tested this on Fedora 22 x86 using glibc 2.22 and python 3.4.2 and it works just fine, so I natively built python 3.4.2 on poky x86 linking to poky&apos;s glibc 2.22 and it worked fine as well, this means there&apos;s an issue with poky&apos;s Python3, either during compilation or with the patches</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>56963</commentid>
    <comment_count>13</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-12-02 20:35:34 +0000</bug_when>
    <thetext>I tried building this with GCC 4.9 just to make sure it wasn&apos;t a GCC 5.* issue, I had the same result.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57019</commentid>
    <comment_count>14</comment_count>
    <who name="Aníbal Limón">anibal.limon</who>
    <bug_when>2015-12-03 22:41:58 +0000</bug_when>
    <thetext>I tested on Jethro qemux86 python 3.4.3 and glibc 2.22 and works.

root@qemux86:~# python3.4 --version
Python 3.4.3
root@qemux86:~# cat yoba.py 
import os 
pid = os.fork()
if pid: 
    print(&quot;parent&quot;)
    os.waitpid(pid, 0)
else:
    print(&quot;child&quot;)
root@qemux86:~# python3   
python3            python3.4          python3.4m         
python3-config     python3.4-config   python3.4m-config  
root@qemux86:~# python3 yoba.py 
parent
child</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57020</commentid>
    <comment_count>15</comment_count>
    <who name="Aníbal Limón">anibal.limon</who>
    <bug_when>2015-12-03 22:55:31 +0000</bug_when>
    <thetext>hi multisosnooley,

Can you confirm that is failing on Jethro?

Regards,</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57021</commentid>
    <comment_count>16</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-12-03 22:58:55 +0000</bug_when>
    <thetext>(In reply to comment #15)
&gt; Can you confirm that is failing on Jethro?
I will try, but this will took couple of days, since board are not with me right now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57083</commentid>
    <comment_count>17</comment_count>
    <who name="">multisosnooley</who>
    <bug_when>2015-12-07 14:15:56 +0000</bug_when>
    <thetext>I&apos;ve just test jethro on my amd geode board (boot from usb stick) and simple python tests (os.fork and multiprocessing.Process) are ok. So, probably, this bug is covered by updates. I have no ability to play with python a lot (pip and libraries), since I can&apos;t install my linux build due some errors and I have no time and motivation to fix it.
But if Alejandro Hernandez still can reproduce this bug (AFAIR he can try to), then part(?) of bug is still there.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57087</commentid>
    <comment_count>18</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2015-12-07 14:48:50 +0000</bug_when>
    <thetext>Its very likely, this was fixed by the updates, I will do a bisect to check what fixed it and mark this as solved afterwards</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>57833</commentid>
    <comment_count>19</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2016-01-14 18:10:49 +0000</bug_when>
    <thetext>I just tested this on master (92cc02fe517bad0af4e493fda3331738cbcc9a26) using qemux86, and it&apos;s not working, so we&apos;re back were we started.

# python3.5 a.py 
parent
Traceback (most recent call last):
  File &quot;a.py&quot;, line 8, in &lt;module&gt;
    os.waitpid(pid, 0)
ChildProcessError: [Errno 10] No child processes</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>59296</commentid>
    <comment_count>20</comment_count>
    <who name="Benjamin Esquivel">benjamin.esquivel</who>
    <bug_when>2016-02-19 22:50:40 +0000</bug_when>
    <thetext>moving it to minor since this is a very sporadic issue. Will continue working in it though.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>60332</commentid>
    <comment_count>21</comment_count>
    <who name="Bjorn Bosell">bjorn.bosell</who>
    <bug_when>2016-03-23 11:42:33 +0000</bug_when>
    <thetext>Hi,

We recently ran into a strange issue that seems very similar.
Yocto: 2.01 (Jethro)
Python: 3.4.3
Platform: imx6 (ARM Cortex-a9)

The issue we saw was that we couldn&apos;t start new processes using multiprocess.Process in python.


We were able to work around this issue in a very odd way.
After installing an image on our target, we used smart to remove python3, and then re-installed it using a rpm package repository built from the same tree as the original image.


After playing around with installing images/rpms we managed to narrowed the problem down to os.fork() returning something very bad.
(In fact, it turned out it returned a pointer to the fork() function from libc)

When running the two different scenarios (clean image vs re-installed python3) through gdb we could see that in the case where os.fork() fails, resolve_fork() is invoked instead of fork(). And resolve_fork() returns the pointer to the actual fork() function.

We do not know why this is yet, it is still very strange, &quot;posixmodule.c&quot; from the python sources calls fork(), but for some reason, from a fresh install the function invoked is resolve_fork().</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>60338</commentid>
    <comment_count>22</comment_count>
    <who name="Bjorn Bosell">bjorn.bosell</who>
    <bug_when>2016-03-23 13:40:57 +0000</bug_when>
    <thetext>Sorry, that should be fork_resolve() rather than resolve_fork()</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>60487</commentid>
    <comment_count>23</comment_count>
    <who name="Bjorn Bosell">bjorn.bosell</who>
    <bug_when>2016-03-29 13:42:30 +0000</bug_when>
    <thetext>Looks like this may be the same problem:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9131</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>62834</commentid>
    <comment_count>24</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2016-06-09 15:33:10 +0000</bug_when>
    <thetext>(In reply to comment #23)
&gt; Looks like this may be the same problem:
&gt; https://bugzilla.yoctoproject.org/show_bug.cgi?id=9131

I can confirm this is the same problem, disabling pre-linking works , and since it is disabled as default, we shouldn&apos;t have a problem for now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>62835</commentid>
    <comment_count>25</comment_count>
    <who name="Alejandro Hernandez">alejandro.hernandez</who>
    <bug_when>2016-06-09 15:35:54 +0000</bug_when>
    <thetext>Changing the status to NEEDINFO, until the pre linking issue gets fixed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>62946</commentid>
    <comment_count>26</comment_count>
    <who name="Stephen K Jolley">sjolley.yp.pm</who>
    <bug_when>2016-06-13 22:29:54 +0000</bug_when>
    <thetext>It shouldn&apos;t be moved to NEEDINFO if it is dependent on another bug.  I have assigned it to Mark.  If is is a duplicate, it should be closed as duplicate.  Also moved it to Medium since the comments show it is not a major issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>68415</commentid>
    <comment_count>27</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2016-11-17 16:29:37 +0000</bug_when>
    <thetext>Could you retest this please? We enabled prelink for x86 again in August with updates to fix some of these issues.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>69131</commentid>
    <comment_count>28</comment_count>
    <who name="Plauchu Edwin">edwin.plauchu.camacho</who>
    <bug_when>2016-12-14 17:54:39 +0000</bug_when>
    <thetext>I Ran it again
Setting LD_USE_LOAD_BIAS=1 when starting

Yocto: master
Python: 3.5.2
Platform: qemux86
--------------------------------------------------

sh-4.3# export LD_USE_LOAD_BIAS=1
sh-4.3# cat yoba.py
import os 
pid = os.fork()
if pid: 
    print(&quot;parent&quot;)
    os.waitpid(pid, 0)
else:
    print(&quot;child&quot;)
sh-4.3# python3 yoba.py
parent
child</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>69132</commentid>
    <comment_count>29</comment_count>
    <who name="Plauchu Edwin">edwin.plauchu.camacho</who>
    <bug_when>2016-12-14 17:58:23 +0000</bug_when>
    <thetext>
I&apos;ve forgotten to add the revision ( 14539203655913b3304bf98d2dd1f2e1fed3d7ca )</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>69161</commentid>
    <comment_count>30</comment_count>
    <who name="Plauchu Edwin">edwin.plauchu.camacho</who>
    <bug_when>2016-12-15 16:25:26 +0000</bug_when>
    <thetext>We have set LD_USE_LOAD_BIAS with value 1 as per resolution in bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=9131

*** This bug has been marked as a duplicate of bug 9131 ***</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>2734</attachid>
            <date>2015-09-15 21:38:00 +0000</date>
            <delta_ts>2015-09-15 21:38:00 +0000</delta_ts>
            <desc>strace_log_before_glibc_upgrade</desc>
            <filename>file_8192.txt</filename>
            <type>text/plain</type>
            <size>845</size>
            <attacher name="Alejandro Hernandez">alejandro.hernandez</attacher>
            
              <data encoding="base64">MzU2ICAgcmVhZCgzLCAiIyEvdXNyL2Jpbi9weXRob24zXG5pbXBvcnQgb3NcbnBpZCA9IG9zLmZv
cmsoKVxuaWYgcGlkOiBcbiAgICBwcmludChcInBhcmVudFwiKVxuICAgIG9zLndhaXRwaWQocGlk
LCAwKSAgIFxuZWxzZTpcbiAgICBwcmludChcImNoaWxkXCIpXG4iLCAxMDI0KSA9IDEyNQ0KMzU2
ICAgX2xsc2VlaygzLCAwLCBbMF0sIFNFRUtfU0VUKSAgICAgID0gMA0KMzU2ICAgcmVhZCgzLCAi
IyEvdXNyL2Jpbi9weXRob24zXG5pbXBvcnQgb3NcbnBpZCA9IG9zLmZvcmsoKVxuaWYgcGlkOiBc
biAgICBwcmludChcInBhcmVudFwiKVxuICAgIG9zLndhaXRwaWQocGlkLCAwKSAgIFxuZWxzZTpc
biAgICBwcmludChcImNoaWxkXCIpXG4iLCAxMDI0KSA9IDEyNQ0KMzU2ICAgcmVhZCgzLCAiIiwg
MTAyNCkgICAgICAgICAgICAgICAgID0gMA0KMzU2ICAgY2xvc2UoMykgICAgICAgICAgICAgICAg
ICAgICAgICAgID0gMDM1NiAgIA0KbXVubWFwKDB4Yjc3ZDYwMDAsIDQwOTYpICAgICAgICAgID0g
MA0KMzU2ICAgY2xvbmUoY2hpbGRfc3RhY2s9MCwgZmxhZ3M9Q0xPTkVfQ0hJTERfQ0xFQVJUSUR8
Q0xPTkVfQ0hJTERfU0VUVElEfFNJR0NITEQsIGNoaWxkX3RpZHB0cj0weGI3N2QzNzY4KSA9IDM1
Nw0KMzU3ICAgc2V0X3JvYnVzdF9saXN0KDB4Yjc3ZDM3NzAsIDEyKSAgID0gMA0KMzU3ICAgd3Jp
dGUoMSwgImNoaWxkXG4iLCA2IDx1bmZpbmlzaGVkIC4uLj4NCjM1NiAgIHdyaXRlKDEsICJwYXJl
bnRcbiIsIDcpICAgICAgICAgICA9IDcNCjM1NiAgIHdhaXRwaWQoMzU3LCAgPHVuZmluaXNoZWQg
Li4uPg0KMzU3ICAgPC4uLiB3cml0ZSByZXN1bWVkPiApICAgICAgICAgICAgID0=
</data>

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>2735</attachid>
            <date>2015-09-15 21:39:58 +0000</date>
            <delta_ts>2015-09-15 21:39:58 +0000</delta_ts>
            <desc>strace_log_after_glibc_upgrade</desc>
            <filename>file_8192.txt</filename>
            <type>text/plain</type>
            <size>817</size>
            <attacher name="Alejandro Hernandez">alejandro.hernandez</attacher>
            
              <data encoding="base64">MzU3ICAgbW1hcDIoTlVMTCwgNDA5NiwgUFJPVF9SRUFEfFBST1RfV1JJVEUsIE1BUF9QUklWQVRF
fE1BUF9BTk9OWU1PVVMsIC0xLCAwKSA9IDB4Yjc3OTkwMDANCjM1NyAgIHJlYWQoMywgIiMhL3Vz
ci9iaW4vcHl0aG9uM1xuaW1wb3J0IG9zXG5waWQgPSBvcy5mb3JrKClcbmlmIHBpZDogXG4gICAg
cHJpbnQoXCJwYXJlbnRcIilcbiAgICBvcy53YWl0cGlkKHBpZCwgMCkgICBcbmVsc2U6XG4gICAg
cHJpbnQoXCJjaGlsZFwiKVxuIiwgMTAyNCkgPSAxMjUNCjM1NyAgIF9sbHNlZWsoMywgMCwgWzBd
LCBTRUVLX1NFVCkgICAgICA9IDANCjM1NyAgIHJlYWQoMywgIiMhL3Vzci9iaW4vcHl0aG9uM1xu
aW1wb3J0IG9zXG5waWQgPSBvcy5mb3JrKClcbmlmIHBpZDogXG4gICAgcHJpbnQoXCJwYXJlbnRc
IilcbiAgICBvcy53YWl0cGlkKHBpZCwgMCkgICBcbmVsc2U6XG4gICAgcHJpbnQoXCJjaGlsZFwi
KVxuIiwgMTAyNCkgPSAxMjUgICAgICAgICAgICAgICAgICAgICAgICANCjM1NyAgIHJlYWQoMywg
IiIsIDEwMjQpICAgICAgICAgICAgICAgICA9IDANCjM1NyAgIGNsb3NlKDMpICAgICAgICAgICAg
ICAgICAgICAgICAgICA9IDANCjM1NyAgIG11bm1hcCgweGI3Nzk5MDAwLCA0MDk2KSAgICAgICAg
ICA9IDANCjM1NyAgIHdyaXRlKDEsICJwYXJlbnRcbiIsIDcpICAgICAgICAgICA9IDcNCjM1NyAg
IHdhaXRwaWQoMTE4ODA1NTgyNCwgMHhiZmFkMjUxYywgMCkgPSAtMSBFQ0hJTEQgKE5vIGNoaWxk
IHByb2Nlc3NlcykNCjM1NyAgIHdyaXRlKDIsICJUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwg
bGFzdCk6XG4iLCAzNSkgPSAzNQ==
</data>

          </attachment>
      

    </bug>

</bugzilla>