printer icon does not disappear

Bug #1291075 reported by asgard2
146
This bug affects 32 people
Affects Status Importance Assigned to Milestone
system-config-printer (Ubuntu)
Fix Released
Medium
Unassigned
Trusty
Confirmed
Medium
Unassigned

Bug Description

Hi,

I have a network printer installed, which is connected at my router.

The printer was working ever, but now (maybe after the upgrade to saucy), the printer icon freezes after a network print but printing is working.

Now I could reproduce this at a clean xubuntu vm with the current upgrades and the same happens again.

I think that is may be related to cups.

Cups error log is clear.

Xubuntu 13.10 64Bit
Kernel 3.11.0-18

UPDATE:

I append the "apport-collect" from a clean xubuntu 14.04 64bit vm, where I reproduced this bug.

I hope this can be fixed, it is annoying.

Thanks.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CupsErrorLog:

CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-05-04 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
Lpstat: device for HP-Deskjet-5550: socket://192.168.178.1:9100
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: system-config-printer (not installed)
Papersize: a4
PpdFiles: HP-Deskjet-5550: HP Deskjet 5550, hpcups 3.14.3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4eb73dcc-c1a8-4f1a-9889-793e0efd6c43 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

asgard2 (kamp000x)
description: updated
Anders (eddiedog988)
Changed in cups (Ubuntu):
status: New → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Seems that this icon is provided by system-config-printer.

Tim, can you have a look or tell the original poster which logs he should supply?

affects: cups (Ubuntu) → system-config-printer (Ubuntu)
Revision history for this message
asgard2 (kamp000x) wrote :

awaiting orders ...

Revision history for this message
asgard2 (kamp000x) wrote : BootDmesg.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
asgard2 (kamp000x) wrote : CurrentDmesg.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : Locale.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : Lspci.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : PrintingPackages.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : ProcEnviron.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : ProcInterrupts.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : ProcModules.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : UdevDb.txt

apport information

Revision history for this message
asgard2 (kamp000x) wrote : UdevLog.txt

apport information

description: updated
Revision history for this message
b3nmore (b3nmore) wrote :

In my experience this issue occurs mainly with non-local printers. Somehow the icon does not get removed from systray; a reload/restart of the panel (e.g. xfce4-panel -r) will remove it.

Revision history for this message
b3nmore (b3nmore) wrote :

Running system-config-printer-applet --debug from a terminal outputs the following after starting a print job:
checking for jobs
Starting job applet
ERROR:dbus.proxies:Introspect error on :1.91:/org/fedoraproject/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.
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.

Revision history for this message
b3nmore (b3nmore) wrote :

It seems, that scp-dbus-service is somehow effected by printing or the query of the print-applet: After login (or restart of scp-dbus-service) it can be queried by e.g.
$ qdbus --session org.fedoraproject.Config.Printing
/
/org
/org/fedoraproject
/org/fedoraproject/Config
/org/fedoraproject/Config/Printing

After the first print job (when the icon gets stuck) it does not reply anymore:
$ qdbus --session org.fedoraproject.Config.Printing
Error: 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.

Revision history for this message
b3nmore (b3nmore) wrote :

Another observation: the systray icon gets removed if one kills scp-dbus-service. However to gain normal functionality (i.e. notification upon printing) system-config-printer-applet (applet.py) has to be restarted as well.

Revision history for this message
b3nmore (b3nmore) wrote :

When I start scp-dbus-service.py with --debug, I get the attached log. After finishing the first print job it hangs at:
job-completed-successfully
Connected as user XXX
Authentication pass: 1
Authentication: password callback set
open notifications: 1
num_jobs: 1
num_jobs_when_hidden: 0
Upset printers: set([])

(which doesn't seem right) and something is blocking it (i.e. no further output on following print jobs) until it gets killed.

Revision history for this message
August Karlstrom (fusionfile) wrote :

I experience this bug as well in Lubuntu 14.04. My Samsung printer is wirelessly attatched to the local network.

Revision history for this message
apsaras (c-launchpad1) wrote :

Another non-local printer here. I'm getting the problem with with a wirelessly connected Lexmark Pro205.

Revision history for this message
apsaras (c-launchpad1) wrote :

I meant to say: I'm running Xubuntu 14.04. Printer uses device URI socket://192.168.0.3:9100

Revision history for this message
Alex Moldovan (alexmoldovan) wrote :

Same bug here on Xubuntu 14.10

Revision history for this message
Konstal (konni33100) wrote :

I can confirm the Bug on 5 different Xubuntu 14.04 Systems i'm using.

Revision history for this message
dinamich (damjan-adamic) wrote :

Same bug on Linux Mint 17 Qiana

Revision history for this message
Mark smith (zebiddy8) wrote :

Same here with two different network printers on Linux Mint 17 Qiana XFCE desktop.
The xfce4-panel -r command in a terminal window removes it OK though.

Revision history for this message
Lars Behrens (lars-behrens-u) wrote :

Confirming for Xubuntu 14.04.1

Revision history for this message
b3nmore (b3nmore) wrote :

There is a red hat bug report containing a patch, which seems to solve this issue for me on trusty:
https://bugzilla.redhat.com/show_bug.cgi?id=1116756

And here's the request for applying the path on the debian side:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756878

Revision history for this message
b3nmore (b3nmore) wrote :

I've attached a patched version for trusty, for those who want to make a quick test. Just replace the original file in /usr/share/system-config-printer/scp-dbus-service.py with attached one (and make sure it has the right permissions).

Revision history for this message
fv (fratiman-vladut) wrote :

solution #28 work for me
Thanks!!!!

Revision history for this message
asgard2 (kamp000x) wrote :

With this patch, the printer icon is gone and not showing up during printing.

Changed in system-config-printer (Ubuntu):
importance: Undecided → Medium
Revision history for this message
oliverjames (richardremlap) wrote :

It would be excellent if someone could resolve this annoying bug.

Revision history for this message
Cameron Paine (cbp) wrote :

I have observed that the unresponsiveness of the printer notifier is related to the length of time a printer takes to consume the job data. I have 3 instances of xubuntu 14.04 (on physical machines) that send jobs to the same lpd print server. The laser printer attached to that server has a "deep sleep" mode. When asleep, it takes 60 seconds to "wake" and emit the first page. The notifier often hangs if the printer is asleep. At all other times pages are emitted within seconds and the notifier behaves as expected.

I have installed b3nmore's experimental scp-dbus-service.py (reply #28) on all 3 machines. Superficially it seems to have corrected the problem. I will report back when I've seen a lot more jobs pass through this printer.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Marking as fixed in Vivid and as present in Trusty, as the proposed fix is already included in (as part of the upstream code) in the system-config-printer version of Vivid.

Changed in system-config-printer (Ubuntu):
status: Confirmed → Fix Released
Changed in system-config-printer (Ubuntu Trusty):
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.