Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DYMO USB serial number issue #271

Closed
mikestamat opened this issue Apr 9, 2023 · 5 comments
Closed

DYMO USB serial number issue #271

mikestamat opened this issue Apr 9, 2023 · 5 comments
Assignees
Labels
bug Something isn't working platform issue Issue is specific to an OS or desktop priority-medium
Milestone

Comments

@mikestamat
Copy link

I have three Dymo Labelwriters connected to a Raspberry Pi 3. Because Dymo does not report the printer serial number in the Device ID, I compiled OpenPrinting CUPS from source using the instructions @michaelrsweet described in this known issue: (OpenPrinting/cups#170) ... and also discussed here: (https://ubuntuforums.org/showthread.php?t=2441092)

The install was successful and lpinfo reported the unique device URIs for each printer. However, when attempting to add a printer via the CUPS web interface, the page would error out and checking the logs reported:
W [09/Apr/2023:16:14:41 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103

It appears the fix action is migrating away from OpenPrinting CUPS to lprint, but unfortunately the previous issue has surfaced again.
pi@rpi3:~ $ sudo snap run lprint server -o server-name=rpi3 -o server-port=632 -o auth-service=cups DYMO LabelWriter 450 (USB) (usb://DYMO/LabelWriter%20450?serial=01010112345600;MFG:DYMO;CMD: ;MDL:LabelWriter 450;CLASS:PRINTER;DESCRIPTION:DYMO LabelWriter 450;SERN:01010112345600;) -> dymo_lw-450 DYMO LabelWriter 450 (USB) (usb://DYMO/LabelWriter%20450?serial=01010112345600;MFG:DYMO;CMD: ;MDL:LabelWriter 450;CLASS:PRINTER;DESCRIPTION:DYMO LabelWriter 450;SERN:01010112345600;) -> dymo_lw-450 E [2023-04-09T20:44:42.257Z] Printer 'DYMO LabelWriter 450' already exists. DYMO LabelWriter 450 Turbo (USB) (usb://DYMO/LabelWriter%20450%20Turbo?serial=17082908152669;MFG:DYMO;CMD: ;MDL:LabelWriter 450 Turbo;CLASS:PRINTER;DESCRIPTION:DYMO LabelWriter 450 Turbo;SERN:17082908152669;) -> dymo_lw-450-turbo E [2023-04-09T20:44:42.264Z] Unable to register 'LPrint._ipps-system._tcp': Local name collision E [2023-04-09T20:44:43.328Z] Unable to register 'LPrint._ipps-system._tcp': Local name collision

Requesting a fix for lprint to handle this known Dymo bug.

@michaelrsweet michaelrsweet changed the title Local name collision for multiple Dymo Printers DYMO USB serial number issue Apr 11, 2023
@michaelrsweet michaelrsweet transferred this issue from michaelrsweet/lprint Apr 11, 2023
@michaelrsweet michaelrsweet self-assigned this Apr 11, 2023
@michaelrsweet michaelrsweet added bug Something isn't working priority-medium platform issue Issue is specific to an OS or desktop labels Apr 11, 2023
@michaelrsweet michaelrsweet added this to the v1.4 milestone Apr 11, 2023
@michaelrsweet
Copy link
Owner

Changed the title and moved to PAPPL, which is responsible for USB device support. There is workaround code in PAPPL but it doesn't kick in if the printer reports a serial number in the 1284 device ID...

DYMO is hardly the only offender in this behavior, but it is frustrating...

@mikestamat
Copy link
Author

Thanks for the quick reply! Standing by to test in v1.4

@michaelrsweet
Copy link
Owner

[master 92223bc] Use the USB device serial number instead of the 1284 serial number value (Issue #271)

[v1.3.x f1e45ef] Use the USB device serial number instead of the 1284 serial number value (Issue #271)

Need to test but this mirrors the CUPS USB backend.

@michaelrsweet
Copy link
Owner

OK, tests out on macOS and Linux.

@mikestamat
Copy link
Author

mikestamat commented Jun 18, 2023

Sorry for the n00b question, but how can I go about testing this? Since it appears you merged to master for this fix, I did git clone https://github.com/michaelrsweet/pappl and attempted to compile from source. I guess I need the cups developer package? Assuming I get pappl installed then do I need to compile lprint from source with configure referencing my pappl files?

I ask because I'm getting the following error on "make":

Compiling pwg-driver.c...
Linking testmainloop...
/usr/bin/ld: pwg-driver.o: in function pwg_rwriteline': /home/pi/pappl/testsuite/pwg-driver.c:772: undefined reference to cupsRasterWritePixels'
/usr/bin/ld: pwg-driver.o: in function pwg_rstartjob': /home/pi/pappl/testsuite/pwg-driver.c:616: undefined reference to cupsRasterOpenIO'
/usr/bin/ld: pwg-driver.o: in function pwg_rendjob': /home/pi/pappl/testsuite/pwg-driver.c:517: undefined reference to cupsRasterClose'
/usr/bin/ld: pwg-driver.o: in function pwg_rstartpage': /home/pi/pappl/testsuite/pwg-driver.c:641: undefined reference to cupsRasterWriteHeader2'
/usr/bin/ld: ../pappl/libpappl.a(job-process.o): in function papplJobCreatePrintOptions': /home/pi/pappl/pappl/job-process.c:416: undefined reference to cupsRasterInitPWGHeader'
/usr/bin/ld: ../pappl/libpappl.a(job-process.o): in function _papplJobProcessRaster': /home/pi/pappl/pappl/job-process.c:599: undefined reference to cupsRasterOpenIO'
/usr/bin/ld: /home/pi/pappl/pappl/job-process.c:607: undefined reference to cupsRasterReadHeader2' /usr/bin/ld: /home/pi/pappl/pappl/job-process.c:841: undefined reference to cupsRasterClose'
/usr/bin/ld: /home/pi/pappl/pappl/job-process.c:704: undefined reference to cupsRasterReadPixels' /usr/bin/ld: /home/pi/pappl/pappl/job-process.c:769: undefined reference to cupsRasterReadPixels'
/usr/bin/ld: /home/pi/pappl/pappl/job-process.c:819: undefined reference to `cupsRasterReadHeader2'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:73: testmainloop] Error 1
make: *** [Makefile:28: all] Error 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working platform issue Issue is specific to an OS or desktop priority-medium
Projects
None yet
Development

No branches or pull requests

2 participants