[opensuse] cups printing pain on 10.3
After years of effortless printer setups on 10.1 and earlier, I've stumbled. The CUPS web-based admin works wonderfully, but when I try to print from any app, I seem to get stuck in a way I've never seen before. Google shows others appearently having similar issues, but no solutions could I find. Printer is a Brother HL-2060 When trying to print from vim, after a few seconds of 'sending to printer', the message changes to 'E365: Failed to print PostScript file'. Firefox just thinks there is a "Default/PostScript" printer, not finding the real one, and of course, laboriously prints nothing... OpenOffice seems similarly clueless about where to find the printer. Never had these problems in 10.1 or earlier, and I haven't any idea what to do about them. Trying to check the printer in kprinter: after un-confusing kprinter that the CUPS server is on localhost, and not the IP of the printer, kprinter does a perfectly good job of printing a test page. Some potentially useful information: $ lpr test_printer.txt lpr: Error - scheduler not responding! $ lpstat -p -d lpstat: server-error-operation-not-supported no system default destination lpoptions -p Brother_HL-2070N_series -l lpoptions: Unable to get PPD file for Brother_HL-2070N_series: client-error-not-found (the above is odd, considering both cups and kprinter can print a test page just fine...) $ cat /etc/printcap # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. Brother_HL-2070N_series_192.168.1.13|Brother HL-2070N series:rm=vlad.office:rp=Brother_HL-2070N_series_192.168.1.13: Brother_HL_2070N_series|Brother HL-2070N series:rm=vlad.office:rp=Brother_HL_2070N_series: $ rpm -qa | grep enscript enscript-1.6.4-83 $ rpm -qa | grep cups cups-libs-1.2.12-22 cups-backends-1.0-126 gnome-cups-manager-0.32cvs20060120-168 cups-1.2.12-22 cups-drivers-1.2.12-28 cups-autoconfig-0.1.0-27 cups-client-1.2.12-22 libgnomecups-0.2.2-123 libgnomecups-devel-0.2.2-123 cups-devel-1.2.12-22 gnome-cups-manager-devel-0.32cvs20060120-168 cupswrapperHL2070N-2.0.1-1 TIA Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael Fischer wrote:
After years of effortless printer setups on 10.1 and earlier, I've stumbled. The CUPS web-based admin works wonderfully, but when I try to print from any app, I seem to get stuck in a way I've never seen before. Google shows others appearently having similar issues, but no solutions could I find.
Printer is a Brother HL-2060
When trying to print from vim, after a few seconds of 'sending to printer', the message changes to 'E365: Failed to print PostScript file'.
Firefox just thinks there is a "Default/PostScript" printer, not finding the real one, and of course, laboriously prints nothing...
OpenOffice seems similarly clueless about where to find the printer.
Never had these problems in 10.1 or earlier, and I haven't any idea what to do about them.
Trying to check the printer in kprinter:
after un-confusing kprinter that the CUPS server is on localhost, and not the IP of the printer, kprinter does a perfectly good job of printing a test page.
Some potentially useful information:
$ lpr test_printer.txt lpr: Error - scheduler not responding!
$ lpstat -p -d lpstat: server-error-operation-not-supported no system default destination
lpoptions -p Brother_HL-2070N_series -l lpoptions: Unable to get PPD file for Brother_HL-2070N_series: client-error-not-found
(the above is odd, considering both cups and kprinter can print a test page just fine...)
$ cat /etc/printcap # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. Brother_HL-2070N_series_192.168.1.13|Brother HL-2070N series:rm=vlad.office:rp=Brother_HL-2070N_series_192.168.1.13: Brother_HL_2070N_series|Brother HL-2070N series:rm=vlad.office:rp=Brother_HL_2070N_series:
$ rpm -qa | grep enscript enscript-1.6.4-83
$ rpm -qa | grep cups cups-libs-1.2.12-22 cups-backends-1.0-126 gnome-cups-manager-0.32cvs20060120-168 cups-1.2.12-22 cups-drivers-1.2.12-28 cups-autoconfig-0.1.0-27 cups-client-1.2.12-22 libgnomecups-0.2.2-123 libgnomecups-devel-0.2.2-123 cups-devel-1.2.12-22 gnome-cups-manager-devel-0.32cvs20060120-168 cupswrapperHL2070N-2.0.1-1
TIA
Michael
Anything from the cups daemon in your system logs that may indicate what the problem is? I don't know what the issue is, but that may help. Also, you may want to check and see if there is a way to increase the verbosity of your cups log entries. I dunno, I'm not that savvy with cups. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-04-28 at 15:50 -0600, Jason Bailey, Sun Advocate Webmaster wrote:
Anything from the cups daemon in your system logs that may indicate what the problem is? I don't know what the issue is, but that may help. Also, you may want to check and see if there is a way to increase the verbosity of your cups log entries. I dunno, I'm not that savvy with cups.
That's easy: edit /etc/cups/cupsd.conf # # LogLevel: controls the number of messages logged to the ErrorLog # file and can be one of the following: # # debug2 Log everything. # debug Log almost everything. # info Log all requests and state changes. # warn Log errors and warnings. # error Log only errors. # none Log nothing. # LogLevel info #LogLevel debug2 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIFmKZtTMYHG2NR9URAgW2AJ9/+s/76XEVD0Im/rrxXu9EI3gsYgCeNiJB PolQCDVvO7MHI/F5J0+tDic= =ZXNj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Apr 28 17:44 Michael Fischer wrote (shortened):
$ lpr test_printer.txt lpr: Error - scheduler not responding!
Without a local running cupsd, nothing can work. I don't know why there is no local running cupsd. See http://en.opensuse.org/SDB:CUPS_in_a_Nutshell how to get debugging information: ---------------------------------------------------------------- If problems are encountered: 1. Set the "LogLevel debug" in /etc/cups/cupsd.conf. 2. Stop cupsd. 3. Move /var/log/cups/error_log* to another location (or delete it) in order to avoid having to search through gigantic log files. 4. Start cupsd. 5. Retry the action leading to the problem. 6. Now /var/log/cups/error_log* contains many messages that are useful for troubleshooting. ---------------------------------------------------------------- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Apr 29, Johannes Meixner wrote:
Hello,
On Apr 28 17:44 Michael Fischer wrote (shortened):
$ lpr test_printer.txt lpr: Error - scheduler not responding!
Without a local running cupsd, nothing can work. I don't know why there is no local running cupsd. See http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
Thanks to all who replied. The logging unfortunately didn't tell me anything... Eventually I tried the "Windows approach" and deleted the printer in Yast, and tried to set it up again as a TCP network printer (which didn't work originaly - for no reason I could understand at the time) but it worked fine on this occaision, and now all is working right.... go figure. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Apr 30, 2008 at 2:55 PM, Michael Fischer
On Tue, Apr 29, Johannes Meixner wrote:
Hello,
On Apr 28 17:44 Michael Fischer wrote (shortened):
$ lpr test_printer.txt lpr: Error - scheduler not responding!
Without a local running cupsd, nothing can work. I don't know why there is no local running cupsd. See http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
Thanks to all who replied.
The logging unfortunately didn't tell me anything...
Eventually I tried the "Windows approach" and deleted the printer in Yast, and tried to set it up again as a TCP network printer (which didn't work originaly - for no reason I could understand at the time) but it worked fine on this occaision, and now all is working right.... go figure.
Remember to assure that the printer always gets the same IP on power up, or you will have maddening reoccurrance of this head scratching incident. I usually do this by putting the printer's mac address in the dhcp server and reserving an IP that way rather than trying to hard code the IP into the printer's control panel. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Jason Bailey, Sun Advocate Webmaster -
Johannes Meixner -
John Andersen -
Michael Fischer