Canon IP4300 won't print

thom_raindog · 2011-03-29 14:10:38

Hello,

I have the printer mentioned above and though it did once, weeks ago, now it will not print anymore. I have changed every cartridge (since their lights were flashing) but that did nothing. The printer applet in KDE tells me the job is being processed (for near two hours now), same thing the cups webinterface says.

Where would I start looking to tackle this problem?

lagagnon · 2011-03-29 15:31:02

Start by checking out all the CUPS logs in /var/log/cups and post any error messages to this thread if you can't figure them out.

jwhendy · 2011-03-29 20:00:17

Similar thing happened to me. After a reinstall, and following the WIKI, my printer would not print. I solved this by using the gutenprint drivers instead of the Canon proprietary drivers.

I'd suggest using http://localhost:631 to delete the printer and reinstall per the wiki link posted above. See if that helps.

thom_raindog · 2011-03-30 19:56:23

Not sure what happens here. I deleted the printer, added it again (I had it as a Gutenprinter in the first place) and it shows the job that has been laying around canceled for the longest while now. The job actually got startet again automatically but was stuck and now that I cancelled it it reads (surprise) "cancelled" but won't get off the list.
And the printers little light is still slowly blinking as IF it were actually processing a job...

This is the error_log for tonights attempt. Can someone read some sense into that?

E [30/Mar/2011:21:12:59 +0200] Unable to open listen socket for address ::1:631 - Address family not supported by protocol.
E [30/Mar/2011:21:12:59 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
E [30/Mar/2011:21:13:02 +0200] Unable to open listen socket for address ::1:631 - Address family not supported by protocol.
E [30/Mar/2011:21:22:48 +0200] Returning HTTP Forbidden for CUPS-Delete-Printer (ipp://localhost/printers/Canon_iP4300) from localhost
E [30/Mar/2011:21:22:54 +0200] Returning HTTP Forbidden for CUPS-Delete-Printer (ipp://localhost/printers/Canon_iP4300) from localhost
E [30/Mar/2011:21:23:09 +0200] Returning HTTP Forbidden for CUPS-Delete-Printer (ipp://localhost/printers/Canon_iP4300) from localhost
E [30/Mar/2011:21:28:41 +0200] Unable to open listen socket for address ::1:631 - Address family not supported by protocol.
E [30/Mar/2011:21:28:41 +0200] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
E [30/Mar/2011:21:30:01 +0200] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost
E [30/Mar/2011:21:30:01 +0200] [CGI] CUPS-Get-Devices request failed with status 401: Forbidden
E [30/Mar/2011:21:37:46 +0200] [CGI] Unable to create avahi client: Resource temporarily unavailable
E [30/Mar/2011:21:37:46 +0200] [cups-deviced] PID 1962 (dnssd) stopped with status 1!
E [30/Mar/2011:21:49:42 +0200] [CGI] Unable to create avahi client: Resource temporarily unavailable
E [30/Mar/2011:21:49:42 +0200] [cups-deviced] PID 2074 (dnssd) stopped with status 1!
E [30/Mar/2011:21:50:36 +0200] Request from "localhost" using invalid Host: field "thom-desktop:631"
E [30/Mar/2011:21:50:36 +0200] Request from "localhost" using invalid Host: field "thom-desktop:631"
E [30/Mar/2011:21:50:36 +0200] Request from "localhost" using invalid Host: field "thom-desktop:631"
E [30/Mar/2011:21:50:37 +0200] Request from "localhost" using invalid Host: field "thom-desktop:631"

Any more ideas?

jwhendy · 2011-03-30 20:50:49

Hmmm -- it's almost like it doesn't like your hostname. Can you post /etc/hosts?

I've clicked on a link in CUPS webconfig to a printer and had it fail because it went to "bigBang:631/printername" instead of "localhost:631/printername". If I change it to the same URL but replace "bigBang" with "localhost" it goes fine. Those last lines, as well as the first, almost suggest some kind of hostname resolution error, and the ::1 mention suggests some kind of ipv6 issue? Not sure, though.

thom_raindog · 2011-04-02 06:06:35

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1               localhost.localdomain   localhost thom-desktop

# End of file

I can click on anything in the cups interface just fine, no problem there How would I tackle IPv6?

jwhendy · 2011-04-02 13:14:24

Interesting! I asked because of this line in your error post (first line):

E [30/Mar/2011:21:12:59 +0200] Unable to open listen socket for address ::1:631 - Address family not supported by protocol.

There's a few other mentions of that ::1:631, which is your local address in ipv6 notation. Perhaps it just can't connect properly and that's causing all your woes. My /etc/hosts looks like this:

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1    localhost.localdomain    localhost Macrophage
::1        localhost.localdomain    localhost Macrophage

The ::1 is the ipv6 equivalent of 127.0.0.1.

Perhaps you could try this?

$ ls /etc | grep pacnew

Unless you intentionally removed that line, the ::1 bit is part of the Arch default. I'm wondering if you have a file called /etc/hosts.pacnew, which is where pacman puts updated config files. It's quite important to sort through those and merge any needed changes into it. I didn't know about these files and booted up at one point and had some serious issues. I couldn't even login properly. I had to boot from the install disk, fiddle with all of those files to get them updated, and then reboot.

Or perhaps you already knew all of that and the no-ipv6 line is your doing? Figured more information is more helpful than not

thom_raindog · 2011-04-04 19:42:47

ipv6 was the key.. it prints again! Awesome and thank you! (And I really need to look through those new config files! *blush*)

jwhendy · 2011-04-04 21:19:05

@thom_raindog:

Sweet! No worries -- the configs caught me off guard as someone new to Arch as well. It was only as a result of a problem that I found out about them, as well Good luck. If it helps at all, my typical method is like so (probably grossly inefficient):

- open three terminals and full screen it (or tabs in a terminal)
- diff the old and new with:

diff --side-by-side /etc/config /etc/config.pacnew

- switch back and forth between the old and new either pasting in the old into the new or modifying the old to match the new
- keep diffing in the third terminal/tab until only what I know is unique to my system remains
- when all done, I either delete /etc/config or do 'mv /etc/config.pacnew /etc/config' depending on whether I added the old into the new or vice versa

Hope that helps. Maybe if someone reads this they can suggest a better way. This is only when something like /etc/groups comes along. For the mirrorlist, I just do 'mv /etc/pacman.d/mirrorlist.pacnew /etc/pacman.d/mirrorlist' and then uncomment my mirror of choice. It's not worth it for files in which very few differences exist. I only do work when I've put a lot of work into the config in the first place.

Arch Linux

#1 2011-03-29 14:10:38

Canon IP4300 won't print

#2 2011-03-29 15:31:02

Re: Canon IP4300 won't print

#3 2011-03-29 20:00:17

Re: Canon IP4300 won't print

#4 2011-03-30 19:56:23

Re: Canon IP4300 won't print

#5 2011-03-30 20:50:49

Re: Canon IP4300 won't print

#6 2011-04-02 06:06:35

Re: Canon IP4300 won't print

#7 2011-04-02 13:14:24

Re: Canon IP4300 won't print

#8 2011-04-04 19:42:47

Re: Canon IP4300 won't print

#9 2011-04-04 21:19:05

Re: Canon IP4300 won't print

Board footer