| Summary: | >=media-gfx/sane-backends-1.0.27 does not recognize Samsung SCX-4725FN scanner | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | edes <edes> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | edes |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
edes
2018-04-16 12:42:53 UTC
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4a4aa9c04d755547aa82b881499fd7a6172bfc9 commit b4a4aa9c04d755547aa82b881499fd7a6172bfc9 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2018-10-20 15:11:29 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2018-10-20 16:35:31 +0000 media-gfx/sane-backends: Fixes from Fedora and Debian... They fix an important bug with Samsung devices not being properly recognized and noises in some devices. We also start disabling locking as all the other distributions and stop trying to randomly generate extra documentation files that are not really needed and add a lot of hidden dependencies tend to break in several ways. Closes: https://bugs.gentoo.org/636202 Closes: https://bugs.gentoo.org/653300 Closes: https://bugs.gentoo.org/668232 Closes: https://bugs.gentoo.org/668350 Signed-off-by: Pacho Ramos <pacho@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 .../sane-backends-1.0.27-revert-samsung.patch | 406 +++++++++++++++++++++ ...ne-backends-1.0.27-uninitialized-variable.patch | 25 ++ .../sane-backends/sane-backends-1.0.27-r2.ebuild | 344 +++++++++++++++++ 3 files changed, 775 insertions(+) It's working now again with my Samsung SCX-4725FN, thank you! There's only one minor problem: it spends a long time scanning for devices, and it takes like half a minute to recognize the printer/scanner. Previous versions recognized the device immediately. Other than that, it's working fine. Maybe that is caused by this fix:
eapply "${FILESDIR}"/${PN}-1.0.27-uninitialized-variable.patch
you can try commenting that line to see if it improves again
|