Description of problem:
Updated to fc23, along came all the sane/xsane 1.0.25-1.fc23 packages and
my HP5300C scanner no longer works. (It's on USB)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. normal operation
Scanner is found by sane-find-scanner.
Scanner is found by scanimage -L, as root only, I think.
xsane doesn't work either as root or normal user, with a "Failed to sart scanner: Error during device I/O.
At this point device is wedged and one needs to kill xsane, unplug the scanner and plug it back in.
Downgraded to the fc22 1.0.24-14 versions and it work again.
Problem may be on sane-backends only, but I replaced all the xsane rpms too.
I have the same issue after upgrading to FC23 - scanner is found by sane-find-scanner, however xsane crashes immediately on loading.
Update - I managed to solve this by removing all modules referencing sane, then re-installing.
I have the same problem with CanoScan LiDE 210 flatbed scanner ('genesys' backend).
When I compiled the Gentoo Linux sane-backends in the chroot with the same devices from the Fedora working station and kernel, it works as expected.
Sorry for the late reply.
Henrique, Oleksander, can you reproduce this with the current development version of sane-backends? There are a number of USB related changes since 1.0.25 was released. Thanks!
Sorry, cant' test this anymore.
I still have that HP ScanJet up in storage but have since replaced it, along with my older printer, with a Brother network printer/scanner that not only saves space as it works fine with sane's network backend.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Sorry for my late response.
I have come to use CentOS 7 and there is no such an issue there with backends.
It is not so easy for me now to test the backends in Fedora, therefore.
Thank you for your support.
Thanks fo rthe info! In that case I'll close the bug.