After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 763730 - Gimp is not recognising Canon Lide 110 scanner with Twain driver downloaded.
Gimp is not recognising Canon Lide 110 scanner with Twain driver downloaded.
Status: RESOLVED DUPLICATE of bug 143855
Product: GIMP
Classification: Other
Component: General
2.8.16
Other Mac OS
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-03-15 23:57 UTC by John Pearson
Modified: 2016-03-16 19:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Pearson 2016-03-15 23:57:03 UTC 
I have used Gimp with Windows 7 machine and with Lide 110 scanner for some years. Have switched to Mac Mini and have added Lide 110 scnner and downloaded the latest Twain (and general) driver for the mac running on OSX 10.11.3. Have talked through the prob;em with Canon and they feel it is a problem with Gimp. The Mac recognises the scanner and Canon MP Navigator runs the scanner amd I can download the saved file into Gimp. Gimp, however, does not recognise the scanner and File -> Create does not show scanner as it used to do on the old Windows machine. This means I cannot use the excellent Gimp dialogue to preview, select and resize the parts pf the document to bring into Gimp. Scanning in the Canon software is slow and time consuming and every part has to be done separately. I downloaded Gimp 2.8.16.

This issue may be related to 311965 or 426846 in the possible duplicates, but I have not seen any messages or menu choices relating to Twain or Aquire.
Comment 1 tobias 2016-03-16 08:51:14 UTC 
I think this is a duplicate of bug #143855
Comment 2 Michael Natterer 2016-03-16 19:57:34 UTC 
Yes, our twain stuff is probably broken beyond repair and should
be redone from scratch.

*** This bug has been marked as a duplicate of bug 143855 ***