Closed ghost closed 3 years ago
The applet is run automatically when you print, create a print queue or if a driver is going to be installed during print queue creation.
If you run it by hand, it will just check for existing print jobs and if there is any, the applet is started. If not, it returns to Glib loop and run in the loop till you kill it.
Could it be just slightly more user-friendly? I believe, nobody would expect the behaviour you just described. Perhaps, the text of the aforementioned comment could be just added verbatim to the message displayed at program execution?
The applet is not meant to be run by an user, but by printing system, so user friendliness is out of scope here.
Hello, everyone.
I'm running
system-config-printer-applet --debug
from the terminal, and getting zero feedback. The only thing that I see is:The applet does not appear, nothing happens.
System: Linux 5.4.80, xfce 4.14, cups 2.3.3, system-config-printer 1.5.13