http://bugzilla.novell.com/show_bug.cgi?id=502719
User mvidner@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=502719#c6
Martin Vidner
2009-05-11 17:22:03 <3> d169(2273) [y2dbus] DBusConn.cc(connect):60 Cannot register service org.opensuse.yast.SCR: Rejected send message, 1 matched rules; type="method_call", sender=":1.39" (uid=0 pid=2271 comm="ruby ./check-setup.rb ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.opensuse.yast.SCR" (uid=0 pid=2273 comm="/usr/lib/YaST2/bin/SCR_dbus_server "))
Ugh, the error message does not make sense to me. It looks like a *consequence* of not being able to register the name, not the *cause*:
is reported by y2error("Cannot register service %s: %s", service.c_str(), dbus_error.message). So the Dbus error itself should be improved to contain more details. Yast could just log a suggestion what to do (Dbus reload) to y2log.
I guess it's not possible to pass any error code back when the connection fails, the reply cannot be sent without a DBus connection.
Note that we do have a connection, we just could not register the service name. In dbus sources, bus/activation.c, handle_activation_exit_error, there does not seem to be a way to pass an error message. If we really really wanted that, we could have the service send the error via a signal on the interface o.o.y.FamousLastWords OTOH, I hope such errors only occur with improper installation during development, so the customers, having a proper RPM, will never see them[TM]. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.