I'm not so sure it's a simple as that. The method is called for the object on the *system* bus, but the program providing the service needs to run in the graphical session for the user running at the console. Can D-Bus really do that?
For clarification, the applet performs two D-Bus functions:
1. The NewPrinterNotification *service*, which it provides.
2. Listening for D-Bus *signals* from CUPS, currently using the com.redhat.PrinterSpooler interface.
so there will still need to be some small C program listening out for D-Bus signals from CUPS.
I'm not so sure it's a simple as that. The method is called for the object on the *system* bus, but the program providing the service needs to run in the graphical session for the user running at the console. Can D-Bus really do that?
For clarification, the applet performs two D-Bus functions:
1. The NewPrinterNotif ication *service*, which it provides.
2. Listening for D-Bus *signals* from CUPS, currently using the com.redhat. PrinterSpooler interface.
so there will still need to be some small C program listening out for D-Bus signals from CUPS.