There's no rule of what the client service names should be. The only service name that matters is the watcher.
The others register to the watcher so we can get their service name then. David On 9 May 2017 00:41, "Calvin Lee" <cyrus...@gmail.com> wrote: > It seems that other applications use the "Unique DBus name" (example ":1.12") > only or service names which don't obey the naming rule. Nice catch! I think that this is the fault of the "xembed-sni-proxy" that translates xembed programs to the SNI protocol. Native StatusNotifier programs like Konversation use "org.kde.StatusNotifierItem-PID-ID". So even for KDE's version of the protocol I think it's a bug. -Calvin Lee
