Ask Your Question
2

F28 cups not printing: using usb to paralell port adapter cable with HP LaserJet 1100 printer

asked 2018-08-24 15:23:43 -0600

Generic User gravatar image

updated 2018-09-06 16:47:16 -0600

After sending a job to my printer there is no printer activity. Checking the printer queue shows 1 job processing; however, the printer shows no activity.

So I check the logs using the following command: journalctl -b -p err

In the journal error output, I find the entries related to cupsd:

cupsd[nnn]: [CGI] cups-brf must be called as root
cupsd[nnn]: [cups-deviced] PID 13104 (cups-brf) stopped with status 1!

Some relevant details:

  • Fedora Linux version 28 - Server edition
  • Kernel version (uname -r): 4.17.17-200.fc28.x86_64
  • cups.x86_64 version: 1:2.2.6-18.fc28
  • cups-filters.x86_64 version: 1.20.0-9.fc28

Although the following might not have any bearing, the printer is a HP LaserJet 1100 which has a parallel port connector connected to a parallel port to usb adapter with the usb end connected to the computer.

Does anyone else have this problem and have they solved it?

edit retag flag offensive close merge delete

Comments

cups-brf is the backend for a braille printer, and your error message is most likely irrelevant. Check the timestamp of the message.

I would guess that the issue is with the parallel port to usb adapter. A google search for "usb parallel port adapter linux" shows some hits which might be relevant.

villykruse gravatar imagevillykruse ( 2018-08-25 04:56:39 -0600 )edit

2 Answers

Sort by ยป oldest newest most voted
1

answered 2018-09-05 22:42:31 -0600

Generic User gravatar image

updated 2018-09-06 16:43:52 -0600

Thanks for your responses! I was away for a week vacation so I had to leave this problem alone. Now that I am back and I can pay more attention to it, I have come to the following discovery:

  1. With the response from villykruse, I went back to what I did suspect all along, that the usb-to-parallel-port-adapter-cable connection might be causing difficulties; although, I have to point out that I have been printing just fine up until about a month and a half ago. I first started having problem around August 25th, when I wanted to print something. So it may be possible that upgrades may have changed something in CUPS or in usb device handling that I am checking into right now.
  2. systemctl --state=failed yielded a related service failure: configure-printer@usb-003-003.service loaded failed failed Configure Plugged-In Printer. The "usb-003-003" interface descriptor refers to the usb port where the usb-to-parallel-port-adapter-cable is connected and so there is where my problems start.
  3. Next, from the output of lsusb (I cannot upload as yet so I have to summarize) the relevant line is Bus 003 Device 003: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port. So far, it appears that the usb discovery is seeing the usb-to-parallel adapter correctly; however, it is failing to discover the printer connected on the other end.
  4. From the output of systemctl status configure-printer@usb-003-003.service, it showed that the actual executable, "udev-configure-printer add usb-003-003" was failing (ie: returning 1 instead of 0) so it appears that the problem is in the code that is trying to discover the printer at the designated usb port.
  5. At first, this might seem like it is a straight-forward bug report; however, as some issues turn out to be more than meet the eye, this one is certainly one of those. Apparently, there are 2 ways of accessing a printer connected via usb (one is via 'libusb' and the other is through the kernel module 'usblp') and it is unclear whether udev-configure-printer is aware of both of them. I am guessing that it is using 'libusb' and is not aware of 'usblp'. After reading through some of the problems that others have been having with 'usb-to-parallel-port' adapters (as suggested by villykruse), it seems that I should still be able to print using the kernel module 'usblp'. So the question becomes can I ignore the udev-configure-printer failure and just connect using 'usblp'? Up until a month and a half ago, I have been using the 'usblp' method without any problems until now, so it seems that CUPS and systemd are dropping compatibility with 'usblp' in favor of 'libusb'?
  6. Just to document this issue so that others might be spared some of the pain that some of us have already been through, I decided to double check whether I have set up my printer to work with the kernel module 'usblp' correctly. lsmod | grep usblp shows that the 'usblp' module is loaded.
  7. journalctl -b | grep usblp showed kernel: usblp 3-2:1 ...
(more)
edit flag offensive delete link more

Question Tools

2 followers

Stats

Asked: 2018-08-24 15:05:16 -0600

Seen: 395 times

Last updated: Sep 06 '18