stopped working...

[rogue-ronin]

The printer was working a couple of weeks ago, but today when I needed it - nothing.

I have permissions working properly, I think. The GUI recognizes the printer.

This feels like some update changed something... (xdotool stopped working properly too, but that's probably not helpful to you.)

EndeavourOS (Arch). XFCE4. X11. Kernel 6.17 and 6.12 - neither work.

The only other thing I noticed was that I can turn it off now - previously it would not turn off when the power light would blink. Which it would do when returning from suspend - a disconnect from USB and reconnect would restore the power light to solid. Now I can power it on and off whether the light is blinking or not.

I have not dropped or damaged the printer. I've pulled and reinstalled the cartridge and the battery (same ones, not new) and I've tried it with a fresh 9v battery and a different cartridge, but everything seems fine mechanically. I suppose it could have died in some other manner.

I've also tried switching to the Dymo CUPS drivers from the git repository, but no change so I've switched back. I've tried downgrading CUPS, no change. I've also swapped USB cables, just in case. No change.

Any ideas?

labelle-gui --verbose
[DEBUG] Active device configuration already found.
[DEBUG] Opened printer interface: <INTERFACE 0: Printer>
[DEBUG] Printing label..
[DEBUG] Sending chunk of 573 bytes
[DEBUG] Sending chunk of 567 bytes
[DEBUG] Sending chunk of 567 bytes
[DEBUG] Sending chunk of 103 bytes
[DEBUG] Post-send response: [64, 0, 129, 0, 7, 186, 0, 0]
[DEBUG] Sending chunk of 115 bytes
[DEBUG] Post-send response: [64, 0, 129, 0, 7, 132, 0, 0]
[DEBUG] Done printing.
[DEBUG] Cleaned up.

labelle -v test outputs

[DEBUG] Read config file: /home/rogue/.config/labelle.ini
[DEBUG] Found single device
[DEBUG] <DEVICE ID 0922:1002 on Bus 005 Address 005>
  manufacturer: Dymo
  product: DYMO LabelManager PnP
  serial: 01373819112015
  configurations:
  - <CONFIGURATION 1: 500 mA>
    interfaces:
    - <INTERFACE 0: Printer>
    - <INTERFACE 1: Mass Storage>
    - <INTERFACE 2: Human Interface Device>

[DEBUG] Recognized device as LabelManager PnP (mode switch)
[DEBUG] Active device configuration already found.
[DEBUG] Opened printer interface: <INTERFACE 0: Printer>
[DEBUG] Printing label..
[DEBUG] Sending chunk of 573 bytes
[DEBUG] Sending chunk of 567 bytes
[DEBUG] Sending chunk of 567 bytes
[DEBUG] Sending chunk of 103 bytes
[DEBUG] Post-send response: [64, 0, 130, 0, 7, 234, 0, 0]
[DEBUG] Sending chunk of 151 bytes
[DEBUG] Post-send response: [64, 0, 130, 0, 7, 213, 0, 0]
[DEBUG] Done printing.
[DEBUG] Cleaned up.

[maresb]

From the USB side this appears to be a successful print. What happens physically with your printer? Does it just do nothing?

One potential red flag for me is the 64 status code. I'm not sure exactly what this means, but see computerlyrik/dymoprint#43 (comment) for relevant discussion.

[rogue-ronin]

It does nothing.

I just tried an uninstall of labelle and a reinstall. Still nothing.

I may have to buy another one just to confirm it's not hardware... :(

Is there any way to monitor more closely that might help you?

Late here, gonna sleep but will check back in the morning.

Aloha!

[rogue-ronin]

I've ordered another printer; should be here in a week or so.

If you have any suggestions in the meantime, glad to follow up.

EDIT: I see that some changes to labelle (v1.4.1 to v1.4.2) happened in Arch on 09-SEP - that is likely after I previously used the printer. Maybe something changed there?

[maresb]

I've ordered another printer; should be here in a week or so.

That's definitely the most robust way forward. It'd be really helpful if you could follow up with your findings regarding new vs. old.

If you have any suggestions in the meantime, glad to follow up.

I'll let you know if I think of anything else. Maybe try removing and reinserting the cartridge, and make sure you're not operating it with the door open.

EDIT: I see that some changes to labelle (v1.4.1 to v1.4.2) happened in Arch on 09-SEP - that is likely after I previously used the printer. Maybe something changed there?

Very unlikely, all that release did was to prevent Labelle from using the latest (incompatible) release of python-barcode. See the release notes

[rogue-ronin]

I will also try the current one with a laptop tomorrow. Also on EndeavourOS but nowhere near as customized as my main rig.

[rogue-ronin]

Fresh install of labelle and dymo-print-drivers on a T480 running EndeavourOS. I adjusted the permissions in the udev rule and the printer showed in the gui. There were a lot of dependencies.

Same exact symptoms; I also switched out the print cartridge again just in case. labelle-gui --verbose still showing similar results.

I should have the new printer in a few days (hopefully - shipping from CA to HI is usually reasonable but who knows anymore?)

[rogue-ronin]

Got the new Dymo today - exact same behavior. It has to be some sort of (presumably updated) library issue?

[rogue-ronin]

So I uninstalled labelle (Arch) and got the following error on trying to reinstall:

fusermount3: failed to access mountpoint /run/user/1000/doc: Permission denied
error: fuse init failed: Can't mount path /run/user/1000/doc

[rogue-ronin]

Some combination of things have made the 2nd printer work! It wasn't working on first test, as described above.

There may have been a jam on the cartridge, and there were a few library updates. Does libboost have any influence over labelle?

However I did check the 1st printer and it is still not working - the cartridge from that one works in the 2nd printer.

Would the 1st printer be of any use to you? Glad to send it to you (no cost). It seems weird that it would just stop working...