[opensuse] Cups compatibility
Hello List, having recently upgraded by 42.3 machine to Leap 15, I've noticed my cups client does not talk to the (ancient) server anymore. When I look at other machines, cups seems to have changed from 1.7.5 to 2.2.7, so maybe something changed so drastically that compatibility is impaired? My cups knowledge is sketchy, so I do not really know how to debug this problem. Any hints? For what it's worth, I see E [25/Jun/2018:14:23:45 +0200] cupsdReadClient: 20 IPP Read Error! in the server's error_log while the client reports lpr: bad request My /etc/cups/client.conf is unchanged from previous versions (i.e. it's still working for Leap 42.3 and earlier): ServerName our_cups_server.mpibpc.intern/version=1.1 Thanks, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann
Hi, Am 25.06.2018 um 14:42 schrieb Ansgar Esztermann-Kirchner:
Hello List,
having recently upgraded by 42.3 machine to Leap 15, I've noticed my cups client does not talk to the (ancient) server anymore.
1) have you taken a look inside the release notes of leap 15? === 2) then maybe (my ancient printers where from update opensuse 11.4 cups 1.4.6 to tumbleweed (one year in past, now it is 2.3b4) not working anymore. i have read: localhost:631/help/network.html and from this info, my string for the socket of my printers (not a real printerserver) has to include the cups version: socket://192.168.0.11:35/?version=1.1 before: socket://192.168.0.11:35 (/etc/cups/printers.conf) -> DeviceURI so maybe something similar for your problem. hope this helps. == 3) if not...if not try to google cups changelog simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Simon,
having recently upgraded by 42.3 machine to Leap 15, I've noticed my cups client does not talk to the (ancient) server anymore.
1) have you taken a look inside the release notes of leap 15?
Yes, I did. If there's anything there about cups, it has escaped me.
and from this info, my string for the socket of my printers (not a real printerserver) has to include the cups version:
socket://192.168.0.11:35/?version=1.1
Yep. I changed this about a year ago.
if not...if not try to google cups changelog
I looked through the changelog (in vain), but maybe the one pertinent line escaped me amongst the unrelated stuff. Thanks for your input, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann
Oh, by the way, i forgot to mention, somewhere between my updates the standard behavior of cups has also changed: from sending postscript to sending pdf i do not know if this will also affect you. for me it was somewhere made in background, my old ppd's (printers with did not accept pdf) where with some warnings accepted. (i do not remember exactly but i think i have also changed some lines) simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/25/2018 08:02 AM, Simon Becherer wrote:
somewhere between my updates the standard behavior of cups has also changed:
from sending postscript to sending pdf
If you set the printer to RAW in CUPs that should revert. Your printer driver is then responsible for sending postscript with the proper ppd etc. Conversion to pdf from postscipt, hpcl, epsom, etc is so well solved that if your printer can handle PDF directly it is by far the preferable way to go. Also if your cups client notices that some upstream cups server can accept PDF, that's the preferred route for it to take. The idea is to suppress redundant packaging and unpackaging at each CUPS server. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jun 25, 2018 at 05:02:32PM +0200, Simon Becherer wrote:
somewhere between my updates the standard behavior of cups has also changed:
from sending postscript to sending pdf i do not know if this will also affect you.
Oh, yes, I do remember (but cannot find anything in my logbook) discovering this change some time ago. However, things worked (again) afterwards, so there's something else. A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann
On 2018-06-25 09:02 AM, Simon Becherer wrote:
somewhere between my updates the standard behavior of cups has also changed:
from sending postscript to sending pdf Might this be the reason why the Brother driver for my DCP-7040 stopped working in Leap 15.0? It was working OK in 42.1. Now, CUPS says it has sent the data to the printer, but there is no response at the printer.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 26.06.2018 um 15:39 schrieb Darryl Gregorash:
On 2018-06-25 09:02 AM, Simon Becherer wrote:
somewhere between my updates the standard behavior of cups has also changed:
from sending postscript to sending pdf Might this be the reason why the Brother driver for my DCP-7040 stopped working in Leap 15.0? It was working OK in 42.1. Now, CUPS says it has sent the data to the printer, but there is no response at the printer.
socket://192.168.0.11:35/?version=1.1 if it is a old network printer its the (missing) version string who cause this problem. (i have had similar situation sending data, but nothing happends, but between other opensuse versions) if your printer did not understand pdf (because its old) check if there are new ppd out there for the pdf to ps problem. and/or, as explained from john andersen, try change the settings to send send raw data simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/06/18 10:13 AM, Simon Becherer wrote:
Am 26.06.2018 um 15:39 schrieb Darryl Gregorash:
On 2018-06-25 09:02 AM, Simon Becherer wrote:
somewhere between my updates the standard behavior of cups has also changed:
from sending postscript to sending pdf Might this be the reason why the Brother driver for my DCP-7040 stopped working in Leap 15.0? It was working OK in 42.1. Now, CUPS says it has sent the data to the printer, but there is no response at the printer.
socket://192.168.0.11:35/?version=1.1 if it is a old network printer its the (missing) version string who cause this problem. (i have had similar situation sending data, but nothing happends, but between other opensuse versions)
if your printer did not understand pdf (because its old) check if there are new ppd out there for the pdf to ps problem. and/or, as explained from john andersen, try change the settings to send send raw data
While that's reasonable in one sense, I'm not sure in the greater sense. I can see it making sense in the case of the (many) PDF documents I have, but they aren't the only thing I want to print. My printer groks postscript, heck I paid extra for that, always have since postscript was taken to be the UNIX/Linux 'standard' for printing. I can see PDF->PS in the case of documents that are native PDF, but not all. If I want to print email (which is plain text (or possibly HTML enhanced), a web page or many other things, then I don't want to go {text,html,ebook}->PDF->PS. Even if the process isn't lossy it seems wasteful. I realise that in some applications there is the 'print to file, then save as .PS' option, but why should I have to go though that manual procedure and then RAW print the resulting .PS file? Why can't I just send it through a {text,html,ebook}->PS and then straight to the RAW printer? Oh, wait, there are some nice pretty-printers for email as well; I recall some PS based one from the UNIX days ... I wonder what was used? Was it 'enscript'? Was there a macro package for that? I don't see it bundled now and googling, it seems that 'enscript' is a encryption program! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, mh, maybe i misunderstand you, but normally cups find out what is send to them, and will convert it automatically to ps, if your ppd file is correct and your /etc/cups/printers.conf also. i checked my ppd old and new, i have only changed a little to get rid of some warning messages. and, i changed ps version from 2 to 3 inside ppd (but one of my 2 printers is not able to understand 3) but with 3 this ps2 printer prints better (or at all, i do not remember) for sure, this printer is not able to understand 3, but maybe cups makes some other converts so that it worked fine. (to get these old machines printing has cost me several nights.... for the newer cups, before it was working out of the box) ========== here are some parats for one printer of my 2 printers.conf files, old, and new, (for a postscript only printer) as you can see, you must change some settings to get it to print with new cups versions. see especially the "Filter" and "DeviceURI" line. # Printer configuration file for CUPS v1.4.6 # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING <Printer qms_6100_oben> Info QMS magicolor 6100 MakeModel QMS magicolor 6100 DeviceURI socket://192.168.0.11:35 State Idle StateTime 1530034931 Type 8401100 Filter application/vnd.cups-raw 0 - Filter application/vnd.cups-command 0 commandtops Filter application/vnd.cups-postscript 0 - Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors none,\#00FFFF,#FF00FF,#FFFF00,#000000 Attribute marker-levels -1,-1,-1,-1,-1 Attribute marker-names ,,,, Attribute marker-types toner,toner,toner,toner,fuserOil Attribute marker-change-time 1530034931 </Printer> # Printer configuration file for CUPS v2.3b4 # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING <DefaultPrinter qms_6100_oben> PrinterId 4 UUID urn:uuid:88d769c9-d013-3c4f-7560-c690bd82a911 Info QMS magicolor 6110 MakeModel magicolor 6110 DeviceURI socket://192.168.0.11:35/?version=1.1 State Idle StateTime 1530007972 ConfigTime 1502986825 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors none,\#00FFFF,#FF00FF,#FFFF00,#000000 Attribute marker-levels -1,-1,-1,-1,-1 Attribute marker-names ,,,, Attribute marker-types toner,toner,toner,toner,fuser-oil Attribute marker-change-time 1530007972 </DefaultPrinter> hope this helps you. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/06/18 02:29 PM, Simon Becherer wrote:
Hi,
mh, maybe i misunderstand you, but normally cups find out what is send to them, and will convert it automatically to ps, if your ppd file is correct and your /etc/cups/printers.conf also.
Along the way I have general and specifics. As I understand it I can pretty-print to my postscript printer email messages using 'enscript' with the "language=mail" option under the "-E" option. Right now I have to save the message to a text file and run the command with -P brother_Postscript which is my raw interface. It seems clunky. As clunky as sending a PGP message the same way rather than using the Enigmail plugin. back in the UNIX SVR4 days the front-end filters were smart enough to recognise email and check user config and do the 'enscript' thing. So why isn't CUPS recognising what is being sent to it? Why can't I set up a 'enscript' filter if it sees email? Or, conversely, this isn't a CUPS problem but a problem that has to be solved for each and ever mail user interface individually. Which, as I implied, for an old UNIX hack, seems a bit ridiculous. maybe someone should reinvent the SVR4 print manager and replace CUPS. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-27 05:40, Anton Aylward wrote:
On 26/06/18 02:29 PM, Simon Becherer wrote:
Hi,
mh, maybe i misunderstand you, but normally cups find out what is send to them, and will convert it automatically to ps, if your ppd file is correct and your /etc/cups/printers.conf also.
Along the way I have general and specifics.
As I understand it I can pretty-print to my postscript printer email messages using 'enscript' with the "language=mail" option under the "-E" option.
Right now I have to save the message to a text file and run the command with -P brother_Postscript which is my raw interface.
It seems clunky. As clunky as sending a PGP message the same way rather than using the Enigmail plugin.
back in the UNIX SVR4 days the front-end filters were smart enough to recognise email and check user config and do the 'enscript' thing. So why isn't CUPS recognising what is being sent to it? Why can't I set up a 'enscript' filter if it sees email?
Or, conversely, this isn't a CUPS problem but a problem that has to be solved for each and ever mail user interface individually. Which, as I implied, for an old UNIX hack, seems a bit ridiculous. maybe someone should reinvent the SVR4 print manager and replace CUPS.
I can send basically any file to cups and it is printed. Cups applies the correct software tools to manage it. However, I may not like the result and may apply different filters manually. lpr file.txt lpr file.pdf lpr file.ps lpr file.jpg Ok, the later I have not tried in a long time. I'm trying just now. Yes, it worked. Now, what email file do you want me to try? I saved your email to file from Yhunderbird, then printed it: cer@Telcontar:~> file \[opensuse\]\ Cups\ compatibility.eml [opensuse] Cups compatibility.eml: SMTP mail, ASCII text, with CRLF line terminators cer@Telcontar:~> lpr \[opensuse\]\ Cups\ compatibility.eml cer@Telcontar:~> Worked fine, except that some lines are too long, and that it printed all the headers. It was handled as text. Cups works just fine. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 27/06/18 05:57 AM, Carlos E. R. wrote:
Now, what email file do you want me to try?
I saved your email to file from Yhunderbird, then printed it:
cer@Telcontar:~> file \[opensuse\]\ Cups\ compatibility.eml [opensuse] Cups compatibility.eml: SMTP mail, ASCII text, with CRLF line terminators cer@Telcontar:~> lpr \[opensuse\]\ Cups\ compatibility.eml cer@Telcontar:~>
Worked fine, except that some lines are too long, and that it printed all the headers. It was handled as text.
yes I've seen that in my own experimentation and its WRONG. If you print an email message from within thunderbird using the regular GUI print dialogue you don't get the SMTP format. As it stands the print system is NOT recognising this .eml file as other than text. Big deal. So much for recognition.. Now, offline to CUPS.. I saved you email as plain text, just the normal headers rather than the whole RAW message, the kind of thing you'd normally read in the GUI. I then pretty-printed that using 'enscript' as a filter enscript -G -Email -p Cups\ compatibility.ps Cups\ compatibility.txt In this case I used the "-p" option to save it to a file rather then the -P option to send it to the RAW postscript printer. Rather than throw a long PS file at you and the list, I'm going to send just to you the result of converting it to a much shorter PDF. ps2pdf Cups\ compatibility.ps Cups\ compatibility.pdf People can try this for themselves. Enscript can pretty-print a wide variety of languages, RTFM. In days of old, applications prompted for the kind of print command to use and you could do a lpr -o 'filter requirements...' or enscript .... -d RAW_spool there in the GUI prompt. We've taken horrific steps backwards in the name of user <strike>frailness</strike> friendliness as defined by Apple As I say, back in the SVR4 days the print system could be easily handle this kind of filer routing on demand. Now, as you've seen, CUPS just thinks its a text file. Using 'file' is OK, but if you don't pay attention to what the user wants then what's the point? This isn't artificial intelligence it's stupidity. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi anton, well, i remember 3 or so years in past, i changed somwehere in cups-files the pdf filter to another pdf filter. because i have had problems, my printer has cut off some end of the a4 site. do not ask me now, but because it was possible to do this (without compiling something) i think its possible to implement new filters and rules, but you have to ask somebody who know more about how to do.
if you don't pay attention to what the user wants then what's the point? This isn't artificial intelligence it's stupidity.
for this you need users who are willing to do such things, but most users today, and especially the very young, if you asked them about computers, they will tell you knowing everything, but are not able to put a boot cd correct inside a drive.... ;-))) simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-27 15:25, Anton Aylward wrote:
On 27/06/18 05:57 AM, Carlos E. R. wrote:
Now, what email file do you want me to try?
I saved your email to file from Yhunderbird, then printed it:
cer@Telcontar:~> file \[opensuse\]\ Cups\ compatibility.eml [opensuse] Cups compatibility.eml: SMTP mail, ASCII text, with CRLF line terminators cer@Telcontar:~> lpr \[opensuse\]\ Cups\ compatibility.eml cer@Telcontar:~>
Worked fine, except that some lines are too long, and that it printed all the headers. It was handled as text.
yes I've seen that in my own experimentation and its WRONG.
If you print an email message from within thunderbird using the regular GUI print dialogue you don't get the SMTP format.
As it stands the print system is NOT recognising this .eml file as other than text.
Why should it? EML is a thunderbird invention, Alpine doesn't do it. But I'm almost sure that you can add an automatic filter of your choice to cups. ... Yes, and it is documented: https://en.opensuse.org/SDB:Using_Your_Own_Filters_to_Print_with_CUPS -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
https://en.opensuse.org/SDB:Using_Your_Own_Filters_to_Print_with_CUPS
Oh, interessting site, stored if in future problems occur.... simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/06/18 11:41 AM, Carlos E. R. wrote:
Why should it? EML is a thunderbird invention, Alpine doesn't do it.
In which case the print dialogue of the mail user interface should offer a command that can act as the filter. If you install the 'xv' package, I have xv-3.10a-1280.3.1.x86_64 and therein the view any one of a number of file types such as xv /tmp/eml2.ps and then call up the 'print' option, you will see that it has the option to enter a print command. The default is simply 'lpr' q.v. your earlier email. But if I want I can enter a some complex filter such as the an enscript with a pile of options that send the result to the RAW spooler.
But I'm almost sure that you can add an automatic filter of your choice to cups.
Yes, that method of filtering relies on MIME and as far as MIME is concerned an email message is text. Well, yes it is text, but it is the SEMANTICS that makes it different. Yes, I noted 'cupsPreFilter' but there is still the MIME route to get there. <quote> cupsPreFilter *cupsPreFilter: "source/type cost program" This string keyword provides a pre-filter rule. The pre-filter program will be inserted in the conversion chain immediately before the filter that accepts the given MIME type. </quote> I've just pulled my old SVR4 manuals and looked at how it deal with different things like dot matrix printers, teletype printers, forms processing, , smart typewriters that used pin-wheels for different fonts and more. it was a lot more script-driven and admin friendly and made up out of the discrete components and data pathways, the old 'each thing goes one thing, and paid more attention to what was the command line option that this 'treat all text files as text file'. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2018-06-27 at 12:32 -0400, Anton Aylward wrote:
On 27/06/18 11:41 AM, Carlos E. R. wrote:
Why should it? EML is a thunderbird invention, Alpine doesn't do it.
In which case the print dialogue of the mail user interface should offer a command that can act as the filter.
Ah, no, we are printing from the command line letting cups do the detection automatically, and it does so for many formats. I simply chanced on one that is not included. See /usr/share/cups/mime/mime.types to find out the list. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlszv7UACgkQtTMYHG2NR9UiPwCggvAwIIBhniAwMby1JpsjdPIV J8oAoIrhfUoMv+nxc7pCuupTaCpAMzNt =A2iq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/06/18 12:47 PM, Carlos E. R. wrote:
On Wednesday, 2018-06-27 at 12:32 -0400, Anton Aylward wrote:
On 27/06/18 11:41 AM, Carlos E. R. wrote:
Why should it? EML is a thunderbird invention, Alpine doesn't do it.
In which case the print dialogue of the mail user interface should offer a command that can act as the filter.
Ah, no, we are printing from the command line letting cups do the detection automatically, and it does so for many formats. I simply chanced on one that is not included.
See /usr/share/cups/mime/mime.types to find out the list.
I have. So how would YOU define a text/email ?? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-27 20:34, Anton Aylward wrote:
On 27/06/18 12:47 PM, Carlos E. R. wrote:
On Wednesday, 2018-06-27 at 12:32 -0400, Anton Aylward wrote:
On 27/06/18 11:41 AM, Carlos E. R. wrote:
Why should it? EML is a thunderbird invention, Alpine doesn't do it.
In which case the print dialogue of the mail user interface should offer a command that can act as the filter.
Ah, no, we are printing from the command line letting cups do the detection automatically, and it does so for many formats. I simply chanced on one that is not included.
See /usr/share/cups/mime/mime.types to find out the list.
I have. So how would YOU define a
text/email
I don't know. I would have to study the documentation. Notice that there is no such thing either in "/usr/share/misc/magic". However, eml is detected thus:
cer@Telcontar:~> file \[opensuse\]\ Cups\ compatibility.eml [opensuse] Cups compatibility.eml: SMTP mail, ASCII text, with CRLF line terminators cer@Telcontar:~>
The definition is this (/usr/share/misc/magic): #------------------------------------------------------------------------------ # $File: mail.news,v 1.22 2013/01/04 14:22:07 christos Exp $ # mail.news: file(1) magic for mail and news # # Unfortunately, saved netnews also has From line added in some news software. #0 string From mail text 0 string/t Relay-Version: old news text !:mime message/rfc822 0 string/t #!\ rnews batched news text !:mime message/rfc822 0 string/t N#!\ rnews mailed, batched news text !:mime message/rfc822 0 string/t Forward\ to mail forwarding text !:mime message/rfc822 0 string/t Pipe\ to mail piping text !:mime message/rfc822 0 string/tc delivered-to: SMTP mail text !:mime message/rfc822 0 string/tc return-path: SMTP mail text !:mime message/rfc822 0 string/t Path: news text !:mime message/news 0 string/t Xref: news text !:mime message/news 0 string/t From: news or mail text !:mime message/rfc822 0 string/t Article saved news text !:mime message/news 0 string/t BABYL Emacs RMAIL text 0 string/t Received: RFC 822 mail text !:mime message/rfc822 0 string/t MIME-Version: MIME entity text #0 string/t Content- MIME entity text So maybe that is useful if you want to add eml pretty printing to cups. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Mon, Jun 25, 2018 at 02:42:16PM +0200, Ansgar Esztermann-Kirchner wrote:
Hello List,
having recently upgraded by 42.3 machine to Leap 15, I've noticed my cups client does not talk to the (ancient) server anymore.
BOO #1099167. Apparently, it's a known problem, fixed in 2.2.8, but that has other problems. A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann
participants (6)
-
Ansgar Esztermann-Kirchner -
Anton Aylward -
Carlos E. R. -
Darryl Gregorash -
John Andersen -
Simon Becherer