GNOME Bugzilla – Bug 788962
Scanner does not work in this version
Last modified: 2018-05-08 21:46:28 UTC
Hello. Scanner does not work in this version!
Sure this is 2.9.2?
It it is 2.9.6, it could be for the simple issue that the twain plug-in doesn't handle 64 bit twain drivers yet.
Hi Vagner, what's the exact error message?
Not sure my issue is exactly the same ... on 2.9.8 (Windows 10) driver(s) are not listed on File-Create-Scanner/Camera. Nothing shows. Under 2.8.22 three sources/drivers show up.
(In reply to twern from comment #4) > Not sure my issue is exactly the same ... on 2.9.8 (Windows 10) driver(s) > are not listed on File-Create-Scanner/Camera. Nothing shows. > > Under 2.8.22 three sources/drivers show up. @twern Bonjour, This is normal with this version of Gimp 2.9.8 Win totally 64 bits because 'twain' is a 32-bit application.
I understand now. Thanks. (In reply to sylvie.alexandre from comment #5) > (In reply to twern from comment #4) > > Not sure my issue is exactly the same ... on 2.9.8 (Windows 10) driver(s) > > are not listed on File-Create-Scanner/Camera. Nothing shows. > > > > Under 2.8.22 three sources/drivers show up. > > @twern > Bonjour, > This is normal with this version of Gimp 2.9.8 Win totally 64 bits because > 'twain' is a 32-bit application.
Bonjour, Additional Information : The plugin 'twain' works great with Gimp 2.9.9 64 bit Win. For that it must be compiled in 32 bits and can be placed in a \lib\gimp\2.0\plug-ins\twain\ sub-directory with all these dependencies (twain.exe, libbabl-0.1-0.dll, libgegl-0.3-0.dll, libgimp-xxx, etc. ). In this case, the 64-bit 'twain' plugin must be removed. :o)
Thanks for the tip Sylvie! So basically you are saying that even when distributing a 64-bit GIMP, the twain plug-in myst always be compiled as 32-bit? And also we must build each of its dependencies a second time as 32-bit just for this plug-in? That really sucks. :-/ Also why was it working on 2.8? (from what I understood from the above discussion)
Bonjour, (In reply to Jehan from comment #8) > Thanks for the tip Sylvie! > > So basically you are saying that even when distributing a 64-bit GIMP, the > twain plug-in myst always be compiled as 32-bit? > And also we must build each of its dependencies a second time as 32-bit just > for this plug-in? Yes. > > That really sucks. :-/ No, no... 32-bit compilation is a real pleasure... > > Also why was it working on 2.8? (from what I understood from the above > discussion) There are several ways to make this 'twain' plugin work under 64-bit windows : - The official 64-bit Gimp 2.8.x Win distribution uses a \32 directory where you can find all the dependencies needed to run 32-bit plugins. - In the archive that I propose to test I allow users to use both versions to test. It's a personal choice to make as outlined in Comment #7. In conclusion: - It is mandatory to compile in 32 bits to propose the 'twain' plugin. That's what is done with the official distributions of the stable versions and that's fine. - The plugin 'twain' is necessary in Gimp. It should be included systematically. Official distributions of stable versions can mix 32-bit plugins and 64-bit plugins... it's great... :o)
Ok I guess we just have to not forget doing this when doing a 2.10 release. :-/ Setting to 2.10 milestone with "Windows installer" component.
Current Windows installer installs 32-bit TWAIN plugin by default, and at least for me scanning works fine. Can this be marked as resolved?
From various reports about this it is safe to assume that the issue is fixed - i.e. at the same level of support than 2.8 - with the current installers.
*** Bug 795670 has been marked as a duplicate of this bug. ***
*** Bug 795738 has been marked as a duplicate of this bug. ***