Just another reminder that Iscan works on my machine. I have a feeling you understood that it doesn't. Am I wrong?
To recap. Yes, as you said I installed the two iscan files from avasys and together with libsane everything went fine. (BTW why don't you also provide deb packages on the Avasys website? As there is no source for the plugin all we have is an RPM.) scanimage command also moves the scanner. The big mystery is why kooka and Gwenview don't work. And a bigger mystery is why they do work in SUSE 9.3 with KDE 3.5.2 and they don't work with the same KDE version on a newer kernel in both suse and Kubuntu. There is another thread on the Kubuntu forum about this issue and other people have also complained that after an upgrade to Dapper the 3170 scanner does not fire-up anymore. It appears I'm not the only one with this issue. I did a verbose debug and attaching the files for iscan and kooka Another curious thing: on SUSE 9.3 I see no libkscan...is this a clue? AJ On Sunday 18 June 2006 20:14, you wrote: > Adrian Jadic <[email protected]> writes: > > On Tuesday 13 June 2006 18:48, you wrote: > >> If you have the plugin installed, it ought to work with other SANE > >> frontends as well. But wait! You run on AMD64, right? It won't work > >> with 64bit. You will need to run all your SANE stuff in 32bit mode. > > > > AMD 3000+ 32 bit. > > That ought to be OK. > > > Other sane frontends like kooka and Gwenviw do not work. This is > > basically my big mystery. They did work in suse 9.3 but with 10.0 and > > 10.1 they don't work . only Iscan can fire up this scanner. Now I found > > the same situation in Kubuntu as well. I had so much trouble with this > > scanner that I was really thinking to sell it on ebay and get a Canon > > Lide or smthg since I don't use the film feature anyway nor have I used > > the high resolution enough to justify this unit. > > > > But let me first thank you for trying to help me with this., I have been > > crying about this issue in all possible forums, reported bugs and so on. > > I even returned a purchased suse 10.0 on this issue (among others) and > > nobody gave it any attention. > > > >> > So now kooka displays that small window with "choosing device" and the > >> > Epson 3170 is listed correctly. > >> > But when I press "preview" or "scan" nothing happens. > >> > >> Hmm, that's weird. If listed in the window to choose a device, the > >> backend did see the device allright. Could you take a look at the > >> debugging output? > >> > >> $ SANE_DEBUG_EPKOWA=50 iscan 2> debug.log > > > > I am attaching the output as requested. I also did one with kooka and I > > see that it is different so I am attaching it as well > > > > [epkowa] sane_get_devices() > > [epkowa] sane_open(libusb:005:004) > > [epkowa] init_options() > > [epkowa] open_scanner() > > [epkowa] setvalue(option = 43, value = 0xbfb7da90) > > [epkowa] close_scanner(fd = 0) > > Hmmm, option 43 is the document source. Setting that option does not > cause any communication to the device, AFAIK. There are two calls in > the sources that could trigger an error at this point: > > - sanei_constrain_value > - search_string_list > > and there is no way to extract more debugging info without modifying > the source code. Looking at the source code of both functions, the > only reason I can think of that would trigger a failure to set the > document source here, is that your frontend tries to set an invalid or > non-existent document source. The list of available sources should be > correct based on the log (so there is no chance of duplicate matches > that would cause sanei_constrain_value to return a no good status). > > To summarise, I have no clue :-(. Perhaps that running iscan with a > more verbose debug setting sheds some light on this, but I doubt it. > > $ SANE_DEBUG_EPKOWA=127 iscan &> perfection-3170.log > > Are you 100% positive that you are running a 100% 32bit setup when > trying to use the scanner? > > I don't understand what the kooka error messages are about. Maybe > something in libkscan itself? > > > But, shouldn't this unit work just by installing libsane and > > libsane-extras? I see that libsane-extras has epkowa. Bottom line which > > file does actually contain the driver? > > The epkowa backend from libsane-extras is not expected to work with > this device. It requires a non-free module which is not included in > that package (for obvious reasons). You can safely uninstall it if > you don't use the other SANE backends it includes. > > Your EPSON Perfection 3170 should work (out-of-the-box) by installing > libsane and a recent version of iscan (>= 1.18.0) with the plugin that > your device requires (iscan-plugin-gt-9400). > > # I'm not sure what'll happen if you also have libsane-extras > # installed, so suggest you uninstall it. > > > Thank you > > > >> The output will end up in the debug.log file. > >> > >> > Thank you, > >> > A Jadic > >> > > >> > On Tuesday 13 June 2006 00:54, you wrote: > >> >> Adrian Jadic <[email protected]> writes: > >> >> > I have trouble using the Epson Perfection 3170 Photo in Kubuntu > >> >> > 6.06 > >> >> > > >> >> > Kooka and scanimage recognise the scanner. However when I try to > >> >> > scan I am getting the following errors: > >> >> > ================= > >> >> > ~$ scanimage -L > >> >> > device `epson:libusb:001:004' is a Epson flatbed scanner > >> >> > >> >> This scanner is NOT supported by the epson backend. It is also not > >> >> supported by the plustek or snapscan backends. If you want to use > >> >> this scanner, you will have to use the epkowa backend together with a > >> >> non-free binary-only plugin. Some distributions now include this > >> >> backend but the plugin is probably only available via: > >> >> > >> >> http://www.avasys.jp/english/linux_e/index.html > >> >> > >> >> > ~$ scanimage > >> >> > scanimage: sane_start: Invalid argument > >> >> > ~$ kooka > >> >> > libkscan: WARNING: Trying to copy a not healthy option (no name nor > >> >> > desc) libkscan: WARNING: Trying to copy a not healthy option (no > >> >> > name nor desc) ScimInputContextPlugin() > >> >> > ~ScimInputContextPlugin() > >> >> > ~$ > >> >> > ================= > >> >> > This happens in both root and user. > >> >> > Can anyone help me get further here? This scanner works fine in > >> >> > SUSE 9.3 > >> >> > > >> >> > metricus > >> >> > AMD 3000+, 1GB RAM, Kubuntu 6.06 > >> >> > >> >> The plugin is only available for i386 ... > >> >> > >> >> Hope this helps, > > As always, hope this helps, -------------- next part -------------- A non-text attachment was scrubbed... Name: perfection-3170-iscan.log Type: text/x-log Size: 6206 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060619/14cc08c4/perfection-3170-iscan.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: perfection-3170-kooka.log Type: text/x-log Size: 4910 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060619/14cc08c4/perfection-3170-kooka.bin From [email protected] Mon Jun 19 23:48:20 2006 From: [email protected] (Olaf Meeuwissen) Date: Tue Jun 20 00:17:23 2006 Subject: [sane-devel] FYI: iscan-2.1.0 released Message-ID: <[email protected]> Hi everyone, Already hinted at in several previous messages, iscan-2.1.0 has been released to the public. Packages are available via: http://www.avasys.jp/english/linux_e/index.html http://www.avasys.jp/linux/index.html (in Japanese) This version adds udev support (trying to follow your distribution's approach to handling sane-backends udev support) and support for the following devices: - GT-X900 - PM-A890 - PM-A950 - Perfection V700 - Perfection V750 - Stylus CX4100 - Stylus CX4200 - Stylus CX4700 - Stylus CX4800 - Stylus DX4200 - Stylus DX4800 - Stylus Photo RX640 - Stylus Photo RX650 None of the above devices requires an additional plugin. The udev support, following the hotplug support added in 1.14.0, tries to make sure that normal users can access the device out-of-the-box. Messing with permissions on device files in /dev, /proc or /sys should be a thing of the past. There may be problems on SELinux enabled systems, but dropping your policy to Permissive should work around these. As you may (or may not) have noticed, the iscan packages no longer include the non-free binary-only i386 plugins that are required with some of the supported devices. The download pages will list plugins if the device you selected needs one. For the record, here is a list of devices with the plugin they need: GT-7200U iscan-plugin-gt-7200 GT-7300U iscan-plugin-gt-7300 GT-9400UF iscan-plugin-gt-9400 GT-F500 iscan-plugin-gt-f500 GT-F520 iscan-plugin-gt-f520 GT-F550 iscan-plugin-gt-f500 GT-F570 iscan-plugin-gt-f520 GT-F600 iscan-plugin-gt-f600 GT-X750 iscan-plugin-gt-x750 Perfection 1250 iscan-plugin-gt-7200 Perfection 1250 PHOTO iscan-plugin-gt-7200 Perfection 1260 iscan-plugin-gt-7300 Perfection 1260 PHOTO iscan-plugin-gt-7300 Perfection 2480 PHOTO iscan-plugin-gt-f500 Perfection 2580 PHOTO iscan-plugin-gt-f500 Perfection 3170 PHOTO iscan-plugin-gt-9400 Perfection 3490 PHOTO iscan-plugin-gt-f520 Perfection 3590 PHOTO iscan-plugin-gt-f520 Perfection 4180 PHOTO iscan-plugin-gt-f600 Perfection 4490 PHOTO iscan-plugin-gt-x750 For those of you who build from "source", please note that builds on non-i386 platforms will no longer try to build the iscan frontend as that requires (yet another) non-free binary-only i386 library. On such platforms only the epkowa backend will be built. The configure script has an option to explicitly control this behaviour. Pass the --disable-frontend option to skip building the frontend. Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
