When trying to use a HP Deskjet F2100 series AIO to scan, I noticed that it wasn't working. When I plug the device in, I see the following in the dmesg: [10414.661192] usb 5-1: new full-speed USB device number 5 using uhci_hcd [10414.847295] usb 5-1: New USB device found, idVendor=03f0, idProduct=7d04 [10414.847298] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10414.847300] usb 5-1: Product: Deskjet F2100 series [10414.847302] usb 5-1: Manufacturer: HP [10414.847303] usb 5-1: SerialNumber: CN7B84P67T0505 [10414.853475] usblp 5-1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x7D04 [10420.279685] usblp0: removed [10420.285823] usblp 5-1:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x03F0 pid 0x7D04 [10420.876945] udev-add-printe[7144]: segfault at 0 ip 00007f2a8ac5a79b sp 00007ffceba7ce38 error 6 in libffi.so.6.0.2[7f2a8ac55000+7000] # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error found USB scanner (vendor=0x0bda [Realtek], product=0x2838 [RTL2838UHIDIR]) at libusb:001:002 found USB scanner (vendor=0x03f0 [HP], product=0x7d04 [Deskjet F2100 series]) at libusb:005:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
I also notice the following in the journal: systemd-coredump[7171]: Process 7144 (udev-add-printe) of user 0 dumped core. Stack trace of thread 7144: #0 0x00007f2a8ac5a79b ffi_prep_closure_loc (libffi.so.6) #1 0x00007f2a857abb6d b_callback (_cffi_backend.cpython-36m-x86_64-linux-gnu.so) #2 0x00007f2a857abe8b _ffi_callback_decorator (_cffi_backend.cpython-36m-x86_64-linux-gnu.so) #3 0x00007f2a96334505 _PyCFunction_FastCallDict (libpython3.6m.so.1.0) #4 0x00007f2a9633bc0a call_function (libpython3.6m.so.1.0) #5 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #6 0x00007f2a962ca545 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #7 0x00007f2a962fe5bf fast_function (libpython3.6m.so.1.0) #8 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #9 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #10 0x00007f2a96348c87 PyEval_EvalCodeEx (libpython3.6m.so.1.0) #11 0x00007f2a96349a3b PyEval_EvalCode (libpython3.6m.so.1.0) #12 0x00007f2a96376ff7 builtin_exec (libpython3.6m.so.1.0) #13 0x00007f2a963347c0 PyCFunction_Call (libpython3.6m.so.1.0) #14 0x00007f2a9637e8f6 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #15 0x00007f2a962ca103 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #16 0x00007f2a962fe5bf fast_function (libpython3.6m.so.1.0) #17 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #18 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #19 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #20 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #21 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #22 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #23 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #24 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #25 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #26 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #27 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #28 0x00007f2a962cae4a _PyFunction_FastCallDict (libpython3.6m.so.1.0) #29 0x00007f2a962cb4ae _PyObject_FastCallDict (libpython3.6m.so.1.0) #30 0x00007f2a963105ee _PyObject_CallMethodIdObjArgs (libpython3.6m.so.1.0) #31 0x00007f2a962c0674 PyImport_ImportModuleLevelObject (libpython3.6m.so.1.0) #32 0x00007f2a9637b71b _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #33 0x00007f2a96348c87 PyEval_EvalCodeEx (libpython3.6m.so.1.0) #34 0x00007f2a96349a3b PyEval_EvalCode (libpython3.6m.so.1.0) #35 0x00007f2a96376ff7 builtin_exec (libpython3.6m.so.1.0) #36 0x00007f2a963347c0 PyCFunction_Call (libpython3.6m.so.1.0) #37 0x00007f2a9637e8f6 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #38 0x00007f2a962ca103 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #39 0x00007f2a962fe5bf fast_function (libpython3.6m.so.1.0) #40 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #41 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #42 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #43 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #44 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #45 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #46 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #47 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #48 0x00007f2a962fe38a fast_function (libpython3.6m.so.1.0) #49 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0) #50 0x00007f2a96378f6a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #51 0x00007f2a962cae4a _PyFunction_FastCallDict (libpython3.6m.so.1.0) #52 0x00007f2a962cb4ae _PyObject_FastCallDict (libpython3.6m.so.1.0) #53 0x00007f2a963105ee _PyObject_CallMethodIdObjArgs (libpython3.6m.so.1.0) #54 0x00007f2a962c0674 PyImport_ImportModuleLevelObject (libpython3.6m.so.1.0) #55 0x00007f2a9637b71b _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #56 0x00007f2a96348c87 PyEval_EvalCodeEx (libpython3.6m.so.1.0) #57 0x00007f2a96349a3b PyEval_EvalCode (libpython3.6m.so.1.0) #58 0x00007f2a96376ff7 builtin_exec (libpython3.6m.so.1.0) #59 0x00007f2a963347c0 PyCFunction_Call (libpython3.6m.so.1.0) #60 0x00007f2a9637e8f6 _PyEval_EvalFrameDefault (libpython3.6m.so.1.0) #61 0x00007f2a962ca103 _PyEval_EvalCodeWithName (libpython3.6m.so.1.0) #62 0x00007f2a962fe5bf fast_function (libpython3.6m.so.1.0) #63 0x00007f2a9633bcce call_function (libpython3.6m.so.1.0)
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.