<?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>91</bug_id>
          
          <creation_ts>2010-05-18 03:26:25 +0000</creation_ts>
          <short_desc>after successful Deploy, error message still printing</short_desc>
          <delta_ts>2010-12-21 05:58:24 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Anjuta Plugin</product>
          <component>anjuta-plugin</component>
          <version>0.9</version>
          <rep_platform>All</rep_platform>
          <op_sys>x86</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>0.9 M1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="liping Ke">liping.ke</reporter>
          <assigned_to name="liping Ke">liping.ke</assigned_to>
          <cc>jessica.zhang</cc>
    
    <cc>josh</cc>
    
    <cc>liping.ke</cc>
    
    <cc>sgw</cc>
    
    <cc>yp.ap.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>8650</commentid>
    <comment_count>0</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-05-18 03:26:25 +0000</bug_when>
    <thetext>After deploy an application successfully to the target, the error message is still printing: &quot;Error during deployment&quot;.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>8675</commentid>
    <comment_count>1</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-05-19 08:59:43 +0000</bug_when>
    <thetext>Hi, Jessica
The root cause is that when doing deploy after local_install, callback deploy_launcher_child_exited_cb will be triggered and do deploy_set_state (sp, DEPLOY_STATE_COPY); After doing deploy_do_copy, deploy_launcher_child_exited_cb will be triggered again and then do deploy_do_delete (AnjutaPluginSdk *sp). before calling the first vfs_ops, gnome_vfs_uri_new, gnome_vfs_init is not called. So uri is NULL. Some warning &quot;Did you call _gnome_vfs_configuration_init&quot; will be prompted.
When I add gnome_vfs_init before calling gnome_vfs_uri_new in plugin.c, everyting is just fine. I will send out the patch and close the bug later.
Thanks&amp; Regards,
criping

paste func desc:
gboolean    gnome_vfs_init                  (void);
If gnome-vfs is not already initialized, initialize it. This must be called prior to performing any other gnome-vfs operations, and may be called multiple times without error.
Returns :	TRUE if gnome-vfs is successfully initialized (or was already initialized).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>8955</commentid>
    <comment_count>2</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2010-07-13 04:01:39 +0000</bug_when>
    <thetext>Fixed in 0.7.1</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9492</commentid>
    <comment_count>3</comment_count>
    <who name="liping Ke">liping.ke</who>
    <bug_when>2010-09-01 00:30:49 +0000</bug_when>
    <thetext>Hi, saul
This bug is verified and checked in by Josh. The code is checked into upstream tagged with 0.7.1. The bug could be marked with &quot;verified&quot; and closed.

Thanks&amp; Regards,
criping</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>