I installed sane-backends, sane-backends-autoconfig, xsane, and sane-hplip. Yast recognized my Canon Canoscan LIDE 200 scanner and chose the corresponding genesys backend. However, when I try using xsane to scan a text file and have the output formatted as a pdf file, there is a dark line down the center. Has anyone else who has encountered this problem overcome it?
How annoying! A quick online search turned up a another report in this askubuntu thread. It contained a link to this bug report
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459
No resolution yet, but you may be able to downgrade sane perhaps.
Same issue with the CanoScan LiDE 100 in Leap 15.
https://software.opensuse.org/package/sane-backends
Has a 1-click install community edition 1.0.25 under Tumbleweed and 42.3 – they are the same one.
I installed from the Tumbleweed list, over the preinstalled 1.0.27 version.
zypper search -s- sane-backends
showed
S | Name | Type | Version | Arch | Repository
—±--------------------------±-----------±-----------------------------±-------±----------------------
i+ | sane-backends | package | 1.0.25-1.226 | x86_64 | (System Packages)
v | sane-backends | package | 1.0.27.git20190202-lp150.1.3 | x86_64 | home:Sauerland
v | sane-backends | package | 1.0.27-lp150.4.1 | x86_64 | openSUSE-Leap-15.0-Oss
| sane-backends | srcpackage | 1.0.27.git20190202-lp150.1.3 | noarch | home:Sauerland
| sane-backends-32bit | package | 1.0.27-lp150.4.1 | x86_64 | openSUSE-Leap-15.0-Oss
v | sane-backends-autoconfig | package | 1.0.27.git20190202-lp150.1.3 | x86_64 | home:Sauerland
i+ | sane-backends-autoconfig | package | 1.0.27-lp150.4.1 | x86_64 | openSUSE-Leap-15.0-Oss
| sane-backends-devel | package | 1.0.27.git20190202-lp150.1.3 | x86_64 | home:Sauerland
| sane-backends-devel | package | 1.0.27-lp150.4.1 | x86_64 | openSUSE-Leap-15.0-Oss
| sane-backends-devel-32bit | package | 1.0.27-lp150.4.1 | x86_64 | openSUSE-Leap-15.0-Oss
(Sorry - won’t keep spaces)
It worked after a restart.
For future reference, when posting output enclose it within CODE tags to preserve formatting (refer to the ‘#’ button in the forum editor).