Hi,
I've got a bug report that xscanimage and xsane are freezing when run
as GIMP plugins ; it seems it could be caused by the use of the
deprecated scanner module, although it should still be confirmed.
So, I'm wondering : would it be a good idea to pull support for the
scanner module starting w
--V/YKEhZ4Pe4jxeTU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
This turned out to be due to a misconfiguration of the epson backend.
1.0.15 does indeed fix this problem.
Sorry for the noise,
Tim.
*/
--V/YKEhZ4Pe4jxeTU
Content-Type: application/pgp-signature
Content-Dis
Hi Rene,
it is SuSE 9.2 and here is the log:
--
sane-backends-1.0.15> SANE_DEBUG_AVISION=7 xsane
[sanei_debug] Setting debug level of avision to 7.
[avision] sane_init: parsing config line ""
[avision] sane_init:
Hi,
Martin Deppe wrote:
> well, it doesn't crash anymore - thank you so far - but it doesn't find
> the device anymore ... (none of xsane, scanimage, xscanimage or kooka)
...
> When I use the current version the following happens:
> -
Hi Rene,
well, it doesn't crash anymore - thank you so far - but it doesn't find
the device anymore ... (none of xsane, scanimage, xscanimage or kooka)
The devicename is "/dev/sg0"
and I have two directories "/dev/scanner" and "/dev/scanners"
could this be a problem?
In "/dev/scanne
