[sane-devel] Canon LiDE 50 CanoScan (04a9:2213) is broken with 1.0.20

2009-06-22 Thread Ozan Çağlayan
Hi, I've just noticed that my Canon LiDE 50 is broken with sane-backends 1.0.20 (1.0.19 was OK). I've bisected it to: e026a4fa2c72f71a3a8b79755a36d32ae4cddecb is first bad commit commit e026a4fa2c72f71a3a8b79755a36d32ae4cddecb Author: Pierre Willenbrock Date: Mon Feb 23 14:20:39 2009 +

[sane-devel] Canon LiDE 50 CanoScan (04a9:2213) is broken with 1.0.20

2009-06-22 Thread Ozan Çağlayan
Pierre Willenbrock wrote: > Thanks for bisecting, but this bug should be fixed in git master. See > bug #311691. > Argh, I took a look at the commits after RELEASE_1_0_20 but that didn't catch my attention at all. I'll grab/try the patch tomorrow. Thanks!

[sane-devel] [PATCH] Avision backend: Mark FCPA 620C with AV_LIGHT_CHECK_BOGUS

2009-06-23 Thread Ozan Çağlayan
backend/avision.c: Mark Fujitsu ScanPartner 620C with AV_LIGHT_CHECK_BOGUS as it currently refuses to work through avision after 90 tries: scanimage --device=avision:/dev/sg0 --source ADF --mode Color [sanei_debug] Setting debug level of avision to 7. [avision] sane_init:(Version: 1.0 Build: 290)

[sane-devel] [PATCH] Avision backend: Mark FCPA 620C with AV_LIGHT_CHECK_BOGUS

2009-06-23 Thread Ozan Çağlayan
Ozan ?a?layan wrote On 23-06-2009 12:48: > backend/avision.c: Mark Fujitsu ScanPartner 620C with > AV_LIGHT_CHECK_BOGUS as it currently refuses to work through avision > after 90 tries: > BTW, the scanner works well with sp15c backend and it's marked as *good* in avision.c. So it's possible th