problems understanding the output of dbus-monitor (security policy)

Havoc Pennington hp@redhat.com
Sun Jan 9 15:16:55 PST 2005


Hi,

My guess is that you and Ikke are seeing the same thing, which is that a
message with no reply expected (perhaps a signal) is somehow triggering
an UnknownMethod error. Because no reply is expected, the error is not
allowed to go back through the bus.

This shouldn't really be a problem, though it's a bug.

Havoc




More information about the dbus mailing list