Indeed. Some careful thinking needs to be done about how exactly this should work, as the NewPrinterNotification interface is actually based on the applet providing a D-Bus service -- although I said "signals" earlier, I was not being specific enough.
I don't think that D-Bus service ownership can be passed from one application to another. Perhaps the small C program needs to stay around all the time, providing the D-Bus NewPrinterNotification service on the system bus, and communicating with the applet over a similar interface on the session bus. In this way it would act as a sort of proxy for the applet. Does that make sense? -- Do not auto-start the python applet https://bugs.launchpad.net/bugs/323322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs