An 'EACCES' error is an OS permission problem, and to me seems like the USB port/cable is flaky, leading to the printer being repeatedly re-enumerated on the bus with udev not being able to fix up permissions before it is accessed by CUPS. That said, CUPS will access it as root anyway, so it's not clear why EACCES would ever be an issue. As for BUSY, that could indeed happen if multiple things try to probe the printer simultaneously, but that shouldn't be happening either as CUPS serializes all access...
dyesub: backend: Roll up some bugfixes.
cups: Don't recognize "ARGB" (really RGBA)
cups: Recognize CUPS_CSPACE_SRGB and CUPS_CSPAGE_ARGB
Citizen CZ-01 can only print 4x4
Oh, you're using the gutenprint-printer-app on ubunbu. I honestly have no idea if that works properly; I use standalone CUPS + gutenprint directly using the lp command flow (with explicitly specified sizes) rather than whatever mechanism the app uses to route cmdline prints and select the size that gets used. (Also, my tests were done on a DNP QW410 which is programatically identical to the CZ-01)
Oh, you're using the gutenprint-printer-app on ubunbu. I honestly have no idea if that works properly; I use standalone CUPS + gutenprint directly. (Also, my tests were done on a DNP QW410 which is programatically identical to the CZ-01)
2025 Gutenprint breaks drivers because it doesn't support old format