[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: lsdbus: recursively dump all DBus services/paths/methods
From:       Arnold Krille <kde () arnoldarts ! de>
Date:       2009-08-10 10:47:35
Message-ID: 200908101247.40344.kde () arnoldarts ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 10 August 2009 11:51:37 Melchior FRANZ wrote:
> * Thiago Macieira -- Monday 10 August 2009:
> > You should print the services that :1.58 has. They appear after :1.58 and
> > are all prefixed with a space.
> There's another reason why I didn't want to scan the colon services,
> besides being volatile and, thus, not usable in scripts: qdbus occasionally
> hung there for a while and then reported "Cannot introspect object / at
> :1.2366:" etc., or even "Service ':1.7844' does not exist."

These are apps that connect to dbus as client-only. They don't provide any 
service, so no introspection...

> > To make your life easier, I'd reverse the output of qdbus (pipe through
> > tac) so that you get all names followed by the unique name (the : name).
> > You scan the unique name and if you get your match, you print all names
> > you've stored.
> Ah, so all "space" services after a colon service (and before the next
> colon service) are just different references to the same service? So in the
> following part, krunner and screensaver are the same service? Or at least
> all of them share that same part that's otherwise known as :1.19?
>   :1.19
>    org.freedesktop.ScreenSaver
>    org.kde.krunner
>    org.kde.screensaver

I don't know. Here re-starting qdbusviewer gives a different order each time...

Have fun,

Arnold

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]