Around 2.8 megs according to gnome-system-monitor, which is a bit more
than the other indicators and about the same as indicator-messages.
I wonder where that comes from, indicator-printers is really only
listening to some d-bus messages and shows a menu in the panel. I'll
have a look at it.
--
Great, thanks. Out of curiosity, what is the (idle) memory consumption
of indicator-printers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/323322
Title:
Do not auto-start the python applet
To mana
Thx, but I switched to mac :)
2012/2/17 Lars Uebernickel
> Fixed with the introduction of indicator-printers.
>
> system-config-printer-applet autostart was removed in
> 1.3.8+20120201-0ubuntu2.
>
> ** Changed in: system-config-printer (Ubuntu)
>Status: In Progress => Fix Released
>
> --
Fixed with the introduction of indicator-printers.
system-config-printer-applet autostart was removed in
1.3.8+20120201-0ubuntu2.
** Changed in: system-config-printer (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: system-config-printer (Ubuntu)
Status: New => In Progress
** Changed in: system-config-printer (Ubuntu)
Assignee: (unassigned) => Lars Uebernickel (larsu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
> 1. The NewPrinterNotification *service*, which it provides.
I don't think that incurring high startup cost associated with Python
interpreter and consuming 10M RAM *all the time* is too much cost for
providing that service.
Essentially I believe that new printer notification service must be re-
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
Hello Tim,
Tim Waugh [2009-02-02 14:12 -]:
> 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.
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 ca
"... 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
10 matches
Mail list logo
