Bug 742026

Please run the printing troubleshooter.

https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter

Created attachment 525637 [details]
The trouble shooter hangs at this screenshot

This command from the https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter page no longer works on FC16:

$ su -c '/sbin/service cups restartlog'
Redirecting to /bin/systemctl  restartlog cups.service
Unknown operation restartlog

Once debugging is enabled for cups, then this error gets shown when I click 'Print Test Page':

There was an error during the CUPS operation: 'server-error-internal-error'. Attaching the error log.

Created attachment 525639 [details]
Error log after enabling cups debugging

Had to compress this, as it was too big otherwise

Thanks pointing me to the trouble shooter page.

Printer info from lpinfo:

Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = ipps
        class = network
        info = Internet Printing Protocol (ipps)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = beh
        class = network
        info = Backend Error Handler
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = serial:/dev/ttyS0?baud=115200
        class = serial
        info = Serial Port #1
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = https
        class = network
        info = Internet Printing Protocol (https)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = dnssd://HP%20LaserJet%20Professional%20M1212nf%20MFP._pdl-datastream._tcp.local/
        class = network
        info = HP LaserJet Professional M1212nf MFP
        make-and-model = Hewlett-Packard HP LaserJet Professional M1212nf MFP
        device-id = MFG:Hewlett-Packard;MDL:HP LaserJet Professional M1212nf MFP;FZY:0;
        location = 
Device: uri = dnssd://HP%20LaserJet%20Professional%20M1212nf%20MFP._printer._tcp.local/
        class = network
        info = HP LaserJet Professional M1212nf MFP
        make-and-model = Hewlett-Packard HP LaserJet Professional M1212nf MFP
        device-id = MFG:Hewlett-Packard;MDL:HP LaserJet Professional M1212nf MFP;FZY:0;
        location = 

PPD:

[stef@stef-desktop Desktop]$ grep '^*NickName:' /etc/cups/ppd/laserjet.ppd 
*NickName: "HP LaserJet Professional m1212nf MFP, hpcups 3.11.7, requires proprietary plugin"

Hmmm, that last one says "requires proprietary plugin". Is that really the case? And if so that message should be displayed in the printer state, rather than the current: "Idle - ready to print"

(In reply to comment #5)
> Hmmm, that last one says "requires proprietary plugin". Is that really the
> case? And if so that message should be displayed in the printer state, rather
> than the current: "Idle - ready to print"

Yes, that's most likely the reason.
Please install it with 'hp-plugin'.

from error_log:
STATE: +hplip.plugin-error

Thank you for pointing me in that direction. As you probably agree, we need to point the user in this direction rather than saying "Idle - ready to print". I've changed the bug description.

In other news:

[stef@stef-desktop tmp]$ wget http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.11.7-plugin.run
--2011-09-30 13:20:57--  http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.11.7-plugin.run
Resolving www.openprinting.org... 140.211.169.32
Connecting to www.openprinting.org|140.211.169.32|:80... connected.
HTTP request sent, awaiting response... 503 Service Temporarily Unavailable
2011-09-30 13:20:57 ERROR 503: Service Temporarily Unavailable.

I'll try to find that file elsewhere.

This bug report has so many bugs indicated...

So, let's try to enumerate them:

1. hpijs.drv doesn't contain a cupsIPPReason attribute to give descriptive text to the hplip.plugin-error state reason (hpcups.drv does)

2. gnome-settings-daemon doesn't display anything about the fact that the job stopped in any case, and ignores hplip.plugin-error

3. comment #4 indicates that something is busy-looping talking to cupsd, and won't take 401 for an answer (probably troubleshooter?)

4. troubleshooter not working right (comment #2)

5. Wiki page needs updating (comment #2)

Let's make this particular bug ID about the first one: hpijs.drv needs to describe a cupsIPPReason PPD attribute.  I'll file bugs for the next 3, and fix the wiki page.

Great. Let me know if more information or testing is needed.

BTW, just to confirm, after I managed to find that plugin file and installed it, the printer works.

Wait a minute... you're using the hpcups driver.  So actually problem 1 above is rubbish (hpijs doesn't use the hplip.plugin-error state reason at all).

So I'll change this bug ID to be about the second one, file bugs for the next 2, and fix the wiki page.

To summarise:

The part of gnome-settings-daemon that watches for CUPS events should:

* look for printer queues suddenly gaining unrecognised printer state reasons (e.g. hplip.plugin-error),
* look them up in the PPD using the cupsIPPReason attributes, and
* display a notification to the user about them.

Fix for this bug is available in gnome-settings-daemon-3.3.5 which is available in Fedora 17 (still under development). I'm closing this with resolution nextrelease.

Marek