dbus-monitor too dumb?

[Jakub Piotr Cłapa]

On 11/1/05, Havoc Pennington <hp at redhat.com> wrote:
> On Mon, 2005-10-31 at 23:17 -0600, Steev Klimaszewski wrote:
> > Hey all, I am trying to track down a possible bug here, not exactly sure
> > where to start though...
> >
> > running dbus-monitor --system, I get the following output:
> >
> > signal sender=:1.0 -> dest=(null destination)
> > interface=org.freedesktop.Hal.Device; member=PropertyModified int32 2
> > [ (dbus-monitor too dumb to decipher arg type 'r')
> >   (dbus-monitor too dumb to decipher arg type 'r')
> > ]
> >
> > and this repeats... is this intended?  or is there something that might
> > be wrong in one of my configs?  where do I start looking?
>
> Nobody has written the code for dbus-monitor to print the complex types
> like struct, I think. Nothing you can do about it except hack on
> dbus-monitor ...

You could try to use the purePython one but this would probably
require some hacking too (DBus changed a little since I've written
it). Nevertheless it knew how to parse (and display) all data that was
going through the bus.

--
Regards,
Jakub Piotr Cłapa