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

edit

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 ...