Closed proski closed 5 months ago
On Linux you need to run lprint as root or be a member of the group that owns the USB device files.
Thank you! Indeed, running lprint as root gave me the correct URI. It has an extra space encoded as %20
after Munbyn
.
usb://Munbyn%20/ITPP941?serial=9412033000184
The new URL is working (with a lot of struggle, not directly related to this issue). I was able to print a PDF document from an Android phone. I still cannot print anything locally, but that would be better discussed in another issue.
Maybe lprint should print a warning that it cannot access USB devices?
Also, it's not good that lpinfo -v
and lprint devices
produce different URIs. Maybe one of them should be modified to match the other? Then the USB device matching code should accept differences in spacing in URIs vs devices.
First, that's a highly system-specific thing. I can't even make it a Linux conditional because every distro supports USB slightly differently... :/
Second, the legacy USB URIs that CUPS 2.x puts out are specific to CUPS 2.x and are NOT a standardized thing. PAPPL (which LPrint uses) generates similar URIs but the values are what PAPPL and libusb require.
I'm using the current master branch of lprint on up-to-date Fedora 39 x86_64 with pappl 1.4.4 and CUPS 2.4.7.
lprint fails to see the Munbyn ITPP941 label printer. It sees other printers.
lpinfo sees the label printer.
Adding the printer appears to work (
lprint server
is running in another terminal):However, the server cannot see the printer:
Nothing gets printed.
lsusb output for the printer:
I'm surprised that "Munbyn" and "ITPP941" don't even appear in lsusb output, yet lpinfo uses them in the URI.