Do not auto-start the python applet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
Fix Released
|
Wishlist
|
Lars Karlitski |
Bug Description
Binary package hint: system-
s-c-p is the only Python process in a GNOME session, and it runs all the time, for a comparatively little job (essentially, doing nothing most of the time). The startup costs of firing up a Python interpreter are pretty high.
It wouldl be nice if the applet would start on demand, i. e. when the user starts a print job or a printer is connected.
Rewriting the entire applet is perhaps a bit big, but it should not run all the time. It could be called from gnome-settings-
Quoting Tim Waugh:
"It only needs to use D-Bus. Yes, using D-Bus session activation would be a good way to do it.
The small stub process would just need to listen to the system D-Bus for CUPS D-Bus signals indicating that there are jobs to watch, and for NewPrinterNotif
Changed in system-config-printer: | |
importance: | Undecided → Wishlist |
Changed in system-config-printer (Ubuntu): | |
assignee: | nobody → Lars Uebernickel (larsu) |
status: | New → In Progress |
"... or started in libgtk's print module."
This would be a bad idea, as then the applet would only be triggered if a GTK application sends a job to the printing system. The current applet listens to D-Bus messages from the CUPS daemon and from hal-cups-utils. So it gets triggered on jobs from any program, independent which toolkit it uses, if it sends a print job to CUPS all is OK.