Re: cups sucks!!! Epilogue
On 11/3/18 7:24 pm, Tim wrote: On Wed, 2018-03-07 at 08:00 +1100, Stephen Morris wrote: I have my home multifunction device connected to my router, so it is effectively a network device. I suppose should be really specific and say, is that an ethernet (or WiFi) connection between printer and router, or is the printer connected to a USB port on your router (which may entail fun and games as how the router presents a printer to the network). The device is a copier, scanner and printer in one device. It is an Epson Expression ET 3700 continuous flow ink device that is connected to the router via ethernet over a home plug device, the wifi interface on the device doesn't work properly. The wireless interface is 2.4 GHz, and with the device located where I had the predecessor canon device, the Epson device can't see the network, and if I move the device to next to the router it can see the network but continually rejects the connection password even though the password is correct. I need the Epson driver for Fedora and Ubuntu as cups has no support for my device whatsoever. Having installed the driver, with no printers defined at all in cups, if I go to Add Printers, cups sees two network definitions for my device, one using lpd and one using dnssd. lpd is the old pre-CUPS-era way of doing things, if I recall correctly. dnssd is one of those ZeroConf, Bonjour, Avahi protocols. One of those systems would have to be working properly for that to work as intended. Those two protocols are the two network definitions for the device that cups sees if the Epson supplied driver is installed, without the driver cups can't see the device at all. If I select the lpd definition, cups adds that printer once I select the driver, if I then go to Printers, with cups-browsed active a second definition has automagically appeared that is using ippd, which the definition says is driverless. I can't recall you saying what the printer actually is. You've said you've installed an Epson driver, perhaps it doesn't name itself in a unique manner? Perhaps it's not really a printing "driver", just making it appear to the system? If the printer directly accepts PostScript, PDF, or one of a few common languages, perhaps CUPS does the actual print driving. Without the driver, cups doesn't have a definition in its drivers list for this device, and neither does the Epson Escpr driver package in the repository that I don't have installed at the moment. The printer doesn't accept postscript or pdf or any other language that I know of, none of the inkjet printers I've had have had any documentation on exactly what the data output to the printer actually is. Having all 3 definitions in cups, all 3 output to the device. The driver that was in cups for the Canon MX926 device I had previously which I was using wirelessly, didn't have support for the 9600x4800 resolution the canon device had either, like the Epson driver it only had support for up to 600 dpi as well. None of these drivers impress me with their level of support for the printer. The printer is capable of printing at 4800x1200, but all of the drivers only offer a print resolution of "Standard" or "High". If I'm using Windows and doing a print from Photoshop Elements, Elements tells me the standard print resolution is 300 dpi and the high print resolution is 600 dpi, and selecting the different Epson paper types make no difference. A lot of printers are just 600 dpi printers, with software doing some pretending to make the printing look crisper. Selecting paper types may make no noticeable difference, it depends on what the printer does with the information, it could affect any of: Changing dithering patterns, slightly changing distance between the print head and the paper, changing drying times, which inks it uses, changing toner temperatures, simply selecting the right paper tray to print from or too (e.g. cardstock requiring a straight through path), offering/refusing double-sided printing, the range of print resolutions it offers. I distinctly hate having to deal with printers. Firstly you have to get it working, which can be a nightmare, even on their supported OSs. A year or two after getting one you may find it impossible to get ink or toner, or it's become ridiculously expensive. Or they only supplied a badly working driver for an old OS that can't be used on a newer one. If I select the "high" resolution which Photoshop Elements says is 600 dpi, the output on Matt Photo Paper is vastly different to the output on the Premium Glossy Photo Paper, the Glossy Photo Paper output is significantly better even though the printer is not actually a photo printer. Switching between the different quality papers makes a difference to the quality of the output but not the resoluton. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to
Re: cups sucks!!! Epilogue
On Wed, 2018-03-07 at 08:00 +1100, Stephen Morris wrote: > I have my home multifunction device connected to my router, so it is > effectively a network device. I suppose should be really specific and say, is that an ethernet (or WiFi) connection between printer and router, or is the printer connected to a USB port on your router (which may entail fun and games as how the router presents a printer to the network). > I need the Epson driver for Fedora and Ubuntu as cups has no support > for my device whatsoever. Having installed the driver, with no > printers defined at all in cups, if I go to Add Printers, cups sees > two network definitions for my device, one using lpd and one using > dnssd. lpd is the old pre-CUPS-era way of doing things, if I recall correctly. dnssd is one of those ZeroConf, Bonjour, Avahi protocols. One of those systems would have to be working properly for that to work as intended. > If I select the lpd definition, cups adds that printer once I select > the driver, if I then go to Printers, with cups-browsed active a > second definition has automagically appeared that is using ippd, > which the definition says is driverless. I can't recall you saying what the printer actually is. You've said you've installed an Epson driver, perhaps it doesn't name itself in a unique manner? Perhaps it's not really a printing "driver", just making it appear to the system? If the printer directly accepts PostScript, PDF, or one of a few common languages, perhaps CUPS does the actual print driving. > None of these drivers impress me with their level of support for the > printer. The printer is capable of printing at 4800x1200, but all of > the drivers only offer a print resolution of "Standard" or "High". If > I'm using Windows and doing a print from Photoshop Elements, Elements > tells me the standard print resolution is 300 dpi and the high print > resolution is 600 dpi, and selecting the different Epson paper types > make no difference. A lot of printers are just 600 dpi printers, with software doing some pretending to make the printing look crisper. Selecting paper types may make no noticeable difference, it depends on what the printer does with the information, it could affect any of: Changing dithering patterns, slightly changing distance between the print head and the paper, changing drying times, which inks it uses, changing toner temperatures, simply selecting the right paper tray to print from or too (e.g. cardstock requiring a straight through path), offering/refusing double-sided printing, the range of print resolutions it offers. I distinctly hate having to deal with printers. Firstly you have to get it working, which can be a nightmare, even on their supported OSs. A year or two after getting one you may find it impossible to get ink or toner, or it's become ridiculously expensive. Or they only supplied a badly working driver for an old OS that can't be used on a newer one. -- [tim@localhost ~] -rsvp Linux 4.13.16-100.fc25.x86_64 #1 SMP Mon Nov 27 19:52:46 UTC 2017 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
On 6/3/18 11:24 am, Tim wrote: On Tue, 2018-03-06 at 07:44 +1100, Stephen Morris wrote: Have you considered implementing the other Microsoft way, which I'm not sure how to do as I'm not a network technician but which a number of organizations tend to do, and that is when the client does a network browse for network printers, selects the printer that they want to use, the server downloads and installs the driver on the client machine? Admittedly, this still requires the client to prepare the data for printing, but at least the server or the printer itself handles the queuing of print jobs. Still a damn awful way to do things. It gets even hairier if all your client computers are different OSs. Microsoft, and even MacOS are still crap at handling printers. Just the other week, I turned on the printer, and the OS insisted on installing drivers for the printer. Despite the fact that drivers were already installed, and fully operational. Even with a stand-alone networked printer, I still set it up to be accessible through the LAN server. That way any Linux box can print easily through it without the shenanigans of specially setting up that printer on each and every PC. I don't know at what stage the original poster discovered CUPs being a backwards designed schmozzle, but I'm sure it was working the old and good way on my latest Fedora 26 installation. I can't check now, the motherboard went kablooey, last week. And I'm back on an old Fedora 25 installation on my ancient laptop. Not to mention that my LAN file & printer server is completely ancient, and still on Fedora Core 4. I have my home multifunction device connected to my router, so it is effectively a network device. For obvious reasons if I go to add printers in cups, it can't see the printer unless it is turned on. I use the printer on my machine from Windows 10, Fedora and Ubuntu and from Windows 10 on my wife's computer, so I have installed the Epson drivers on all 4 operating systems. I need the Epson driver for Fedora and Ubuntu as cups has no support for my device whatsoever. Having installed the driver, with no printers defined at all in cups, if I go to Add Printers, cups sees two network definitions for my device, one using lpd and one using dnssd. If I select the lpd definition, cups adds that printer once I select the driver, if I then go to Printers, with cups-browsed active a second definition has automagically appeared that is using ippd, which the definition says is driverless. None of these drivers impress me with their level of support for the printer. The printer is capable of printing at 4800x1200, but all of the drivers only offer a print resolution of "Standard" or "High". If I'm using Windows and doing a print from Photoshop Elements, Elements tells me the standard print resolution is 300 dpi and the high print resolution is 600 dpi, and selecting the different Epson paper types make no difference. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
On Tue, 2018-03-06 at 07:44 +1100, Stephen Morris wrote: > Have you considered implementing the other Microsoft way, which I'm > not sure how to do as I'm not a network technician but which a number > of organizations tend to do, and that is when the client does a > network browse for network printers, selects the printer that they > want to use, the server downloads and installs the driver on the > client machine? > Admittedly, this still requires the client to prepare the data for > printing, but at least the server or the printer itself handles the > queuing of print jobs. Still a damn awful way to do things. It gets even hairier if all your client computers are different OSs. Microsoft, and even MacOS are still crap at handling printers. Just the other week, I turned on the printer, and the OS insisted on installing drivers for the printer. Despite the fact that drivers were already installed, and fully operational. Even with a stand-alone networked printer, I still set it up to be accessible through the LAN server. That way any Linux box can print easily through it without the shenanigans of specially setting up that printer on each and every PC. I don't know at what stage the original poster discovered CUPs being a backwards designed schmozzle, but I'm sure it was working the old and good way on my latest Fedora 26 installation. I can't check now, the motherboard went kablooey, last week. And I'm back on an old Fedora 25 installation on my ancient laptop. Not to mention that my LAN file & printer server is completely ancient, and still on Fedora Core 4. -- [tim@localhost ~] -rsvp Linux 4.13.16-100.fc25.x86_64 #1 SMP Mon Nov 27 19:52:46 UTC 2017 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
On 6/3/18 5:24 am, David A. De Graaf wrote: On 03/03/18 20:20, Stephen Morris wrote: On 3/3/18 9:01 am, David A. De Graaf wrote: The cups system in Fedora 27 has taken a giant step backward from prior versions in that browsing no longer works automatically. In F26, if the cups-browsed service was enabled and started, all the printers on the LAN would be discovered and be available for use - automatically. Hi David, I'm a little confused by what you mean here. In all versions of cups, including F27, when you add a printer to cups, if the network printer is turned on cups can automatically find it if it has support for the printer, then when that printer is selected and the driver selected, the printer is added to the printer list. The term "network printer" has (at least) two meanings. For you, I suspect, it means a printer that is directly accessible on the LAN with its own IP. It has enough internal memory to store some arbitrary number of jobs enqueued to be printed when the printer manages to get to them. Every computer on the LAN can send jobs directly to the printer with the expectation that interfering traffic will somehow be resolved. In addition each computer must be trained to know the idiosyncrasies of that computer in the form of a "driver" designed specifically for that printer. Jobs must be prepared at the sending computer to be agreeable to that specific printer's needs. This is the Microsoft way. For me, a UNIX traditionalist, a "network printer" is available to any computer on the LAN, but ONLY through the intervention of the server that controls it. This includes printers that are, in fact, wired to the server via USB, etc., as well as those with direct (but secret) IP access. The server, usually with tons of memory to spare, can easily accept jobs simultaneously from many senders and queue them. It also can analyze the file content sent, and filter it appropriately. Only the server computer needs to know the details of how to actually prepare the job for successful printing; the clients simply send print jobs to the server and let it figure out the details. This is the *NIX way. It is the second configuration that is getting short shrift in the latest cups development. It seems perfectly obvious that when a server "advertises" a printer's services, that each and every client should see that service queue automatically. That's the very essence of the job that cups-browsed is created to do. And it is what the newest version fails utterly to do, unless the config file is edited as I described. The F26 version worked perfectly, exactly as I expected, so it is possible. One of my two printers is a bit rare and exotic. It is a Brother HL-L8250CDN color laser printer, and is totally unknown to Fedora (and to Windows). Fortunately, Brother has prepared installable .rpm files with the necessary drivers that I have downloaded and installed on the server computer. They work perfectly. But, considering all that trouble, why in the name of God, would I want to repeat that effort for each and every client computer that might want to use that printer? That's just insane. But that's the Microsoft way. Have you considered implementing the other Microsoft way, which I'm not sure how to do as I'm not a network technician but which a number of organizations tend to do, and that is when the client does a network browse for network printers, selects the printer that they want to use, the server downloads and installs the driver on the client machine? Admittedly, this still requires the client to prepare the data for printing, but at least the server or the printer itself handles the queuing of print jobs. regards, Steve If cups-browsed is active then another entry is automatically added. In my case, with the Epson printer (Expression ET 3700) I have cups finds two entries provided from having installed the Epson supplied driver (cups doesn't have native support), one using lpd and the other using dnssd. The entry that gets auto added if cups-browsed is active uses ipps and is specified as driverless, hence when selecting paper types it doesn't know anything about Epson specific paper. regards, Steve In F27 this no longer works. But there is a workaround. I must now edit /etc/cups/cups-browsed.conf on each and every client machine to add these lines: BrowsePoll datium BrowsePoll datair LocalQueueNamingRemoteCUPS RemoteName where datium and datair are _my_ servers with connected printers. Note that Fully Qualified Names, such as datium.datix.lan, are NOT acceptable. With only two physical printers and a handful of client machines on my LAN, this is marginally tolerable; with a much larger LAN, it isn't. I've complained in https://bugzilla.redhat.com/show_bug.cgi?id=1518415 and in https://bugzilla.redhat.com/show_bug.cgi?id=1525937. Apparently the "upstream" developers have
Re: cups sucks!!! Epilogue
On 03/03/18 20:20, Stephen Morris wrote: On 3/3/18 9:01 am, David A. De Graaf wrote: The cups system in Fedora 27 has taken a giant step backward from prior versions in that browsing no longer works automatically. In F26, if the cups-browsed service was enabled and started, all the printers on the LAN would be discovered and be available for use - automatically. Hi David, I'm a little confused by what you mean here. In all versions of cups, including F27, when you add a printer to cups, if the network printer is turned on cups can automatically find it if it has support for the printer, then when that printer is selected and the driver selected, the printer is added to the printer list. The term "network printer" has (at least) two meanings. For you, I suspect, it means a printer that is directly accessible on the LAN with its own IP. It has enough internal memory to store some arbitrary number of jobs enqueued to be printed when the printer manages to get to them. Every computer on the LAN can send jobs directly to the printer with the expectation that interfering traffic will somehow be resolved. In addition each computer must be trained to know the idiosyncrasies of that computer in the form of a "driver" designed specifically for that printer. Jobs must be prepared at the sending computer to be agreeable to that specific printer's needs. This is the Microsoft way. For me, a UNIX traditionalist, a "network printer" is available to any computer on the LAN, but ONLY through the intervention of the server that controls it. This includes printers that are, in fact, wired to the server via USB, etc., as well as those with direct (but secret) IP access. The server, usually with tons of memory to spare, can easily accept jobs simultaneously from many senders and queue them. It also can analyze the file content sent, and filter it appropriately. Only the server computer needs to know the details of how to actually prepare the job for successful printing; the clients simply send print jobs to the server and let it figure out the details. This is the *NIX way. It is the second configuration that is getting short shrift in the latest cups development. It seems perfectly obvious that when a server "advertises" a printer's services, that each and every client should see that service queue automatically. That's the very essence of the job that cups-browsed is created to do. And it is what the newest version fails utterly to do, unless the config file is edited as I described. The F26 version worked perfectly, exactly as I expected, so it is possible. One of my two printers is a bit rare and exotic. It is a Brother HL-L8250CDN color laser printer, and is totally unknown to Fedora (and to Windows). Fortunately, Brother has prepared installable .rpm files with the necessary drivers that I have downloaded and installed on the server computer. They work perfectly. But, considering all that trouble, why in the name of God, would I want to repeat that effort for each and every client computer that might want to use that printer? That's just insane. But that's the Microsoft way. If cups-browsed is active then another entry is automatically added. In my case, with the Epson printer (Expression ET 3700) I have cups finds two entries provided from having installed the Epson supplied driver (cups doesn't have native support), one using lpd and the other using dnssd. The entry that gets auto added if cups-browsed is active uses ipps and is specified as driverless, hence when selecting paper types it doesn't know anything about Epson specific paper. regards, Steve In F27 this no longer works. But there is a workaround. I must now edit /etc/cups/cups-browsed.conf on each and every client machine to add these lines: BrowsePoll datium BrowsePoll datair LocalQueueNamingRemoteCUPS RemoteName where datium and datair are _my_ servers with connected printers. Note that Fully Qualified Names, such as datium.datix.lan, are NOT acceptable. With only two physical printers and a handful of client machines on my LAN, this is marginally tolerable; with a much larger LAN, it isn't. I've complained in https://bugzilla.redhat.com/show_bug.cgi?id=1518415 and in https://bugzilla.redhat.com/show_bug.cgi?id=1525937. Apparently the "upstream" developers have a much different view than me of why Linux printing has traditionally been so successful and reliable and are hell-bent on "fixing" it. -- David A. De GraafDATIX, Inc.Hendersonville, NC d...@datix.us www.datix.us ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
On 3/3/18 9:01 am, David A. De Graaf wrote: On 02/27/18 17:04, François Patte wrote: Le 25/02/2018 à 19:42, François Patte a écrit : Bonjour. I try to configure a printer on my local network but all attemps fail. I have a printer attached to one computer on an usb port and I want to use it with other computers on my local network. I opened firefox on one computer and miracle: the printer attached to the other computer is discovered and cups admin interface asks me if I want to add this printer. Nice: the job is easy!! *But* this does not work at all!! Sending a test page returns that the printer is not responding. I tried to cofigure the printer using the "Add printer" way and chose ipp. According to the given syntax, I wrote: ipp://name-of-server/ipp but this does not work: sending a test page returns that the printer is misconfigured or no longer exists... I replaced the name of the server by its IP address... same result. I tried: ipp://name-of-server:631/printers/name-of-printer-on-server. It does not work, the message is now: Filter failed. What fiter? I don't know as cups logs no longer exist since systemd... Does somebody know a solution? After googleling a lot I could solve my problem but in a very strange way! First I found some people talking about the impossibility to use the same driver on the server (the computer to which the printer is plugged) and the other computers on the LAN, them claimed that the driver to use on the clients must be the "raw" driver. So I tried to modify the configuration on a client, changing the driver to raw, but cups refuses at the end to modify the config and I had to delete the printer on the client and to re-add the printer from scratch using the raw driver and cups accepted this way of doing. But printing a test page failed. "Filter failed" was the error! journalctl gives useless information, just a joke (maybe): " Job stopped due to filter errors; please consult the error_log file for details." There is no more error_log file At last I tried to use the "automatic way": ask cups to find the printers on the LAN and add the computer. Using this way, I chose the raw driver (cups accepted this) but the configuration failed one more time: "the printer is misconfigured or no longer exists". So, I asked to modify this configuration, replacing the dnssd address by an ipp one and I did not change the driver in this modification and, this time, cups accepted the modification and at last the printer worked! cups really sucks! The cups system in Fedora 27 has taken a giant step backward from prior versions in that browsing no longer works automatically. In F26, if the cups-browsed service was enabled and started, all the printers on the LAN would be discovered and be available for use - automatically. Hi David, I'm a little confused by what you mean here. In all versions of cups, including F27, when you add a printer to cups, if the network printer is turned on cups can automatically find it if it has support for the printer, then when that printer is selected and the driver selected, the printer is added to the printer list. If cups-browsed is active then another entry is automatically added. In my case, with the Epson printer (Expression ET 3700) I have cups finds two entries provided from having installed the Epson supplied driver (cups doesn't have native support), one using lpd and the other using dnssd. The entry that gets auto added if cups-browsed is active uses ipps and is specified as driverless, hence when selecting paper types it doesn't know anything about Epson specific paper. regards, Steve In F27 this no longer works. But there is a workaround. I must now edit /etc/cups/cups-browsed.conf on each and every client machine to add these lines: BrowsePoll datium BrowsePoll datair LocalQueueNamingRemoteCUPS RemoteName where datium and datair are _my_ servers with connected printers. Note that Fully Qualified Names, such as datium.datix.lan, are NOT acceptable. With only two physical printers and a handful of client machines on my LAN, this is marginally tolerable; with a much larger LAN, it isn't. I've complained in https://bugzilla.redhat.com/show_bug.cgi?id=1518415 and in https://bugzilla.redhat.com/show_bug.cgi?id=1525937. Apparently the "upstream" developers have a much different view than me of why Linux printing has traditionally been so successful and reliable and are hell-bent on "fixing" it. -- David A. De GraafDATIX, Inc.Hendersonville, NC d...@datix.us www.datix.us ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
On 02/27/18 17:04, François Patte wrote: Le 25/02/2018 à 19:42, François Patte a écrit : Bonjour. I try to configure a printer on my local network but all attemps fail. I have a printer attached to one computer on an usb port and I want to use it with other computers on my local network. I opened firefox on one computer and miracle: the printer attached to the other computer is discovered and cups admin interface asks me if I want to add this printer. Nice: the job is easy!! *But* this does not work at all!! Sending a test page returns that the printer is not responding. I tried to cofigure the printer using the "Add printer" way and chose ipp. According to the given syntax, I wrote: ipp://name-of-server/ipp but this does not work: sending a test page returns that the printer is misconfigured or no longer exists... I replaced the name of the server by its IP address... same result. I tried: ipp://name-of-server:631/printers/name-of-printer-on-server. It does not work, the message is now: Filter failed. What fiter? I don't know as cups logs no longer exist since systemd... Does somebody know a solution? After googleling a lot I could solve my problem but in a very strange way! First I found some people talking about the impossibility to use the same driver on the server (the computer to which the printer is plugged) and the other computers on the LAN, them claimed that the driver to use on the clients must be the "raw" driver. So I tried to modify the configuration on a client, changing the driver to raw, but cups refuses at the end to modify the config and I had to delete the printer on the client and to re-add the printer from scratch using the raw driver and cups accepted this way of doing. But printing a test page failed. "Filter failed" was the error! journalctl gives useless information, just a joke (maybe): " Job stopped due to filter errors; please consult the error_log file for details." There is no more error_log file At last I tried to use the "automatic way": ask cups to find the printers on the LAN and add the computer. Using this way, I chose the raw driver (cups accepted this) but the configuration failed one more time: "the printer is misconfigured or no longer exists". So, I asked to modify this configuration, replacing the dnssd address by an ipp one and I did not change the driver in this modification and, this time, cups accepted the modification and at last the printer worked! cups really sucks! The cups system in Fedora 27 has taken a giant step backward from prior versions in that browsing no longer works automatically. In F26, if the cups-browsed service was enabled and started, all the printers on the LAN would be discovered and be available for use - automatically. In F27 this no longer works. But there is a workaround. I must now edit /etc/cups/cups-browsed.conf on each and every client machine to add these lines: BrowsePoll datium BrowsePoll datair LocalQueueNamingRemoteCUPS RemoteName where datium and datair are _my_ servers with connected printers. Note that Fully Qualified Names, such as datium.datix.lan, are NOT acceptable. With only two physical printers and a handful of client machines on my LAN, this is marginally tolerable; with a much larger LAN, it isn't. I've complained in https://bugzilla.redhat.com/show_bug.cgi?id=1518415 and in https://bugzilla.redhat.com/show_bug.cgi?id=1525937. Apparently the "upstream" developers have a much different view than me of why Linux printing has traditionally been so successful and reliable and are hell-bent on "fixing" it. -- David A. De GraafDATIX, Inc.Hendersonville, NC d...@datix.us www.datix.us ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: cups sucks!!! Epilogue
Le 25/02/2018 à 19:42, François Patte a écrit : > Bonjour. > > I try to configure a printer on my local network but all attemps fail. > > I have a printer attached to one computer on an usb port and I want to > use it with other computers on my local network. > > I opened firefox on one computer and miracle: the printer attached to > the other computer is discovered and cups admin interface asks me if I > want to add this printer. Nice: the job is easy!! *But* this does not > work at all!! > > Sending a test page returns that the printer is not responding. > > I tried to cofigure the printer using the "Add printer" way and chose > ipp. According to the given syntax, I wrote: ipp://name-of-server/ipp > but this does not work: sending a test page returns that the printer is > misconfigured or no longer exists... > > I replaced the name of the server by its IP address... same result. > > I tried: ipp://name-of-server:631/printers/name-of-printer-on-server. It > does not work, the message is now: Filter failed. > > What fiter? I don't know as cups logs no longer exist since systemd... > > Does somebody know a solution? After googleling a lot I could solve my problem but in a very strange way! First I found some people talking about the impossibility to use the same driver on the server (the computer to which the printer is plugged) and the other computers on the LAN, them claimed that the driver to use on the clients must be the "raw" driver. So I tried to modify the configuration on a client, changing the driver to raw, but cups refuses at the end to modify the config and I had to delete the printer on the client and to re-add the printer from scratch using the raw driver and cups accepted this way of doing. But printing a test page failed. "Filter failed" was the error! journalctl gives useless information, just a joke (maybe): " Job stopped due to filter errors; please consult the error_log file for details." There is no more error_log file At last I tried to use the "automatic way": ask cups to find the printers on the LAN and add the computer. Using this way, I chose the raw driver (cups accepted this) but the configuration failed one more time: "the printer is misconfigured or no longer exists". So, I asked to modify this configuration, replacing the dnssd address by an ipp one and I did not change the driver in this modification and, this time, cups accepted the modification and at last the printer worked! cups really sucks! -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
