Bug 565930

The interesting point is that after adding signal handling for the error:

----------------------------------------------------------------------

diff --git a/plugins/patches/app/models/resolvable.rb b/plugins/patches/app/models/resolvable.rb
index 09b1795..7b9acc3 100644
--- a/plugins/patches/app/models/resolvable.rb
+++ b/plugins/patches/app/models/resolvable.rb
@@ -7,6 +7,23 @@ require 'thread'
 
 require 'exceptions'
 
+class PackageKitError < BackendException
+  def initialize(description)
+    @description = description
+    super("PackageKit error")
+  end
+
+  def to_xml
+    xml = Builder::XmlMarkup.new({})
+    xml.instruct!
+
+    xml.error do
+      xml.type "PACKAGEKIT_ERROR"
+      xml.description @description
+    end
+  end
+end
+
 class Resolvable
 
   attr_accessor   :resolvable_id,
@@ -124,7 +141,18 @@ public
       proxy = transaction_iface.object
     
       proxy.on_signal(signal.to_s, &block)
-      proxy.on_signal("Error") {|u1,u2| dbusloop.quit }
+      proxy.on_signal("ErrorCode") {|u1,u2| 
+        error_string = "#{u1}: #{u2}"
+        Rails.logger.error error_string
+        dbusloop.quit 
+        raise PackageKitError.new(error_string) 
+      }
+      proxy.on_signal("RepoSignatureRequired") {|u1,u2,u3,u4,u5,u6,u7,u8| 
+        error_string = "Repository #{u2} needs to be signed"
+        Rails.logger.error error_string
+        dbusloop.quit 
+        raise PackageKitError.new(error_string) 
+      }
       proxy.on_signal("Finished") {|u1,u2| dbusloop.quit }
       # Do the call only when all signal handlers are in place,
       # otherwise Finished can arrive early and dbusloop will never

---------------------------------------------------------------------

Following exception will be generated:

<error>
<type>GENERIC</type>
<description>return can't jump across threads</description>
<bug type="boolean">true</bug>
−
<backtrace type="array">
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/bus.rb:339:in `introspect_data'
</line>
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/bus.rb:507:in `call'
</line>
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/bus.rb:507:in `process'
</line>
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/bus.rb:468:in `send_sync'
</line>
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/bus.rb:335:in `introspect_data'
</line>
−
<line>
/usr/lib/ruby/site_ruby/1.8/dbus/introspect.rb:444:in `introspect'
</line>
−
<line>
/usr/local/src/rails/rest-service/webservice/../plugins/patches/app/models/resolvable.rb:58:in `packagekit_connect'
</line>
−
<line>
/usr/local/src/rails/rest-service/webservice/../plugins/patches/app/models/resolvable.rb:139:in `execute'
</line>
−
<line>
/usr/local/src/rails/rest-service/webservice/../plugins/patches/app/models/patch.rb:15:in `find'
</line>
−
<line>
/usr/local/src/rails/rest-service/webservice/../plugins/patches/app/controllers/patches_controller.rb:45:in `index'

I cannot reproduce it anymore on my machine after applying commit cde1b8ff40f87a9f3021de7a75878c42461962d1.

But it didn't help for Schubi.

Martin, the last time when it hung at my machine it was stuck somewhere in ruby-dbus code. Unfortunately I have lost the backtrace.

The URL for Lada's commit is http://gitorious.org/opensuse/yast-rest-service/commit/cde1b8ff40f87a9f3021de7a75878c42461962d1

This could be a duplicate of bug 579001 but we should try to reproduce the bug anyway.

Stefan, can you still reproduce it ?

Wwith RC3 the system reports "your system is ok" although there is a patch for
installation. This patch will be shown after I have added the key with zypper again.

The problem from comment #5 is a duplicate of bug bnc#559233 (which just has been fixed).

Schubi, could you still reproduce the original problem (DBus hang)? Please, close the bug if not.

No I cannot. So I close. Thanks