when i try to print here is an error message i have :
> lpstat -p -d
printer Lexmark_Pro800Pro900_Series now printing Lexmark_Pro800Pro900_Series-148. enabled since mar. 22 juil. 2014 09:45:33 CEST
/usr/lib/cups/backend/lxhcp failed
system default destination: Lexmark_Pro800Pro900_Series
The pc canāt reach the printer ( /usr/lib/cups/backend/lxhcp failed ).
On 2014-07-22 10:56, manchette fr wrote:
>
> hello
>
> when i try to print here is an error message i have :
>
>> lpstat -p -d
> printer Lexmark_Pro800Pro900_Series now printing
> Lexmark_Pro800Pro900_Series-148. enabled since mar. 22 juil. 2014
> 09:45:33 CEST
> /usr/lib/cups/backend/lxhcp failed
> system default destination: Lexmark_Pro800Pro900_Series
A comment: When pasting here computer commands and such, please use a
CODE BLOCK, so that the forum software doesnāt do silly things like
converting URLS to tiny urls or otherwise hide or alter the commands you
entered. You get them by clicking on the ā#ā button in the forum editor. See photo
> The pc canāt reach the printer ( /usr/lib/cups/backend/lxhcp failed ).
>
> Can you please help me understand why ?
You can increase cups log verbosity. In ā/etc/cups/cupsd.confā change
āLogLevel debugā, and restart the service:
Iām not familiar with Lexmark hardware, but just to get the background to this, I presume you started by installing the driver from the Lexmark site, and downloaded lexmark-inkjet-legacy-wJRE-1.0-1.x86_64.rpm.sh.tar.gzā or similar? I wonder if the install completed? I note that part of the install adjusts the firewall to open UDP port 5353. Just in case this failed, you might want to check this port, or disable the firewall
I also note that there are two versions of the proprietary driver available - one with JRE, and one without. Hopefully, a Lexmark user can chime in with further advice. You may need to obtain support via Lexmark since it is a proprietary driverā¦
I also note (following a quick check of CUPS) that there is a postsctipt driver available for the Lexmark Pro800-Pro900 Series. Have you tried using that (albeit that it may only provide basic functionality)?
Well, there seems to be a communication issue with the printer as reported here:
E [22/Jul/2014:15:24:21 +0200] [Job 149] Erreur d'imprimante. L'imprimante ne peut pas communiquer avec l'ordinateur.
and the the following CUPS message
(/usr/lib/cups/backend/lxhcp) stopped with status 1.
which might suggest that the printer has paused, or some other error condition is present perhaps. What is shown about the printer in /etc/cups/printers.conf? Check the status via the CUPS web interface
http:localhost:631/printers
Maybe it can resumed from there if necessary.
BTW, you didnāt tell us how this printer is connected (ie ethernet, usbā¦)
Okay, that all looks good. How did you configure your printer? Did you use the ā/usr/local/lexmark/legacy/bin/.scripts/lxtoolboxā utility? Were you able to print a test page during this process?
What happens when you try to run the backend manually?
/usr/local/lexmark/legacy/bin/lxhcp
It may take several seconds for its query to complete or timeout. Do you get any output? If not, maybe there is no packets getting to the printer (ie router or firewall issue perhaps).
to install i followed the gui guide provided during the driver install, i have not really added specifical rules but for the error policy which i set to āretry jobā.
manually it says ācommand not foundā :
linux-opensuse131:~ # /usr/local/lexmark/legacy/bin/lxhcp
/usr/local/lexmark/legacy/bin/lxhcp: line 1: fabrice@linux-opensuse131:~:: command not found
linux-opensuse131:/usr/local/lexmark/legacy/bin # ls
.scripts demond lxhcp printfilter rootme slogcap surunner
I note from examining your printers.conf, that the printer is referenced by its discovered hardware MAC address
DeviceURI lxhcp://00200067AB79
It is possible to use the IP address instead (assuming it has been configured previously). If you have a Windows environment, you might want to consider setting up the printer address to match your network environment. Having said that, the lxhcp backend should be able to cope with either method (as long as the communication packets are able to get to the printer).
In an effort to help, I ran the setup utility (as root) using
/usr/local/lexmark/legacy/bin/.scripts/lxtoolbox
and note that there is an option to āLet me specify an IP addressā, then once the correct āmodelā is chosen it is possible to add an IP address manually. Of course, I donāt have the printer, so canāt really test further.
hi,
yes, itās possible to set an ip, but while installing itās as easy to select the printerās name in the list provided, i guess it should be ok.
Well, the driver is capable of using layer 2 communication (assuming the network is transparent at that level), but sometimes layer 3 (using IP addressing) is necessary. For example, Iāve observed strange behaviour when a printer is connected to router via wired ethernet, and a PC is connected via wireless link on the same network. It āappearsā to be a communication-related issue, but I guess the setup utility was able to discover the device in the first place. I think it is worth perusing (but youāll probably need to configure it via Windows first).
If communication was working, running the backend manually should have produced some output (following communication with the discovered printer)
/usr/lib/cups/backend/lxhcp
From what Iāve read, I think it uses some hybrid mDNS-type discovery broadcast.
I donāt want to confuse you, but there are some good workarounds mentioned in this Puppy Linux forum
actually i know there 's something wrong but iād like to understand how come when it was working a few days ago. ā/usr/lib/cups/backend/lxhcp failedā in cups shows printer canāt be reached but i donāt get why.
i already had port 5353 open and added mDNS service in the firewall but it does not help.
You didnāt mention that before. Can you make sure that any existing print jobs are cancelled?
ā/usr/lib/cups/backend/lxhcp failedā in cups shows printer canāt be reached but i donāt get why.*
Me neither, but I have been encouraging you to run the backend manually with the printer connected and report back with the output (if any). If it fails, we have a communication issue. Do you have any other machines that can reach this printer successfully?
Actually yes, i should have said it earlier.
I can see the results in Cups, i have the list of tasks and i had to erase each task not successfull ( for if not an error message keeps coming all the time) .
Actually yes, i should have said it earlier.
I can see the results in Cups, i have the list of tasks and i had to erase each task not successfull ( for if not an error message keeps coming all the time) .
One quick way of doing that via CLI, would be
cancel -a
When i run manually i have no result in console
/usr/lib/cups/backend/lxhcp
Okay, well your printer should be annunciated (by MAC address) when it is run. You might try disabling your firewall temporarily
systemctl stop SuSEfirewall2.service
then run the command again. If it works, we a have a firewall issue to fix.
I couldnāt see anything unusual in the log.
I have a windows 8 machine nearby, on ethernet too and this one prints ok.
Good to know.
I guess you could use it (or via the printer front panel perhaps) to configure a valid IP address. Then try using the lxtoolbox utility to try an reconfigure for CUPSā¦
linux-opensuse131:~ # /usr/lib/cups/backend/lxhcp
linux-opensuse131:~ # systemctl stop SuSEfirewall2.service
linux-opensuse131:~ # /usr/lib/cups/backend/lxhcp
nothing is returned in console, see below the error log :
D [29/Jul/2014:15:42:18 +0200] cupsdAcceptClient: 12 from localhost (Domain)
D [29/Jul/2014:15:42:18 +0200] Report: clients=1
D [29/Jul/2014:15:42:18 +0200] Report: jobs=63
D [29/Jul/2014:15:42:18 +0200] Report: jobs-active=0
D [29/Jul/2014:15:42:18 +0200] Report: printers=1
D [29/Jul/2014:15:42:18 +0200] Report: printers-implicit=0
D [29/Jul/2014:15:42:18 +0200] Report: stringpool-string-count=25790
D [29/Jul/2014:15:42:18 +0200] Report: stringpool-alloc-bytes=11232
D [29/Jul/2014:15:42:18 +0200] Report: stringpool-total-bytes=470784
D [29/Jul/2014:15:42:18 +0200] cupsdReadClient: 12 POST / HTTP/1.1
D [29/Jul/2014:15:42:18 +0200] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [29/Jul/2014:15:42:18 +0200] cupsdAuthorize: No authentication data provided.
D [29/Jul/2014:15:42:18 +0200] cupsdReadClient: 12 1.1 CUPS-Get-Printers 1
D [29/Jul/2014:15:42:18 +0200] CUPS-Get-Printers
D [29/Jul/2014:15:42:18 +0200] Returning IPP successful-ok for CUPS-Get-Printers (no URI) from localhost
D [29/Jul/2014:15:42:18 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
D [29/Jul/2014:15:42:18 +0200] cupsdReadClient: 12 POST / HTTP/1.1
D [29/Jul/2014:15:42:18 +0200] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [29/Jul/2014:15:42:18 +0200] cupsdAuthorize: No authentication data provided.
D [29/Jul/2014:15:42:18 +0200] cupsdReadClient: 12 1.1 CUPS-Get-Classes 1
D [29/Jul/2014:15:42:18 +0200] CUPS-Get-Classes
D [29/Jul/2014:15:42:18 +0200] Returning IPP successful-ok for CUPS-Get-Classes (no URI) from localhost
D [29/Jul/2014:15:42:18 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
D [29/Jul/2014:15:42:18 +0200] cupsdReadClient: 12 WAITING Closing on EOF
D [29/Jul/2014:15:42:18 +0200] cupsdCloseClient: 12
D [29/Jul/2014:15:42:18 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
In the set up of the printer thereās allready an IP adress being used , iām gonna try to use this in the lxtoolbox utility.
actually this toolbox is only usefull about cartridges, cleaning them for example , printing a test page also and adding a wifi connection to the printer.
(*edit : ok i was going to post this when i suddenly saw 3 windows popping up and allowing me to choose the IP , i guess there was a delay for i tried to add a new printer a bit before using the big + icon , i was then able to set the ip in the utility box menu)
can i leave DHCP On in the printer menu or is it better to turn it Off ? (itās On now, i donāt want to disturb the behavior of the windows machine as itās working ok)
Thanks
ps : adding the IP using DHCP finally allowed printing ! Notice that i never had to do so before i guess itās the safer way , it looks like mac adress can be ālostā sometimes.
Nothing returned from the running the backend essentially means that your printer was not discovered following the broadcast packet(s). The log doesnāt really tell me what was failing, and it would probably take some tcpdump analysis to get a better idea about what was wrong.
In the set up of the printer thereās allready an IP adress being used , iām gonna try to use this in the lxtoolbox utility.
actually this toolbox is only usefull about cartridges, cleaning them for example , printing a test page also and adding a wifi connection to the printer.
(*edit : ok i was going to post this when i suddenly saw 3 windows popping up and allowing me to choose the IP , i guess there was a delay for i tried to add a new printer a bit before using the big + icon , i was then able to set the ip in the utility box menu)
Yep, the delay results from an initial broadcast to get the printer to respond by MAC addressing.
can i leave DHCP On in the printer menu or is it better to turn it Off ? (itās On now, i donāt want to disturb the behavior of the windows machine as itās working ok)
Thanks
ps : adding the IP using DHCP finally allowed printing ! Notice that i never had to do so before i guess itās the safer way , it looks like mac adress can be ālostā sometimes.
Just be careful about having a dynamically-assigned IP address. Usually, it is possible to assign a static (fixed) address for printers. Many domestic routers, do hand out the same address to specific devices (identified by their MAC addresses), but not all. If the IP address changes for some reason, then youāll have to adjust the URI in /etc/cups/printers.conf accordingly.
Anyway, Iām glad we finally got your printer working from your *nix box.