You are not logged in.
For some years I have had problems with my Samsung SCX4500W MFP - and it does work for printing but not scanning. When I last switched it on this morning, connected via USB, I had the following error lines in the journal:
Sep 02 11:18:04 home1 kernel: usb 3-4: new high-speed USB device number 4 using xhci_hcd
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x3 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x84 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x1 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x82 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 systemd[1]: Reached target Printer.
Sep 02 11:18:04 home1 systemd[1]: Created slice system-configure\x2dprinter.slice.
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x1 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 kernel: usb 3-4: ep 0x82 - rounding interval to 8 microframes, ep desc says 10 microframes
Sep 02 11:18:04 home1 systemd[1]: Started Configure Plugged-In Printer.
Sep 02 11:18:04 home1 kernel: usblp 3-4:1.1: usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B
Sep 02 11:18:04 home1 kernel: usbcore: registered new interface driver usblp
Sep 02 11:18:04 home1 udev-configure-printer[11216]: add usb-003-004
Sep 02 11:18:04 home1 udev-configure-printer[11216]: device devpath is /devices/pci0000:00/0000:00:14.0/usb3/3-4
Sep 02 11:18:04 home1 udev-configure-printer[11216]: udev_enumerate_scan_devices failed
Sep 02 11:18:04 home1 systemd[1]: configure-printer@usb-003-004.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 11:18:04 home1 systemd[1]: configure-printer@usb-003-004.service: Unit entered failed state
Sep 02 11:18:04 home1 systemd[1]: configure-printer@usb-003-004.service: Failed with result 'exit-code'.The line with "udev_enumerate_scan_devices failed" is in red in the journal.
Since the printer works fine but the scanner functions do not, presumably this indicates a problem with udev in dealing with the scanner part of the device?
I found a Fedora bug report which seemed analogous to this issue at https://fedorahosted.org/system-config- … ticket/244 in which an early section has a developer reporting that "dev-add-printer Python script has an incorrect line 1" and that it was fixed, but the problem recurred. I wonder if there remains a bug in the corresponding script for adding printers that is also in the code for udev-configure-printer for our arch packages?
Mike C
Offline
In the past few weeks I have found that provided I start the cups daemon before turning on the printer, and then stopping the cups daemon before turning off the printer then there are no failed systemd units once that is complete. Since I can't remember the specific order of starting and stopping the daemon and physical device previously I can't be sure if that was a contributory factor or not.
Mike C
Offline