The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is giving me trouble: if I send it a print job, the panel light goes on and says OK, and the green printer horseshoe light come on but the printer doesn't print. lpstat shows the file has been sent: HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021 03:17:28 PM EDT How do I trouble shoot this and fix it, please? --doug
On Sunday, March 28, 2021 2:23:01 PM CDT Doug McGarrett wrote:
The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is giving me trouble: if I send it a print job, the panel light goes on and says OK, and the green printer horseshoe light come on but the printer doesn't print. lpstat shows the file has been sent:
HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021 03:17:28 PM EDT
How do I trouble shoot this and fix it, please? --doug
Doug, You sure have a lot of trouble with printers! Are you connecting to this printer via USB or network? If it's via network maybe the printer got a different IP address - Hint - set a static IP address for the printer. Or the firewall is blocking communication. So, how are are connecting to this printer? Mark
On 3/28/21 6:07 PM, Mark Petersen wrote:
On Sunday, March 28, 2021 2:23:01 PM CDT Doug McGarrett wrote:
The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is giving me trouble: if I send it a print job, the panel light goes on and says OK, and the green printer horseshoe light come on but the printer doesn't print. lpstat shows the file has been sent:
HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021 03:17:28 PM EDT
How do I trouble shoot this and fix it, please? --doug Doug,
You sure have a lot of trouble with printers!
Are you connecting to this printer via USB or network? If it's via network maybe the printer got a different IP address - Hint - set a static IP address for the printer. Or the firewall is blocking communication.
So, how are are connecting to this printer?
Mark It's on the LAN. I just pinged its static IP and it came back OK. Zero packet loss. Yes, I sure have trouble with printers. The Epson keeps telling me the paper is the wrong size, but it is the right size in OpenSUSE. And the right size in Mint, on another computer, which also has no trouble with the HP. Dunno? --doug
On Sunday, March 28, 2021 5:57:32 PM CDT Doug McGarrett wrote:
On 3/28/21 6:07 PM, Mark Petersen wrote:
On Sunday, March 28, 2021 2:23:01 PM CDT Doug McGarrett wrote:
The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is giving me trouble: if I send it a print job, the panel light goes on and says OK, and the green printer horseshoe light come on but the printer doesn't print. lpstat shows the file has been sent:
HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021 03:17:28 PM EDT
How do I trouble shoot this and fix it, please? --doug
Doug,
You sure have a lot of trouble with printers!
Are you connecting to this printer via USB or network? If it's via network maybe the printer got a different IP address - Hint - set a static IP address for the printer. Or the firewall is blocking communication.
So, how are are connecting to this printer?
Mark
Doug, There is no need to send a reply email to me, just send it to the list.
It's on the LAN.
You say you connecting to it on the LAN. Are you connected via ethernet or wireless?
I just pinged its static IP and it came back OK. Zero packet loss.
Ping generally uses port 80/443, so yes you can reach the printer. But printing via network doesn't use port 80/443. If you open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer. What does it say for Connection: ?? - I have 2 HP LaserJet Pro 400-M401dn's at work that work without issue daily for more than 2 years. These printers are very close to your M201dw. Here is what it says for connection with the printer in my office. Connection: hp:/net/HP_LaserJet_400_M401dn?lp=172.20.10.32 What does yours say? Mark
Yes, I sure have trouble with printers. The Epson keeps telling me the paper is the wrong size, but it is the right size in OpenSUSE. And the right size in Mint, on another computer, which also has no trouble with the HP. Dunno? --doug
On 29/03/2021 06.29, Andrei Borzenkov wrote:
On 29.03.2021 04:34, Mark Petersen wrote:
Ping generally uses port 80/443,
ping does not use any port at all. There is no notion of ports in ICMP.
Right :-) But you can tell some ping programs to use udp/tcp and adjust the port. nping --tcp -p 443 hostname -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/29/21 6:44 AM, Carlos E. R. wrote:
On 29/03/2021 06.29, Andrei Borzenkov wrote:
On 29.03.2021 04:34, Mark Petersen wrote:
Ping generally uses port 80/443,
ping does not use any port at all. There is no notion of ports in ICMP.
Right :-)
But you can tell some ping programs to use udp/tcp and adjust the port.
nping --tcp -p 443 hostname
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux. --doug
On Mon, 2021-03-29 at 17:59 -0400, Doug McGarrett wrote:
On 3/29/21 6:44 AM, Carlos E. R. wrote:
On 29/03/2021 06.29, Andrei Borzenkov wrote:
On 29.03.2021 04:34, Mark Petersen wrote:
Ping generally uses port 80/443,
ping does not use any port at all. There is no notion of ports in ICMP.
Right :-)
But you can tell some ping programs to use udp/tcp and adjust the port.
nping --tcp -p 443 hostname
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux. --doug
Pretty difficult to help you when you won't answer simple questions. I'm/We are not mind readers. Wireless connection or ethernet cable at the PC with openSUSE that won't print? Wireless connection or ethernet cable at the M201dw printer? What does the CUPS webpage say about the connection to the M201dw printer? I'm asking these questions to see if you have a network issue or a printer driver problem. Mark
On 3/29/21 9:31 PM, Mark Peteren wrote:
On Mon, 2021-03-29 at 17:59 -0400, Doug McGarrett wrote:
On 3/29/21 6:44 AM, Carlos E. R. wrote:
On 29/03/2021 06.29, Andrei Borzenkov wrote:
On 29.03.2021 04:34, Mark Petersen wrote:
Ping generally uses port 80/443,
ping does not use any port at all. There is no notion of ports in ICMP. Right :-)
But you can tell some ping programs to use udp/tcp and adjust the port.
nping --tcp -p 443 hostname
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux. --doug
Pretty difficult to help you when you won't answer simple questions. I'm/We are not mind readers.
Wireless connection or ethernet cable at the PC with openSUSE that Wired ethernet cable connection from computer to ASUS router or Netgear switch (don't know which without tracing cables) All connections here are hard wired. won't print?
Wireless connection or ethernet cable at the M201dw printer?08 Wired ethernet cable connections from router or switch to printers
What does the CUPS webpage say about the connection to the M201dw printer? Which CUPS heading should I look on to answer this question?
I'm asking these questions to see if you have a network issue or a printer driver problem. The printer worked for a while, then it stopped working. It still works fine from the Mint computer, which is connected thru the router /switch the same way. The Epson also works fine from the Mint computer, without complaining about the page size.
FYI: both printers have fixed IP addresses. LaserJet is 192.168.1.29; Epson is 192.168.1.26. Mark Thank you for your interest. What should I do now? --doug
On 30/03/2021 04.12, Doug McGarrett wrote:
On 3/29/21 9:31 PM, Mark Peteren wrote:
On Mon, 2021-03-29 at 17:59 -0400, Doug McGarrett wrote:
What does the CUPS webpage say about the connection to the M201dw printer? Which CUPS heading should I look on to answer this question?
He told you that in an email the other day: <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/message/ZVIVVYFLKGO27KRKJTCON45CWCWEY74Z/> -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux.
Well, the routine is the same as always: start with the logs. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux.
Well, the routine is the same as always: start with the logs. What log should I look for? --doug
On Mon, 2021-03-29 at 22:14 -0400, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux.
Well, the routine is the same as always: start with the logs.
What log should I look for? --doug
.
This is out of the box - maybe worth checking: If the printers are wired over Ethernet, is their WiFi connectivity disabled. If not, they could be getting DHCP IP address over WiFi possibly confusing things. Example openSuSE sends packets over to the static IP, the printer responds over DHCP. The Firewall in openSuSE would most likely filter that based on state. Not sure about Mint, but Ubuntu (base for Mint) does not use firewall by default so this kind of situation could work enough. Just a thought. It is easier to disable/check printer WiFi using their displays than going through long checklist here. HTH, Tomas
On 3/30/21 12:57 AM, TomasK wrote:
On Mon, 2021-03-29 at 22:14 -0400, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux. /snio/ This is out of the box - maybe worth checking:
If the printers are wired over Ethernet, is their WiFi connectivity disabled. If not, they could be getting DHCP IP address over WiFi possibly confusing things. Example openSuSE sends packets over to the static IP, the printer responds over DHCP. The Firewall in openSuSE would most likely filter that based on state. Not sure about Mint, but Ubuntu (base for Mint) does not use firewall by default so this kind of situation could work enough.
Just a thought. It is easier to disable/check printer WiFi using their displays than going through long checklist here.
HTH, Tomas Interesting idea. I'll check it tomorrow--getting late here. Wifi does not work well here anyway--there's some kind of interference from something nearby.--doug
On Monday, March 29, 2021 11:48:48 PM CDT Doug McGarrett wrote:
On 3/30/21 12:57 AM, TomasK wrote:
On Mon, 2021-03-29 at 22:14 -0400, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux.
/snio/
This is out of the box - maybe worth checking:
If the printers are wired over Ethernet, is their WiFi connectivity disabled. If not, they could be getting DHCP IP address over WiFi possibly confusing things. Example openSuSE sends packets over to the static IP, the printer responds over DHCP. The Firewall in openSuSE would most likely filter that based on state. Not sure about Mint, but Ubuntu (base for Mint) does not use firewall by default so this kind of situation could work enough.
Just a thought. It is easier to disable/check printer WiFi using their displays than going through long checklist here.
HTH, Tomas
Interesting idea. I'll check it tomorrow--getting late here. Wifi does not work well here anyway--there's some kind of interference from something nearby.--doug
Doug, Yes, follow Tomas' advice and disable the WiFi on the printer. You say these printers have a static IP address, how are you setting these addresses? On the printer itself or in your DHCP server? - If you are setting these static IP addresses on the printers, are they outside of the DHCP server's scope? You don't want 2 devices on the network with the same address. Open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer. What does it say for Connection: Mark
On 3/30/21 9:12 AM, Mark Petersen wrote:
On Monday, March 29, 2021 11:48:48 PM CDT Doug McGarrett wrote:
On 3/30/21 12:57 AM, TomasK wrote:
On Mon, 2021-03-29 at 22:14 -0400, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux. /snio/ This is out of the box - maybe worth checking:
If the printers are wired over Ethernet, is their WiFi connectivity disabled. If not, they could be getting DHCP IP address over WiFi possibly confusing things. Example openSuSE sends packets over to the static IP, the printer responds over DHCP. The Firewall in openSuSE would most likely filter that based on state. Not sure about Mint, but Ubuntu (base for Mint) does not use firewall by default so this kind of situation could work enough.
Just a thought. It is easier to disable/check printer WiFi using their displays than going through long checklist here.
HTH, Tomas
Interesting idea. I'll check it tomorrow--getting late here. Wifi does not work well here anyway--there's some kind of interference from something nearby.--doug Doug,
Yes, follow Tomas' advice and disable the WiFi on the printer.
You say these printers have a static IP address, how are you setting these addresses? On the printer itself or in your DHCP server? - If you are setting these static IP addresses on the printers, are they outside of the DHCP server's scope? You don't want 2 devices on the network with the same address.
Open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer.
What does it say for Connection:
Mark I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it. doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug
On Tuesday, March 30, 2021 6:27:50 PM CDT Doug McGarrett wrote:
On 3/30/21 9:12 AM, Mark Petersen wrote:
On Monday, March 29, 2021 11:48:48 PM CDT Doug McGarrett wrote:
On 3/30/21 12:57 AM, TomasK wrote:
On Mon, 2021-03-29 at 22:14 -0400, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote: > I think this is getting off the problem--obviously the computer > sees > the printer-- it turns on the "in-use" light and the little green > hosrseshoe indicator, it just doesn't actually print anything. I > would think it was a printer problem, but it prints perfectly > from a > laptop running Mint Linux.
/snio/
This is out of the box - maybe worth checking:
If the printers are wired over Ethernet, is their WiFi connectivity disabled. If not, they could be getting DHCP IP address over WiFi possibly confusing things. Example openSuSE sends packets over to the static IP, the printer responds over DHCP. The Firewall in openSuSE would most likely filter that based on state. Not sure about Mint, but Ubuntu (base for Mint) does not use firewall by default so this kind of situation could work enough.
Just a thought. It is easier to disable/check printer WiFi using their displays than going through long checklist here.
HTH, Tomas
Interesting idea. I'll check it tomorrow--getting late here. Wifi does not work well here anyway--there's some kind of interference from something nearby.--doug
Doug,
Yes, follow Tomas' advice and disable the WiFi on the printer.
You say these printers have a static IP address, how are you setting these addresses? On the printer itself or in your DHCP server? - If you are setting these static IP addresses on the printers, are they outside of the DHCP server's scope? You don't want 2 devices on the network with the same address.
Open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer.
What does it say for Connection:
Mark
I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug
Haste makes waste ;-) As Carlos said the printer was just stopped. Well, now that you deleted it; Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps. Mark
On 3/30/21 9:07 PM, Mark Petersen wrote: / long snip/
Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark Mark, everything works like you said, up until you left me! I'm on the "Setup Device" page. Filled in Printer name —HP_LaserJet_Pro_M201dw— and description, which may be wrong: "HP LaserJet". (I tried leaving this out, but got complaint--now put it in and still get complaint.) Location: RPNY (for Rocky Point, New York) and the PPD file was filled in for me: /usr/share/cups/model/manufacturer-PPDs/hplip-hpps/hp-laserjet_pro_m201_m202-ps.ppd.gz Checked Send page to printer. Checked Add printer. Then got:
Complaint: Launched hp-setup. You must finish hp-setup before you can proceed with the printer configuration. Now what? Thanx for the assistance! --doug
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool. --dg
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
It looks to me like HPLIP is only for directly connected printers, not for printers on a LAN. That's what YaST seems to be telling me. --doug
On Wed, 2021-03-31 at 18:51 -0400, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug
Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
It looks to me like HPLIP is only for directly connected printers, not for printers on a LAN. That's what YaST seems to be telling me. --doug
This is long thread .... I kind of feel enough pain to speak up ... HPLIP may not work for everyone - it certainly does not detect my HP LaserJet printers running leap 15.1. Even manual HPLIP discovery with given IP did not work either. HPLIP setup worked in 15.0 and before. I am not special config type of guy on desktop - mostly default install + KDE. I tried pretty hard to use HPLIP in the past. When desperate for ideas - I started Ubuntu guest in KVM on a host and it auto-detected detected the printers just fine - so, probably no firewall or network issues. Here is what I have done to print from leap 15.1: yast2 printer: Print via Network: Connection Wizard: Access Network Printer or Printserver box via: TCP/Port (AppSocket/JetDirect) IP Address: 192.168.1.26 (filled from nmap above) TCP Port: 9100 Test Connection: Answered OK OK In Printer Setup: Search for: hp I selected closest lower ...ppd.gz Default Paper Size: Letter OK Print Test Page: OK Then .... selected the printer in Printer configurations --> Edit --> All Options for Current Driver --> Duplex: DuplexNoThumble ....... Hope that helps if HPLIP does not work as intended. Tomas
On 01/04/2021 00.51, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
It looks to me like HPLIP is only for directly connected printers, not for printers on a LAN. That's what YaST seems to be telling me.
Not correct. Just install hplip from inside yast. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/31/21 6:51 PM, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
It looks to me like HPLIP is only for directly connected printers, not for printers on a LAN. That's what YaST seems to be telling me. --doug
Wrong. In the Device menu, Setup Device. It will offer you ethernet, usb, or wireless. --dg
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip I did this. It didn't say connection. I sent an answer to this somewhere on the list. Anyway, I decided to reinstall the printer. But I can't. YaST can't find it. I've tried every combination I could find, but the printer just can't be found by YaST.
nmap can find it.
doug@linux1:~> su - Password: linux1:~ # nmap -sP 192.168.1.* Starting Nmap 7.80 ( https://nmap.org ) at 2021-03-30 19:15 EDT Nmap scan report for router.asus.com (192.168.1.1) Host is up (0.00038s latency). MAC Address: 30:5A:3A:A0:55:30 (Asustek Computer) Nmap scan report for dell3 (192.168.1.10) Host is up (0.00070s latency). MAC Address: 00:26:B9:CC:F5:0D (Dell) Nmap scan report for 192.168.1.26 Host is up (0.00038s latency). MAC Address: A4:EE:57:73:CB:85 (Seiko Epson) Nmap scan report for 192.168.1.29 <<<<< Host is up (0.00036s latency). <<<<< MAC Address: D0:BF:9C:34:CF:8A (Hewlett Packard) <<<<< Nmap scan report for 192.168.1.48 Host is up (0.00033s latency). MAC Address: 50:E5:49:B3:A2:51 (Giga-byte Technology) Nmap scan report for linux1 (192.168.1.200) Host is up. Nmap done: 256 IP addresses (6 hosts up) scanned in 1.81 seconds
It still prints from the Mint laptop, and not via rf; via lan cable network. I'm at the end of my rope; I've spent hours on this now and I'm not getting anywhere at all, just going backwards. --doug Haste makes waste ;-) As Carlos said the printer was just stopped.
Well, now that you deleted it;
Yast > Printer > Add > Run hp-setup > Networking/Ethernet/Wireless network > Show Advanced Options > tick the Manual Discover box > Enter 192.168.1.29 in the IP Address or network name > Next > Make sure the HP M201dw is selected then click Next ...... I'm not at work so I don't remember the rest of the steps.
Mark
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
OK, I installed HPLIP. Ran hp-toolbox. Got all the way thru it, for a change, and it seemed to be happy. Sent a small test file from Kate to the printer. The PRINT light on the printer lit up. Then nothing. No paper feed, no print. This is where I came in. It still prints perfectly from the Mint computer.
On 3/31/21 7:48 PM, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
snip
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
OK, I installed HPLIP. Ran hp-toolbox. Got all the way thru it, for a change, and it seemed to be happy. Sent a small test file from Kate to the printer. The PRINT light on the printer lit up. Then nothing. No paper feed, no print. This is where I came in. It still prints perfectly from the Mint computer.
Went thru the list of stuff in the hplip help page and tried the print test page option. IT WORKED. So I have to think the problem is within the computer somehow. The printer did print what it was told to as to a test page, it just won't print what the computer (presumably) tells it print. There is a long list of commands on the help page, but I don't see anything that leaps out at me and says HERE is the problem! The computer still prints to the Epson OK, except with the wrong page size, still. Makes the Epson hang on detection of size. --doug
On 01/04/2021 01.48, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
OK, I installed HPLIP. Ran hp-toolbox. Got all the way thru it, for a change, and it seemed to be happy. Sent a small test file from Kate to the printer. The PRINT light on the printer lit up. Then nothing. No paper feed, no print. This is where I came in. It still prints perfectly from the Mint computer.
Then, again, do look it in the logs, which they are, as always, under /var/log/cups/* -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/31/21 9:12 PM, Carlos E. R. wrote:
On 01/04/2021 01.48, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
Or - for the umpteenth time - install HPLIP. Use it to find the printer and install it. HPLIP takes care of the CUPS and YaST interaction - in fact, in the YaST Printer installation, there is a check-box to call HPLIP rather than leaving it to YaST. While you are there, take a look under the 5 tabs. You will see a wealth of data there about managing your driver and various printer logs, both of which AFAIK are not found in any other tool.
--dg
OK, I installed HPLIP. Ran hp-toolbox. Got all the way thru it, for a change, and it seemed to be happy. Sent a small test file from Kate to the printer. The PRINT light on the printer lit up. Then nothing. No paper feed, no print. This is where I came in. It still prints perfectly from the Mint computer.
Then, again, do look it in the logs, which they are, as always, under /var/log/cups/*
Here's the bottom of the long log file: localhost - - [31/Mar/2021:19:27:47 -0400] "POST / HTTP/1.1" 200 3822061 CUPS-Get-PPDs - localhost - - [31/Mar/2021:19:30:55 -0400] "POST / HTTP/1.1" 200 3822061 CUPS-Get-PPDs - localhost - - [31/Mar/2021:19:31:48 -0400] "POST /admin/ HTTP/1.1" 401 12513 CUPS-Add-Modify-Printer successful-ok localhost - root [31/Mar/2021:19:32:13 -0400] "POST /admin/ HTTP/1.1" 200 12513 CUPS-Add-Modify-Printer successful-ok localhost - - [31/Mar/2021:19:33:31 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 332 Create-Job successful-ok localhost - - [31/Mar/2021:19:33:31 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 9603 Send-Document successful-ok localhost - - [31/Mar/2021:19:53:36 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 366 Create-Job successful-ok localhost - - [31/Mar/2021:19:53:36 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 1700 Send-Document successful-ok localhost - - [31/Mar/2021:19:55:52 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 344 Create-Job successful-ok localhost - - [31/Mar/2021:19:55:52 -0400] "POST /printers/HP_LaserJet_Pro_M201dw HTTP/1.1" 200 423163 Send-Document successful-ok localhost - - [31/Mar/2021:20:01:11 -0400] "POST / HTTP/1.1" 200 183 Renew-Subscription successful-ok doug@linux1:/var/log/cups> But no print came out of the machine. --doug
On 01/04/2021 02.27, Doug McGarrett wrote:
On 3/31/21 9:12 PM, Carlos E. R. wrote:
On 01/04/2021 01.48, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
...
Then, again, do look it in the logs, which they are, as always, under /var/log/cups/*
Here's the bottom of the long log file: localhost - - [31/Mar/2021:19:27:47 -0400] "POST / HTTP/1.1" 200 3822061 CUPS-Get-PPDs -
That's access_log. What about error_log?
But no print came out of the machine.
Of course not. You have to study the log to find out the problem. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/31/21 9:34 PM, Carlos E.R. wrote:
On 01/04/2021 02.27, Doug McGarrett wrote:
On 3/31/21 9:12 PM, Carlos E. R. wrote:
On 01/04/2021 01.48, Doug McGarrett wrote:
On 3/31/21 6:38 PM, DennisG wrote:
On 3/30/21 9:07 PM, Mark Petersen wrote:
...
Then, again, do look it in the logs, which they are, as always, under /var/log/cups/*
Here's the bottom of the long log file: localhost - - [31/Mar/2021:19:27:47 -0400] "POST / HTTP/1.1" 200 3822061 CUPS-Get-PPDs -
That's access_log. What about error_log? Here's the last few lines of the error log:
D [31/Mar/2021:19:53:44 -0400] [Job 370] Running command line for pstops: pstops 370 doug \'Die berühmten 3 \' 1 \'finishings=3 job-uuid=urn:uuid:418ad095-d784-3eab-65a7-f410769af154 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1617234816 time-at-processing=1617234816 document-name-supplied=Die\\ berühmten\\ 3\\ \' D [31/Mar/2021:19:53:44 -0400] [Job 370] Using image rendering resolution 600 dpi D [31/Mar/2021:19:53:44 -0400] [Job 370] Set job-printer-state-message to "Grayscale/monochrome printing requested for this job but Poppler is not able to convert to grayscale/monochrome PostScript.", current level=WARN D [31/Mar/2021:19:53:44 -0400] [Job 370] Set job-printer-state-message to "Use \"pdftops-renderer\" option (see README file) to use Ghostscript or MuPDF for the PDF -> PostScript conversion.", current level=WARN D [31/Mar/2021:19:53:44 -0400] [Job 370] Running command line for pdftops: pdftops -level2 -origpagesizes -nocenter -r 600 /var/spool/cups/tmp/016aa606e719e - D [31/Mar/2021:19:53:44 -0400] [Job 370] Started filter pdftops (PID 5805) D [31/Mar/2021:19:53:44 -0400] [Job 370] Started filter pstops (PID 5806) D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1! D [31/Mar/2021:19:53:44 -0400] [Job 370] HP PS filter ENDS D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5802 (/usr/lib/cups/filter/pdftops) stopped with status 1. D [31/Mar/2021:19:53:44 -0400] [Job 370] Hint: Try setting the LogLevel to "debug" to find out more. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5803 (/usr/lib/cups/filter/hpps) exited with no errors. D [31/Mar/2021:19:53:44 -0400] [Job 370] ready to print D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5804 (/usr/lib/cups/backend/hp) exited with no errors. D [31/Mar/2021:19:53:44 -0400] [Job 370] End of messages D [31/Mar/2021:19:53:44 -0400] [Job 370] printer-state=3(idle) D [31/Mar/2021:19:53:44 -0400] [Job 370] printer-state-message="ready to print" D [31/Mar/2021:19:53:44 -0400] [Job 370] printer-state-reasons=none
But no print came out of the machine.
Of course not. You have to study the log to find out the problem.
I don't know where I would set the "LogLevel" and I probably would not understand the answer! --doug
Sending the log files to the list would make this much shorter and save you a lot of time. Am 01.04.21 um 04:49 schrieb Doug McGarrett:
D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1!
this is your (ore one of your problems) "the print file is empty" -> you send data to the printer, BUT the data file is empty. check where you lost the libpoppler.so.106 file install it. (open yast, search for poppler and maybe force installation of the already installed package, first check if the file is somewhere inside) - sorry i do not know the commandline rpm or zypper command for this - simoN -- www.becherer.de
On 01/04/2021 07.58, Simon Becherer wrote:
Sending the log files to the list would make this much shorter and save you a lot of time.
Absolutely. Instead of going in a wild chase reinstalling things that doesn't solve anything, wastes time and causes distress, the log tells precisely what is wrong.
Am 01.04.21 um 04:49 schrieb Doug McGarrett:
D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1!
this is your (ore one of your problems)
"the print file is empty" -> you send data to the printer, BUT the data file is empty.
check where you lost the libpoppler.so.106 file install it. (open yast, search for poppler and maybe force installation of the already installed package, first check if the file is somewhere inside) - sorry i do not know the commandline rpm or zypper command for this -
No, that is not that easy, they can only tell that information if the package is already installed. Unfortunate. BUT, we can look it up for him in our systems. first, "locate libpoppler.so", which on leap says /usr/lib64/libpoppler.so.89 and other hits. Then the command rpm -qf /usr/lib64/libpoppler.so.89 tells the rpm: cer@Telcontar:~> wrpm /usr/lib64/libpoppler.so.89 libpoppler89-0.79.0-lp152.2.3.1.x86_64 cer@Telcontar:~> So in this case you can search in yast for "libpoppler" and it will find it. So will zypper. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~> linux1:~ # zypper install libpoppler.so.89 Loading repository data... Reading installed packages... 'libpoppler.so.89' not found in package names. Trying capabilities. No provider of 'libpoppler.so.89' found. Resolving package dependencies... Nothing to do. Found this for OS Leap, but did not download it as yet: 1. openSUSE Leap 15.3 <https://opensuse.pkgs.org/> 2. openSUSE Oss x86_64 <https://opensuse.pkgs.org/15.3/opensuse-oss-x86_64/> 3. libpoppler89-0.79.0-1.89.x86_64.rpm libpoppler89-0.79.0-1.89.x86_64.rpm ------------------------------------------------------------------------ Description *libpoppler89 - PDF Rendering Library* Property Value Operating system *Linux* Distribution openSUSE Leap 15.3 <https://opensuse.pkgs.org/> Repository openSUSE Oss x86_64 <https://opensuse.pkgs.org/15.3/opensuse-oss-x86_64/> Official Package filename libpoppler89-0.79.0-1.89.x86_64.rpm Package name libpoppler89 Package version 0.79.0
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command. Sigh... Man... just do "zypper install libpoppler" just that. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do. --doug
On 01/04/2021 19.40, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
Sorry, it is: zypper install libpoppler108 You would have seen it if you used the search function in YaST as I told you earlier. or "zypper search libpoppler" -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 2:54 PM, Carlos E. R. wrote:
On 01/04/2021 19.40, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
Sorry, it is:
zypper install libpoppler108
You would have seen it if you used the search function in YaST as I told you earlier.
or "zypper search libpoppler" Searched zypper:
linux1:/home/doug # zypper search libpoppler Loading repository data... Reading installed packages... S | Name | Summary | Type ---+------------------------+---------------------------------------------------------+-------- i+ | libpoppler-cpp0 | C++ API of the Poppler PDF rendering library | package | libpoppler-cpp0-32bit | C++ API of the Poppler PDF rendering library | package | libpoppler-devel | Development files for the Poppler PDF rendering library | package | libpoppler-glib-devel | Development files for the Poppler Glib wrapper library | package i+ | libpoppler-glib8 | Glib wrapper for the poppler PDF rendering library | package | libpoppler-glib8-32bit | Glib wrapper for the poppler PDF rendering library | package i+ | libpoppler-qt5-1 | Qt5 wrapper for the Poppler PDF rendering library | package | libpoppler-qt5-1-32bit | Qt5 wrapper for the Poppler PDF rendering library | package | libpoppler-qt5-devel | Development files for the Poppler Qt5 wrapper library | package i | libpoppler107 | PDF Rendering Library | package | libpoppler108 | PDF Rendering Library | package | libpoppler108-32bit | PDF Rendering Library | package linux1:/home/doug # zypper install libpoppler108 Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: libpoppler108 1 new package to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 3.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libpoppler108-21.03.0-1.1.x86_64 (1/1), 1.2 MiB ( 3.6 MiB unpacked) Retrieving: libpoppler108-21.03.0-1.1.x86_64.rpm .............................[done (1.2 KiB/s)] Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done] Still doesn't print. --doug
On 4/1/21 2:54 PM, Carlos E. R. wrote:
On 01/04/2021 19.40, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
Sorry, it is:
zypper install libpoppler108
You would have seen it if you used the search function in YaST as I told you earlier. The following NEW package is going to be installed: libpoppler108
1 new package to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 3.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libpoppler108-21.03.0-1.1.x86_64 (1/1), 1.2 MiB ( 3.6 MiB unpacked) Retrieving: libpoppler108-21.03.0-1.1.x86_64.rpm .............................[done (1.2 KiB/s)]
Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done]
or "zypper search libpoppler"
The following NEW package is going to be installed: libpoppler108 1 new package to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 3.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libpoppler108-21.03.0-1.1.x86_64 (1/1), 1.2 MiB ( 3.6 MiB unpacked) Retrieving: libpoppler108-21.03.0-1.1.x86_64.rpm .............................[done (1.2 KiB/s)] Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done] Still doesn't print. --doug
On 01/04/2021 21.45, Doug McGarrett wrote:
On 4/1/21 2:54 PM, Carlos E. R. wrote:
On 01/04/2021 19.40, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
Sorry, it is:
zypper install libpoppler108
...
Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done]
Still doesn't print.
Why didn't you paste already what is on the log after that trial? What are you waiting for? You always have to look in the logs when there is a problem in Linux. That's the procedure. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 3:45 PM, Doug McGarrett wrote:
On 4/1/21 2:54 PM, Carlos E. R. wrote:
On 01/04/2021 19.40, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
Sorry, it is:
zypper install libpoppler108
You would have seen it if you used the search function in YaST as I told you earlier. The following NEW package is going to be installed: libpoppler108
1 new package to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 3.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libpoppler108-21.03.0-1.1.x86_64 (1/1), 1.2 MiB ( 3.6 MiB unpacked) Retrieving: libpoppler108-21.03.0-1.1.x86_64.rpm .............................[done (1.2 KiB/s)]
Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done]
or "zypper search libpoppler"
The following NEW package is going to be installed: libpoppler108
1 new package to install. Overall download size: 1.2 MiB. Already cached: 0 B. After the operation, additional 3.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package libpoppler108-21.03.0-1.1.x86_64 (1/1), 1.2 MiB ( 3.6 MiB unpacked) Retrieving: libpoppler108-21.03.0-1.1.x86_64.rpm .............................[done (1.2 KiB/s)]
Checking for file conflicts: .............................................................[done] (1/1) Installing: libpoppler108-21.03.0-1.1.x86_64 .......................................[done]
Still doesn't print. --doug
Does the HPLIP demo page work? Check the logs again. HPLIP/Actions/CUPS/View Printer and Device Information/Status History, or the Status tab. If your printer has an EWS (Embedded Web Server), open it in a browser (ip address of printer). Depending on model, there may be an Event Log. You should definitely familiarize yourself with the EWS, if you have it. --dg
On 4/1/21 1:40 PM, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
--doug
libpoppler108 is the current TW version: https://software.opensuse.org/package/libpoppler108
On 02/04/2021 00.06, DennisG wrote:
On 4/1/21 1:40 PM, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
libpoppler108 is the current TW version:
Unfortunately, libpoppler doesn't follow the name-version.minor.release naming convention. Instead apparently it uses nameversion-minor.release, which made the command to fail. And probably some dependency is broken, because it should have been installed automatically before that, not requiring a manual installation. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 7:34 PM, Carlos E. R. wrote:
On 02/04/2021 00.06, DennisG wrote:
On 4/1/21 1:40 PM, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote:
rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
libpoppler108 is the current TW version:
Unfortunately, libpoppler doesn't follow the name-version.minor.release naming convention. Instead apparently it uses nameversion-minor.release, which made the command to fail.
And probably some dependency is broken, because it should have been installed automatically before that, not requiring a manual installation. Went to the 'net and reinstalled the file via their automatic install function. Still doesn't print.
logfile (portion) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pdftops (PID 23229) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pstops (PID 23230) D [01/Apr/2021:18:51:36 -0400] [Job 373] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23229 (pdftops) stopped with status 127! D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -connecting-to-device D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -media-empty-error,media-jam-error,hplip.plugin-error,cover-open-error,toner-empty-error,other D [01/Apr/2021:18:51:36 -0400] [Job 373] The print file is empty. D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23230 (pstops) stopped with status 1! D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23226 (/usr/lib/cups/filter/pdftops) stopped with status 1. D [01/Apr/2021:18:51:36 -0400] [Job 373] Hint: Try setting the LogLevel to "debug" to find out more. *see below* D [01/Apr/2021:18:51:36 -0400] [Job 373] HP PS filter ENDS D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23227 (/usr/lib/cups/filter/hpps) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] ready to print D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23228 (/usr/lib/cups/backend/hp) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] End of messages D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state=3(idle) D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-message="ready to print" D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-reasons=none doug@linux1:/var/log/cups> LogLevel debug If 'LogLevel' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LogLevel --doug
On 02/04/2021 01.04, Doug McGarrett wrote:
On 4/1/21 7:34 PM, Carlos E. R. wrote:
On 02/04/2021 00.06, DennisG wrote:
On 4/1/21 1:40 PM, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote: > > rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
libpoppler108 is the current TW version:
Unfortunately, libpoppler doesn't follow the name-version.minor.release naming convention. Instead apparently it uses nameversion-minor.release, which made the command to fail.
And probably some dependency is broken, because it should have been installed automatically before that, not requiring a manual installation. Went to the 'net and reinstalled the file via their automatic install function. Still doesn't print.
WHY? WHY on EARTH are you reinstalling things! :-/// DON'T EVER GO TO NET! Oh god... :-/ JUST POST THE LOG! Ok, here is the log. This is the ONLY thing you had to do. We asked you to post the log, nothing else. Just post the log, and wait. Now we have to figure out what else you have broken by "going to the net" :-/ Let's look at the log.
logfile (portion) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pdftops (PID 23229) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pstops (PID 23230) D [01/Apr/2021:18:51:36 -0400] [Job 373] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory
You still have not installed or you have removed libpoppler. It is apparently expecting version 106, and you installed 108 earlier today.
D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23229 (pdftops) stopped with status 127! D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -connecting-to-device D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -media-empty-error,media-jam-error,hplip.plugin-error,cover-open-error,toner-empty-error,other
Your printer is apparently jammed or something, too.
D [01/Apr/2021:18:51:36 -0400] [Job 373] The print file is empty. D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23230 (pstops) stopped with status 1! D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23226 (/usr/lib/cups/filter/pdftops) stopped with status 1. D [01/Apr/2021:18:51:36 -0400] [Job 373] Hint: Try setting the LogLevel to "debug" to find out more. *see below* D [01/Apr/2021:18:51:36 -0400] [Job 373] HP PS filter ENDS D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23227 (/usr/lib/cups/filter/hpps) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] ready to print D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23228 (/usr/lib/cups/backend/hp) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] End of messages D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state=3(idle) D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-message="ready to print" D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-reasons=none
doug@linux1:/var/log/cups> LogLevel debug If 'LogLevel' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LogLevel
What on earth do you expect that to do? It is not a command to type. It is something you can write in some config file, and we have not told you to do that, nor how. This is exasperating. Ok, do this, and only this: run: rpm -qa | grep libpopler copy the result in an email. run: zypper dup let it run to completion, don't post it. then run: rpm -qa | grep libpopler and copy the result to the same email. then reboot Then try to print one page and post everything new that appears on the log file /var/log/cups/error_log. just look at the timestamp when you tried to print and post everything after that timestamp. Don't try to do anything else. DON'T go to the NET. Don't try to repair it. You just post here and wait. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 1:58 AM, Simon Becherer wrote:
Sending the log files to the list would make this much shorter and save you a lot of time.
Am 01.04.21 um 04:49 schrieb Doug McGarrett:
D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1! this is your (ore one of your problems)
"the print file is empty" -> you send data to the printer, BUT the data file is empty.
check where you lost the libpoppler.so.106 file install it. (open yast, search for poppler and maybe force installation of the already installed package, first check if the file is somewhere inside) - sorry i do not know the commandline rpm or zypper command for this -
simoN
I have libpoppler 107 in /usr/share/licenses; libpoplar 107 in /usr/share/doc/packages; libpoppler 107-21.02.0-1.2.x86_64.rpm. These files are dated Feb 23 and Mar 17. There are 18 other libpoppler files, in /usr/lib64 and subdirectories of same, and six in /var/cache.zypp/packages/https-download.opensuse.org-316b27617x86_64 dated from Dec 7 to Mar 17. Also libpoppler-qt5.so1, and libpoppler-qt5.so1.27.0. None of them are lib.poppler.so.106 Trying to install 106: linux1:~ # zypper install libpoplar.so.106 Retrieving repository 'Packman Repository' metadata -----------------------------------------[\] Retrieving repository 'Packman Repository' metadata ......................................[done] Building repository 'Packman Repository' cache ...........................................[done] Retrieving repository 'openSUSE-Tumbleweed-Update' metadata ..............................[done] Building repository 'openSUSE-Tumbleweed-Update' cache ...................................[done] Loading repository data... Reading installed packages... 'libpoplar.so.106' not found in package names. Trying capabilities. No provider of 'libpoplar.so.106' found. Resolving package dependencies... Nothing to do. Now what? --doug
On 01/04/2021 19.00, Doug McGarrett wrote:
On 4/1/21 1:58 AM, Simon Becherer wrote:
Sending the log files to the list would make this much shorter and save you a lot of time.
Am 01.04.21 um 04:49 schrieb Doug McGarrett:
D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1! this is your (ore one of your problems)
"the print file is empty" -> you send data to the printer, BUT the data file is empty.
check where you lost the libpoppler.so.106 file install it. (open yast, search for poppler and maybe force installation of the already installed package, first check if the file is somewhere inside) - sorry i do not know the commandline rpm or zypper command for this -
simoN
I have libpoppler 107 in /usr/share/licenses; libpoplar 107 in /usr/share/doc/packages; libpoppler 107-21.02.0-1.2.x86_64.rpm. These files are dated Feb 23 and Mar 17. There are 18 other libpoppler files, in /usr/lib64 and subdirectories of same,
nononono. You have to ask YaST for the package. You are wasting time looking for the file.
Trying to install 106: linux1:~ # zypper install libpoplar.so.106
And you know this is the wrong use of the command. COMMON! What do you think look it up in yast means? Sigh... Man... just do "zypper install libpoppler" just that. As ALWAYS. Write a postit. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 30/03/2021 04.14, Doug McGarrett wrote:
On 3/29/21 9:34 PM, Carlos E.R. wrote:
On 29/03/2021 23.59, Doug McGarrett wrote:
I think this is getting off the problem--obviously the computer sees the printer-- it turns on the "in-use" light and the little green hosrseshoe indicator, it just doesn't actually print anything. I would think it was a printer problem, but it prints perfectly from a laptop running Mint Linux.
Well, the routine is the same as always: start with the logs. What log should I look for?
The same as every time you have had printer trouble. /var/log/cups/* You should also look back to other times you had printer trouble and review your actions then: <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/message/RZL6TZM3YN5Q4PJXE6FZBPCUU6LUFPPP/> <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/message/GA2MXB5TZ2Y32I4EQSWZG5OKS7PAJF7A/> <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/message/ODEODUKEMPUTJLQVC5NLHLMEECHPG534/> <https://lists.opensuse.org/archives/list/support@lists.opensuse.org/message/MDZUPBXV3AZBALZG6DORPLZQHG4BA6L5/> -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/28/21 9:34 PM, Mark Petersen wrote:
On Sunday, March 28, 2021 5:57:32 PM CDT Doug McGarrett wrote:
On 3/28/21 6:07 PM, Mark Petersen wrote:
On Sunday, March 28, 2021 2:23:01 PM CDT Doug McGarrett wrote:
The HP_LaserJet_Pro_M201dw installed and worked via YaST, but now is giving me trouble: if I send it a print job, the panel light goes on and says OK, and the green printer horseshoe light come on but the printer doesn't print. lpstat shows the file has been sent:
HP_LaserJet_Pro_M201dw-363 doug 15360 Sun 28 Mar 2021 03:17:28 PM EDT
How do I trouble shoot this and fix it, please? --doug Doug,
You sure have a lot of trouble with printers!
Are you connecting to this printer via USB or network? If it's via network maybe the printer got a different IP address - Hint - set a static IP address for the printer. Or the firewall is blocking communication.
So, how are are connecting to this printer?
Mark Doug,
There is no need to send a reply email to me, just send it to the list.
It's on the LAN. You say you connecting to it on the LAN. Are you connected via ethernet or wireless?
I just pinged its static IP and it came back OK. Zero packet loss. Ping generally uses port 80/443, so yes you can reach the printer. But printing via network doesn't use port 80/443.
If you open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer.
What does it say for Connection: ??
- I have 2 HP LaserJet Pro 400-M401dn's at work that work without issue daily for more than 2 years. These printers are very close to your M201dw.
Here is what it says for connection with the printer in my office. Connection: hp:/net/HP_LaserJet_400_M401dn?lp=172.20.10.32
What does yours say?
Mark
To answer your question, rather late, but better than never: HP LaserJet Pro M201dw-363 ID| Name| User| Size| Pages| State| Control| Unknown Withheld 15K 1 Stopped Reprint Job Cancel Move job ID| Name| User| --doug --doug
On 30/03/2021 21.05, Doug McGarrett wrote:
On 3/28/21 9:34 PM, Mark Petersen wrote:
On Sunday, March 28, 2021 5:57:32 PM CDT Doug McGarrett wrote:
On 3/28/21 6:07 PM, Mark Petersen wrote:
I just pinged its static IP and it came back OK. Zero packet loss. Ping generally uses port 80/443, so yes you can reach the printer. But printing via network doesn't use port 80/443.
If you open a web browser and browse to: localhost:631 this will load the CUPS webpage. Click on Printers in the top dark band. Then click on the Queue Name for the M201 printer.
What does it say for Connection: ??
- I have 2 HP LaserJet Pro 400-M401dn's at work that work without issue daily for more than 2 years. These printers are very close to your M201dw.
Here is what it says for connection with the printer in my office. Connection: hp:/net/HP_LaserJet_400_M401dn?lp=172.20.10.32
What does yours say?
Mark
To answer your question, rather late, but better than never:
HP LaserJet Pro M201dw-363
ID| Name| User| Size| Pages| State| Control| Unknown Withheld 15K 1 Stopped Reprint Job Cancel Move job ID| Name| User|
So, the printer is stopped. In the past, you learned how to restart it. So, do it. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (9)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E.R. -
DennisG -
Doug McGarrett -
Mark Peteren -
Mark Petersen
-
Simon Becherer -
TomasK