<?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>2324</bug_id>
          
          <creation_ts>2012-04-18 01:48:59 +0000</creation_ts>
          <short_desc>[Build Appliance] &quot;Run image&quot; not workable in Hob</short_desc>
          <delta_ts>2012-05-08 15:40:59 +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>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>(1.2) Saul/RP, please update the SRCREV in self-hosted-image.bb again just before 1.2 is released  (Apr 18, 2012)</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.2 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jiajun Xu">jiajun.xu</reporter>
          <assigned_to name="Saul Wold">sgw</assigned_to>
          <cc>dexuan.cui</cc>
    
    <cc>dongxiao.xu</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>20609</commentid>
    <comment_count>0</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-04-18 01:48:59 +0000</bug_when>
    <thetext>tree/branch: poky/master
commit: 720fe9e371eef16da19df0885188aa0341ad2090

When I finish a qemu build with Hob in build applicance, if I click &quot;Run Image&quot;, there is no xterm window pop up and no qemu window pop up. Some error logs printed in Hob as below:

sh-4.2$ hob
** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
Traceback (most recent call last):
  File &quot;/home/builder/poky/bitbake/lib/bb/ui/crumbs/imagedetailspage.py&quot;, line 391, in run_button_clicked_cb
    self.builder.runqemu_image(image_name)
  File &quot;/home/builder/poky/bitbake/lib/bb/ui/crumbs/builder.py&quot;, line 938, in runqemu_image
    subprocess.Popen(shlex.split(cmdline))
  File &quot;/usr/lib/python2.7/subprocess.py&quot;, line 679, in __init__
    errread, errwrite)
  File &quot;/usr/lib/python2.7/subprocess.py&quot;, line 1228, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20611</commentid>
    <comment_count>1</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2012-04-18 02:23:00 +0000</bug_when>
    <thetext>This is a known issue. Saul has fixed it in poky master.
Unluckily we haven&apos;t updated the SRCREV  in self-hosted-image.bb.

I have reminded Saul and RP about this. They&apos;ll update the variable just before RC4 (or 1.2) is released.

Now we can manually patch the bitbake in the  guest with the following 3 patches:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4be09eec6a5a25da089d8ad4fb68d2fda8149912
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9789ed626bc69f348b55cfa5f1a79abbdc994204
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=376bf4a39063c2a936d20e8269c4b7681242c1fa</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20612</commentid>
    <comment_count>2</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2012-04-18 02:33:45 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; This is a known issue. Saul has fixed it in poky master.
&gt; Unluckily we haven&apos;t updated the SRCREV  in self-hosted-image.bb.
&gt; 
&gt; I have reminded Saul and RP about this. They&apos;ll update the variable just before
&gt; RC4 (or 1.2) is released.
&gt; 
&gt; Now we can manually patch the bitbake in the  guest with the following 3
&gt; patches:
&gt; 
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4be09eec6a5a25da089d8ad4fb68d2fda8149912
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9789ed626bc69f348b55cfa5f1a79abbdc994204
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=376bf4a39063c2a936d20e8269c4b7681242c1fa

Oh, actually Saul updated the SRCREV a few hours ago:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a8c668c43a3f0e63d1072cf41a9427de2e665d36
So this bug was actually fixed if we use the latest poky master.

However, I think we should update the variable again just before 1.2 is released.
So, here I leave this bug as New and I suppose Saul will change the status appropriately.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20945</commentid>
    <comment_count>3</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2012-05-01 17:03:04 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=denzil&amp;id=d20a24310eb43fed9a3f3e75752c9ad45a18cbe4</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21192</commentid>
    <comment_count>4</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-05-08 15:40:59 +0000</bug_when>
    <thetext>Verify the bug as fixed when we test 1.2 M4 RC5.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>