FS#37605 - [cups] Can't print to network printer

Attached to Project: Arch Linux
Opened by David Jones (ke7mbz) - Saturday, 02 November 2013, 15:59 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 25 November 2013, 21:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I can print to my printer when connected by USB, but not over the network.

I had this bug in Fedora as well, starting with cups 1.6.3. It was fixed in 1.6.4, but apparently the fix hasn't been pushed upstream. I reverted to 1.6.2 on my Arch machine, and it's working again. I tested cups 1.7, and the bug is still there.


Additional info:
cups 1.6.3 and above.
Splix driver for samsung scx-4623f attached to Fedora 19 server.

Seems to be the same as this Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1010580


Steps to reproduce:
Print test page or from any other application. The print job gets stuck in the queue.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 25 November 2013, 21:07 GMT
Reason for closing:  Fixed
Comment by Andreas Radke (AndyRTR) - Saturday, 02 November 2013, 17:50 GMT
Check, if adding that patch does fix it for you:

http://pkgs.fedoraproject.org/cgit/cups.git/tree/cups-final-content-type.patch?id=22be195ed425289a6846c5eccc1489bae881b484

I have a network laser printer that seems to work fine so far. I only had to remove/readd it once for 1.7.0 release when printing stopped working. But
maybe it comes back and I can confirm that revert to fix this issue. But this reverts an upstream change and should be better solved upsteam. Anything else can only be a temporary workaround.
Comment by David Jones (ke7mbz) - Saturday, 02 November 2013, 20:11 GMT
Readding didn't work. I even tried a reboot, since I've pulled in a lot of updates since the last one.

I applied the Fedora patch, and it's working now.

I've attached my PKGBUILD.
   PKGBUILD (8.2 KiB)
Comment by Andreas Radke (AndyRTR) - Monday, 04 November 2013, 15:35 GMT
I've applied this workaround for testing in 1.7.0-2.

But we should follow upstream changes if it gets fixed somewhere in a better way.
Comment by David Jones (ke7mbz) - Monday, 25 November 2013, 17:11 GMT
I just installed 1.7.0.2, and it works. Thanks.

Loading...