Zombie printer icon remains after printing
Bug #1264811 reported by
Ian Hilliard
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux Mint |
New
|
Undecided
|
Unassigned |
Bug Description
Using Linux Mint Mate 16 (olivia) on a Lenovo G500S with quad core i5 and 4GB memory.
When printing, the printer icon appears normally in the system tray. Instead of the icon being removed at the end of the print job, it remains as a zombie printer icon in the system tray. It is not possible to remove it without killing the X-session. Further print jobs no longer give the ability to check the status using the icon as this is just a zombie left from the first print job. This happens every time the computer is used to print.
no longer affects: | ubuntu |
To post a comment you must log in.
I also have this problem, using Linux Mint Mate 16.
I have run /usr/bin/ system- config- printer- applet --debug and received the following output:
checking for jobs proxies: Introspect error on :1.45:/ org/fedoraproje ct/Config/ Printing: dbus.exceptions .DBusException: org.freedesktop .DBus.Error. NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. .DBus.Error. NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
checking for jobs
Starting job applet
ERROR:dbus.
org.freedesktop
The error comes after the job was printed. While it is printing, it is possible to click on the printer icon and see the print queue. After printing, this error occurs and the icon stays there, unusable. The printer is obviously accessible as the job does print.
I don't see anything of interest in /var/log/syslog. Synaptic says apparmor is not installed on my machine.
It would be really nice to have this functionality back as it has worked well for me for the last few years on other machines without a problem. It feels like a step backwards.
Thanks,
John