Scanning using a PiXMA MG5350 became extremely unreliable (to the point of only about a 5% chance of completing an A4 colour scan) with 1.0.27, having been completely reliable on 1.0.25. Downgrading to 1.0.25 (https://koji.fedoraproject.org/koji/buildinfo?buildID=871897) results in reliable scans again. I think this is probably: https://alioth.debian.org/tracker/index.php?func=detail&aid=315827&group_id=30186&atid=410366 Given that sane-backends releases appear only about every 2 years, is Fedora able to backport fixes from their Git?
Hi Stephen, thank you for reporting this issue, sure, I'll backport it into Fedora - thank you for providing actual issue, it is a great help! I'll build the testing package for you and then push it into Fedora.
Thanks Zdenek! Let me know when you have a test build and I'll give it a try.
Stephen, there is scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=22569443 , would you mind testing it?
sane-backends-1.0.27-6.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e629dc0086
Thanks for the rapid turnaround on the build! Unfortunately, it seems like it might be a different issue from the one I linked to - the scratch build has the same problem - manages maybe a page at most; most scans fail partway through the page. Downgrading to 1.0.25 again resulted in multiple pages scanning fine. Did you cherry-pick from upstream, or just build from head? I had a look at Rolf's patches from 31/8, and it looks like they actually fix failing to handle an "end of scan" message, rather than the problem of scans failing part-way. If it's the current Git head, I'll file a bug upstream; if it's a cherry-pick, can you maybe do a scratch build of head? :)
sane-backends-1.0.27-6.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e629dc0086
I took patch from Rolf's commit 450e55c2309d372a088ef963082252fd2f27c524 . Other patch from 31.8. is changing only build number, so I thought it is not necessary to backport. I'll provide you scratch build with upstream head, but be aware, it can break something else - so I would like to backport only patch for this issue (if there is in upstream) after that - would you mind helping me with cherry-picking then (mostly testing created packages)?
Scratch build of current upstream git: https://koji.fedoraproject.org/koji/taskinfo?taskID=22644985
Thanks Zdenek. Still the same problem with the head build unfortunately so looks like it's definitely not the upstream bug that I thought. I'll file a new bug with sane-backends. Thanks!
Stephen, would you mind sharing link to upstream issue here after you create it?
NP. https://alioth.debian.org/tracker/index.php?func=detail&aid=315860
Thank you, Stephen!
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.