Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4275 - CUPS fails to print
Summary: CUPS fails to print
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: x86 Linux
: Highest critical (vote)
Assignee: Grant Goodyear (RETIRED)
URL: http://www.cups.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-28 02:19 UTC by Julien Ponge
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Ponge 2002-06-28 02:19:56 UTC
I have tried printing with CUPS. I never ran into problems with it and I had 
installed it many times with other distros. But with Gentoo it can't print. I 
have emerged cupsd and gimp-print-cups. My printer has an attached device in 
/dev/ and a CUPS driver (it's a HP printer so it is very known). The 
configuration steps did not cause a problem too. Here are 2 lines from the 
error log : 
I [21/Jun/2002:15:36:04 +0200] Job 5 queued on 'Printer' by 'root'. 
E [21/Jun/2002:15:36:04 +0200] Unable to convert file 0 to printable format 
for job 5! 
 
I guess there's something wrong with a missing filter or something.
Comment 1 Grant Goodyear (RETIRED) gentoo-dev 2002-06-28 15:49:29 UTC
Emerge the latest ghostscript.
Comment 2 Matteo Sasso 2002-06-30 05:58:09 UTC
I also experience this bug. I have ghostscript emerged. Logfile also reads: E [30/Jun/2002:12:12:51 +0200] print_job: resource name '/printers/lp' no good! E [30/Jun/2002:12:13:02 +0200] print_job: resource name '/printers/lp' no good!  I also tried remerging cups. 
Comment 3 Matteo Sasso 2002-06-30 06:01:32 UTC
Forgot to say: I used cups for some time and I have this problem since I upgraded to a newer version (can't remember which one). 
Comment 4 Matteo Sasso 2002-06-30 06:06:33 UTC
Ehm... forgot to restart cupsd... ^_^' Sorry. Please somebody close this bug.