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 757393 - Scanner Dialog Closes
Scanner Dialog Closes
Status: RESOLVED DUPLICATE of bug 143855
Product: GIMP
Classification: Other
Component: User Interface
2.8.14
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-10-30 23:14 UTC by adamscr
Modified: 2016-04-17 00:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description adamscr 2015-10-30 23:14:45 UTC 
I use Gimp for Linux Mint a great deal but it doesn't work with my new Epson 860 scanner so I installed Gimp on Windows.  It is very annoying that the dialog closes once the scan is  complete so for each scan you must go to File > Create > Scanner > select your scanner > and then wait for the scanner dialog to reopen.  With Gimp for Linux the dialog remains open and you can quickly get to the next scan.
Comment 1 Michael Schumacher 2015-10-31 14:23:21 UTC 
Please note that there are different plug-ins in use on different platforms - on Linux Mint, you are most likely using the XSane plug-in, and Windows there is a plug-in that makes use of TWAIN:

There's a related report, bug 357818. While none of the patches attached there seem to address this issue, they would at least get rid of the need to select the TWAIN source every time.

There is also bug 601821 (with an attached patch as well), made to prevent accidental multi-page scans (GIMP does currently only handle single pages from TWAIN sources). 

And there is the plain "twain is broken" bug 143855. 

There's currently no one working on these bugs - if you know someone who's got the skills and time to check them out, it would be great if you can ask them to have a look.
Comment 2 Michael Natterer 2016-04-17 00:42:33 UTC 
The TWAIN plug-in is so broken, it doesn't make sense to keep
multiple bugs open for it.

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