Hi Jörg,
Jörg Frings-Fürst writes:
> Hello,
>
> I forward this bug from Debian[1]. Please can someone check the
> included patch?
> diff --git a/backend/genesys.c b/backend/genesys.c
> index 984cead..eb8695a 100644
> --- a/backend/genesys.c
> +++ b/backend/genesys.c
> @@ -210,6 +210,8 @@
Hello,
Am Montag, den 26. Oktober schrieb M G Berberich:
> Canon datasheets say, the Canon LiDE 210 has 2.5 W max power in work,
> 1.4 W in standby and 11 mW in suspend.
>
> Is there any way to determine (via sane) if it is in standby or
> suspend? Can it be switched between standy and suspend?
On 26/10/2015 13:59, M G Berberich wrote:
Hello,
Canon datasheets say, the Canon LiDE 210 has 2.5 W max power in work,
1.4 W in standby and 11 mW in suspend.
Is there any way to determine (via sane) if it is in standby or
suspend? Can it be switched between standy and suspend?
MfG
Michael raselmsh at hotmail.com writes:
John Weber jweber53 at gmail.com writes:
I have similar problems with my Canon LIDE 220. [...] Bottom line is I get
it to work very well using USB3 by setting the environment variable
SANE_DEBUG_GENESYS_LOW=7
[...]
On 07/10/2015 03:56 AM,
Michael writes:
I was wondering if anyone can help me regarding problems using my scanner,
a CanonLiDE 210, on Ubuntu 14.10,
libsane 1.0.24-1.1ubuntu1. It worked previously with Ubuntu 14.04,
libsane 1.0.23. Now when I try
to scan (with xsane or simple-scan), it usually aborts with a grinding
Hi,
I have similar problems with my Canon LIDE 220. Please see the thread I
recently started entitled Canon LIDE 220. Bottom line is I get it to
work very well using USB3 by setting the environment variable
SANE_DEBUG_GENESYS_LOW=7
Disabling USB3 may be another way of masking a race
John Weber jweber53 at gmail.com writes:
I have similar problems with my Canon LIDE 220. [...] Bottom line is I get
it to work very well using USB3 by setting the environment variable
SANE_DEBUG_GENESYS_LOW=7
[...]
On 07/10/2015 03:56 AM, Michael wrote:
Michael writes:
I was wondering if
Michael,
- just an idea until someone with a deeper knowledge comes along -
what about compiling from git sources, and then see if you can find the
breaking commit ?
Be careful about ensuring that it IS the compiled frontend and backend that
is running.
(see the compile/install read-me file)
I can confirm this can be a problem, carefully set the paths for the
configure cmdline... While I got it basically right for lib, man etc in
the first run, I forgot the bin path... and voila, it called still the
old scanimage cmd ;)
BR
Am 22.11.2014 14:35, schrieb Troels Thomsen:
Be careful
