I am trying to setup a print server with a Raspbian installed on a Raspberry PI Zero W.
The printer, connected via USB, is a mfp Samsung SCX-3400.
I have setup everything and i can print, but the printing time (between launch of the print on the client and the actual start of printing on the printer) is quite long... around 5 minutes and more.
Note: if i reboot the print server while has a job in the queue, the print job starts immediately when the raspberry restarts.
This and the debug log makes me think that the problem is an USB connection issue...
I launch the print here:
D [17/Jan/2023:23:54:51 +0100] [Client 7] POST /printers/Samsung_SCX-3400_Series HTTP/1.1
Then:
D [17/Jan/2023:23:54:54 +0100] [Job 44] Printing on printer with URI: usb://Samsung/SCX-3400%20Series?serial=Z6RRB8KD6A0045N&interface=1
D [17/Jan/2023:23:54:54 +0100] [Job 44] libusb_get_device_list=2
D [17/Jan/2023:23:54:54 +0100] [Job 44] STATE: +connecting-to-device
D [17/Jan/2023:23:54:54 +0100] cupsdMarkDirty(---J-)
D [17/Jan/2023:23:54:54 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Printing jobs and dirty files"
D [17/Jan/2023:23:54:54 +0100] cupsdMarkDirty(----S)
D [17/Jan/2023:23:54:54 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files"
D [17/Jan/2023:23:54:54 +0100] [Notifier] state=3
D [17/Jan/2023:23:54:54 +0100] [Notifier] PrinterStateChanged
D [17/Jan/2023:23:54:54 +0100] [Notifier] state=3
D [17/Jan/2023:23:54:54 +0100] [Job 44] STATE: -connecting-to-device
D [17/Jan/2023:23:54:54 +0100] cupsdMarkDirty(---J-)
D [17/Jan/2023:23:54:54 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Dirty files"
D [17/Jan/2023:23:54:54 +0100] cupsdMarkDirty(----S)
D [17/Jan/2023:23:54:54 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
D [17/Jan/2023:23:54:54 +0100] [Notifier] state=3
D [17/Jan/2023:23:54:54 +0100] [Notifier] PrinterStateChanged
D [17/Jan/2023:23:54:54 +0100] [Notifier] state=3
D [17/Jan/2023:23:54:54 +0100] [Job 44] Waiting for printer to become available.
After a few minutes (and several Waiting for printer to become available
...) the printer actually print the document...
D [17/Jan/2023:23:58:47 +0100] [Job 44] libusb_get_device_list=2
I [17/Jan/2023:23:58:47 +0100] Expiring subscriptions...
D [17/Jan/2023:23:58:47 +0100] [Job 44] STATE: +connecting-to-device
D [17/Jan/2023:23:58:47 +0100] cupsdMarkDirty(---J-)
D [17/Jan/2023:23:58:47 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Printing jobs and dirty files"
D [17/Jan/2023:23:58:47 +0100] cupsdMarkDirty(----S)
D [17/Jan/2023:23:58:47 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files"
D [17/Jan/2023:23:58:47 +0100] [Notifier] state=3
D [17/Jan/2023:23:58:47 +0100] [Notifier] PrinterStateChanged
D [17/Jan/2023:23:58:47 +0100] [Notifier] state=3
D [17/Jan/2023:23:58:47 +0100] [Job 44] Switching USB device configuration: 0 -> 1
D [17/Jan/2023:23:58:47 +0100] [Job 44] STATE: -connecting-to-device
D [17/Jan/2023:23:58:47 +0100] cupsdMarkDirty(---J-)
D [17/Jan/2023:23:58:47 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Dirty files"
D [17/Jan/2023:23:58:47 +0100] cupsdMarkDirty(----S)
D [17/Jan/2023:23:58:47 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
D [17/Jan/2023:23:58:47 +0100] [Notifier] state=3
D [17/Jan/2023:23:58:47 +0100] [Notifier] PrinterStateChanged
D [17/Jan/2023:23:58:47 +0100] [Notifier] state=3
D [17/Jan/2023:23:58:48 +0100] [Job 44] Device protocol: 2
D [17/Jan/2023:23:58:48 +0100] [Job 44] Sending data to printer.
D [17/Jan/2023:23:58:48 +0100] cupsdMarkDirty(---J-)
D [17/Jan/2023:23:58:48 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
D [17/Jan/2023:23:58:48 +0100] [Job 44] Set job-printer-state-message to "Sending data to printer.", current level=INFO
D [17/Jan/2023:23:58:48 +0100] [Job 44] PAGE: 1 1
I'd like to receive some hints... Is this really an usb issue? How I could possibly fix it?
Thanks...
Complete log here.