I have a CanoScan LiDE 100 but otherwise the exact same setup. I can fully confirm that this bug is caused by the new ibsane1 1.0.27-1~experimental packages and "fixed" by force replacing all sane packages with the 1.0.25 packages from Ubuntu 17.04.
Somebody also posted this on askubuntu: https://askubuntu.com/questions/973526/thick-black-vertical-line-with- canon-lide-100-scanner-in-ubuntu-17-10 So there are multiple users affected indeed. What I wasn't able to confirm yet is if the current stable release of sane-backends 1.0.27 might fix this or not. You can get it here: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane- release?field.series_filter= I also found an interesting correlation with this bug: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1712997 This seems to happen also on the old drivers for this user but the visual artifacts are very similar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1729077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
