GNOME Bugzilla – Bug 143855
twain plug-in broken
Last modified: 2018-05-24 11:08:36 UTC
When I try to scan a new image there is a problem. File>Acquire>Twain> (twain.exe:4293470075): LibGimp-CRITICAL **: file gimppixelrgn.c: lie 466 (gimp_pixel_rgn_set_rect): assertion 'x>= 0 && x + width <= pr->drawable- >width' failed After scaning a new image, when the image is appear 5% is Ok but next 95% is a black area with strange lines (bugs). Other programs work fine.
The twain plug-in is buggy then and we will need a win32 developer to fix it. Perhaps you want to look at it yourself. The warning clearly indicates what the plug-in is doing wrong. We will happily accept a patch that fixes it.
<<<Perhaps you want to look at it yourself. >>> I to stupid for fix it :-) Thanks for reply
Can you compile plug-ins, or are you using a pre-built package?
I use version for Win (pre-built??)
So you set the status to NEEDINFO. This indicates that we need info from the bug reporter and it is a perfectly good way to hide the bug report.
I don't understand this comment: "perfectly good way to hide the bug report"
NEEDINFO indicates that the developers are waiting for feedback from the bug reporter, or someone else who can reproduce the bug. No one will be working on the bug until this happens.
Ok
Can't reproduce this as I don't have a working scanner setup at the moment, and for some reason the "debug" TWAIN pseudo-source that I remember having used earlier doesn't show up any longer. Can anybody else reproduce this bug?
Works OK for me w/ 2.0.2 binary release, Windows XP, CanoScan N1240U 6.2. I'm having some trouble using it with the SaneTwain driver, though (not seeing that error message, just the image never seems to get created). The problem might be triggered by a particular buggy or "different" driver, or some other specific error condition.
I also have this bug. I described it in bug report 148679 If someone needs informaion about the bug... mail me
*** Bug 148679 has been marked as a duplicate of this bug. ***
It might be a good idea to document which scanner/driver combinations cause problems with the TWAIN plug-in. Probably somewhere in the wiki at http://wiki.gimp.org
*** Bug 162211 has been marked as a duplicate of this bug. ***
*** Bug 167349 has been marked as a duplicate of this bug. ***
*** Bug 170132 has been marked as a duplicate of this bug. ***
In bug 170132, weskaggs wrote "Unfortunately we haven't yet found the magic combination of a person with this problem who has a Windows setup that includes a debugger." What do I need to do to include a debugger in my setup? Jim
You could install MinGW and MSYS from http://www.mingw.org/. You will get an environment that is similiar to that many developers use to build GIMP. A debugger - gdb - is included. There's also a just-in-time debugger called drmingw, but this will be useless unless there is a crash. I'm not sure how much useful information can be extracted from a non-debug build like those (at least I assume) Jernej does. But it should be better than nothing.
I installed the GIMP from the Win32 binary. Do I need to build it from the sources to use the debugger, or can I install the debugger separately? I'm a total newbie in the *nix development world. Jim
I already have Cygwin. I see that I can use MinGW with Cygwin. Would it be better to use MSYS, and if so, do I need to uninstall Cygwin to use MSYS? Or is this the wrong place to ask? Jim
I found some answers to my questions in Wilbur's Wiki: HowToCompileGimpMicrosoftWindowsOld ( http://wiki.gimp.org/gimp/HowToCompileGimpMicrosoftWindowsOld ) Jim
I'm stuck again. Where should I go for help in setting up my GIMP with a debugger, so I can track down the Twain bug? I was trying to follow the instructions in HowToCompileGimp/MicrosoftWindows at http://wiki.gimp.org/gimp/HowToCompileGimp_2fMicrosoftWindows. I got to the part where it says "This is the link to the source of Gimp. You should unpack and enroll it in (for example) c:/msys/home/YOUR_NAME/." I followed the link, which downloaded gimp-2.2.1-i586-setup.zip, which doesn't look like sources to me. It unzips to gimp-2.2.1-i586-setup.exe. When I double-click on that, I get a GIMP setup wizard. I can find GIMP sources, but I'm not sure which ones I should use. Or are they all the same? Don't they have to be modified for i*86? I'm a total newbie in the *nix development world. Jim
Jim, the sources are the same for all platforms. If you want to compile from source, you want to download the latest .tar.gz file from ftp://ftp.gimp.org/pub/gimp/v2.2/. But please don't abuse this bug-tracker for questions on the process of compiling GIMP. You can use the mailing-lists for this.
*** Bug 302623 has been marked as a duplicate of this bug. ***
*** Bug 305380 has been marked as a duplicate of this bug. ***
*** Bug 309386 has been marked as a duplicate of this bug. ***
Using GIMP 2.2.6 for windows Windows XP SP2 & auto-updates CanoScan N1240U 6.2.2.0 Scans from GIMP OK at 300dpi - but not at higher resolutions... Attempts to do so result in neccesity to re-install scanner. Other program [PhotoStudio 2000] scans fine at 2100dpi. 1.1GHz CPU 248Mb RAM 744Mb pagefile 40GB HD - 70% free I will attempt to provide further inf - re: possible 'error messages' etc. in future additional comments.
Newer version - GIMP (for windows) 2.2.9 - seems to have resolved this issue. I suppose there is someone to thank for this.. So, thank you, whoever you are! :^]]
*** Bug 341949 has been marked as a duplicate of this bug. ***
*** Bug 355327 has been marked as a duplicate of this bug. ***
*** Bug 382735 has been marked as a duplicate of this bug. ***
Have a problem with twain with the Mustek 1200 CU Plus scanner. It crashes after the selection of the data source. I will make an attachement with the debug report from drmingw.
Created attachment 78986 [details] Debug Report from drmingw
I would search this bug for myself, but have no idea how to debug that twain-plugin. Can anybody give me some info about debugging?
*** Bug 488670 has been marked as a duplicate of this bug. ***
*** Bug 494125 has been marked as a duplicate of this bug. ***
*** Bug 152789 has been marked as a duplicate of this bug. ***
*** Bug 527124 has been marked as a duplicate of this bug. ***
*** Bug 606193 has been marked as a duplicate of this bug. ***
*** Bug 633585 has been marked as a duplicate of this bug. ***
*** Bug 601821 has been marked as a duplicate of this bug. ***
*** Bug 763730 has been marked as a duplicate of this bug. ***
*** Bug 764967 has been marked as a duplicate of this bug. ***
*** Bug 757393 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/84.