GNOME Bugzilla – Bug 623563
Text tool crashes Gimp (get_impl_drawable)
Last modified: 2012-01-08 02:17:41 UTC
Running on Windows Vista x64, Gimp 2.7.1 crashes whenever I try to use the text tool. This is a different crash than Bug #575866 ("Assertion fail (font finalize) pango win32") which crashes version 2.7.0 with the exact same reproduction recipe, but gives a different error message. Step to reproduce: 1) Select the text tool. 2) Click on the canvas. Actual results: Gimp crashes with a standard Windows error popup ("The application has requested the Runtime to terminate in an unusual way. Blah blah blah.") and the following error is printed in the console: Gdk:ERROR:gdkgc-win32.c:751:get_impl_drawable: code should not be reached Note: Unlike bug #575866, which didn't crash immediately if you selected certain fonts (e.g. Courier, which didn't crash until you tried to type a character) it looks like this bug always crashes as soon as you left-click on the canvas, no matter which font you have selected.
*** Bug 623479 has been marked as a duplicate of this bug. ***
Created attachment 165317 [details] GIMP initial error screen This is the first error message when I click on the canvas with the text tool (any font, any file).
Created attachment 165318 [details] Detail report from Microsoft when GIMP crashes After the initial error screen this is the detail report for the crash. I couldn't expand the box so I tried to get the info I thought was important...
I'm having the same issue. See attachments above to see what happens on my computer and to view the detail report from the crash (as best I could). The file it says is having issues: Application Version: 2.7.1.0 Application Timestamp: 4c29b579 Fault Module Name: libglib-2.0-0.dll Fault Module Version: 2.24.1.0 Fault Module Timestamp: 4c07b57b Exception Code: 40000015 Exception Offset: 000000000004c72a I'm on Win7 Home Premium, 64-bit.
*** Bug 623791 has been marked as a duplicate of this bug. ***
I can't reproduce this with my own git master build on XP SP3.
If it makes any difference, I was using the gimp-win build at http://sourceforge.net/projects/gimp-win/files/GIMP%20%2B%20GTK%2B%20%28development%20rel.%29/GIMP%202.7.1/.
I believe I found a possible reason for this bug - the transparent canvas overlay widgets. To check my intuition I tried some other tools which use the canvas overlays (Curves tool in full-screen mode) and I got exactly the same error message... (Using the 2.7.1 build from gimp-win at sourceforge) I'll try to build the master on windows and check again.
Looks like this is caused by the ms-windows theme of GTK+. It does not happen if you don't use this theme engine - the price is an ugly UI, of course.
(In reply to comment #6) > I can't reproduce this with my own git master build on XP SP3. It seems to be a Vista/Win7 issue, as that's what I run, as does Rick Yorgason.
(In reply to comment #9) > Looks like this is caused by the ms-windows theme of GTK+. It does not happen > if you don't use this theme engine - the price is an ugly UI, of course. So for those of us who run windows... and aren't familiar with compiling this ourselves (yes, it's sad, but true), is there a way to get it to work? Right now I'm using gimp 2.6.8 (or the one before 2.6.9 because that one crashes with the font tool for other reasons). I can keep using it until the issue is fixed, but I was just wondering.
*** Bug 624099 has been marked as a duplicate of this bug. ***
Michael, if it's a bug in the GTK+ theme engine, could you add relevant info to this bug report so we can move it to GTK+?
I guess that's just the GTK+ version, everything else should already be mentioned here. Reassigning to gtk+.
(In reply to comment #11) > So for those of us who run windows... and aren't familiar with compiling this > ourselves (yes, it's sad, but true), is there a way to get it to work? In the etc directory in your Gimp installation, edit the gtkrc file and replace 'MS-Windows' with 'Tango'. Seems to fix the crash for me.
He means the gtkrc file in the etc\gtk-2.0 folder. Note that it is a plain text file, don't attempt to edit it with Word or something like that, and that its name indeed does not have any extension ("type"), its name is just "gtkrc". Anyway, replacing "MS-Windows" with "Tango" is pointless as Tango isn't a theme, but an icon theme. That is a different thing. It is wrong and ineffective to put an icon theme name as the gtk-theme-name setting. (And, as far as I know the GIMP installer doesn't even come with the Tango icon theme.) Just commenting out the gtk-theme-name line, or using whatever random bogus theme name instead of MS-Windows, would have the same effect: The default gtk theme gets used.
Rick, are you running the 32- or 64-bit GIMP? What version of GTK+ is 2.7.1 shipped with?
I'm running the 64-bit version. I'm not certain which version of GTK+ is shipped with 2.7.1, but my best guess is 2.10.0. This guess is based on the fact that there's a folder named 'lib\gtk-2.0\2.10.0'. Is there a better way to find the version?
Oh, just to be clear, 2.7.1 appears to be shipped with a 64-bit and 32-bit version, so it should automatically install the 64-bit version if you're running a 64-bit version of Windows. I just double-checked with the dumpbin tool, and it did indeed install the 64-bit version on my machine.
No, the name of the lib\gtk-2.0\2.10.0 folder does not indicate the version of GTK+. Check the Properties of libgtk-win32-2.0-0.dll, it should tell what version it is. Or run gimp with the -v command-line option.
Thanks; it's 2.20.1.
*** Bug 624992 has been marked as a duplicate of this bug. ***
*** Bug 625158 has been marked as a duplicate of this bug. ***
*** Bug 625352 has been marked as a duplicate of this bug. ***
*** Bug 625733 has been marked as a duplicate of this bug. ***
What more information is needed other than the libgtk-win32-2.0-0.dll version number? It's 2.20.1 on my installation as well. I'm also having this problem on Windows 7 x64.
I am on windows XP SP3 32-bit. same error as was stated originally.
I'm setting up cygwin with MinGW in an attempt to recompile GIMP 2.7.1 from source and see if I still have problems...I've never compiled from source in Windows, and it's a huge pain. I can't find any documentation on how to compile GIMP in windows, so any tips would be nice. I've been working off of a guide to compiling Pidgin in windows.
You need to work on your googling skills then. I found several tutorials on building GIMP with MinGW. Of course, none of them is proably really up-to-date, very little on the web is. But then, part of the skills necessary in programming is to be able to adapt to changes. Anyway, if you have never built anything at all with MinGW before, or you have never built anything that uses a configure script and makefiles, then you need to start your training with something simpler than GIMP. Also, do avoid mixing Cygwin and MinGW. Cygwin is not required to build GIMP on Windows, and in fact, especially if you are new to building software like GIMP on Windows, mixing Cygwin and MinGW will just lead to strange errors and confusion. (Just one example of potential confusion: note that the GTK+ stack for Cygwin that is officialy available for Cygwin uses an *X11* backend, i.e. it requires an X11 server to run GUI programs, i.e. not at all the same as with GIMP for Windows.) Cygwin should be seen as a completely separate operating system that just happens to run on top of Windows. Code built for Cygwin and code built for Windows (with MinGW, or Microsoft's compiler, or other Windows compilers) are different kinds of beasts. Anyway, as the actual error messages here comes from the GTK+ library, not GIMP, you would need to build the whole GTK+ stack for debugging, not just GIMP.
I see, well I set up a Lubuntu virtual machine and installed MinGW to cross compile on that system. I was able to compile babl, gegl, and gimp, but I don't really understand what I need to do to cross compile for windows. Any tips on that would be helpful. But then again, you did say error messages from the GTK+ library are needed, so I guess it's more work then just that.
why are you doing this, if you try to build the gimp yourself would more errors occur from that? Also i found a file that comes with the gimp 2.7.1 source telling how to build the gimp. i wish i knew the name of it, but i have forgotten. it has no file extension, so that might help you find it.
*** Bug 626157 has been marked as a duplicate of this bug. ***
*** Bug 629892 has been marked as a duplicate of this bug. ***
*** Bug 629276 has been marked as a duplicate of this bug. ***
*** Bug 636785 has been marked as a duplicate of this bug. ***
*** Bug 639676 has been marked as a duplicate of this bug. ***
Reopening as the information requested in comment 17 has been provided.
*** Bug 644022 has been marked as a duplicate of this bug. ***
*** Bug 653100 has been marked as a duplicate of this bug. ***
I cannot reproduce this bug on the partha.com unnofficial Win32 build of 2.7.3 (2011-08-06), despite using the MS-Windows theme. This bug may be OBSOLETE. If anyone wants to confirm, note that the appropriate file to change is in etc\gimp\2.0, as there is no gtk folder.
Update on the above: however, adding the option does not seem to actually modify the theme, so I may have spoke too soon.
*** Bug 659903 has been marked as a duplicate of this bug. ***
Hello, I have the same problem on Gimp 2.7.3 on Windows 7 x64 Enterprise. Problem signature: Problem Event Name: APPCRASH Application Name: gimp-2.7.exe Application Version: 2.7.3.0 Application Timestamp: 4e5bf19f Fault Module Name: libglib-2.0-0.dll Fault Module Version: 2.28.8.0 Fault Module Timestamp: 4e20a38e Exception Code: 40000015 Exception Offset: 000000000005113d OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1033 Additional Information 1: ddc0 Additional Information 2: ddc026eda8dbd72e642fcebf560e68bc Additional Information 3: 71d5 Additional Information 4: 71d5603b5ffc96217f4e3353a529b83c Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
This bug still affects Partha's build of GIMP 2.7.4 (using libwimp.dll from GTK+ 2.24.8). D:\Applications\GIMP\bin>gimp-console-2.7.exe -v GNU Image Manipulation Program version 2.7.4 git-describe: Unknown, shouldn't happen using GEGL version 0.1.9 (compiled against version 0.1.9) using GLib version 2.30.2 (compiled against version 2.30.2) using GdkPixbuf version 2.24.0 (compiled against version 2.24.0) using Pango version 1.29.4 (compiled against version 1.29.4) using Fontconfig version 2.8.0 (compiled against version 2.8.0) using Cairo version 1.10.2 (compiled against version 1.10.2)
What GTK+ version is this? You don't just copy libwimp.dll around, do you?
this is from: https://sourceforge.net/projects/gimp-win/files/GIMP%20%2B%20GTK%2B%20%28development%20rel.%29/GIMP%202.7.1/ I am going to try to contact the developer about this. I usually get no responses from this person. he's the guy who develops the windows version of GIMP listed on gimp.org.
https://sourceforge.net/users/jernejs/ is the developer of the windows version of GIMP.
I can confirm that this bug still affects GTK+ 2.24.8 (from the OpenSuSE repository - specific version mingw32-gtk2-2.24.8-1.5.noarch.rpm). Tested both 32 and 64-bit versions, on Windows XP (32-bit, Zune theme) and Windows 7 (32 and 64-bit, with classic and Aero themes) when gtkwimp engine is in use. Gdk:ERROR:gdkgc-win32.c:753:get_impl_drawable: code should not be reached Also, I'm not a developer of GIMP on Windows - I only provide the installer. I do respond to pretty much every e-mail I receive, however if you send me a message through SourceForge, they nearly always reject the reply with "User does not exist" - this is not something I can fix.
Fixed in gtk-2-24 by: http://git.gnome.org/browse/gtk+/commit/?id=f8170ee87388653cfef605636520b7b6fba955cf and http://git.gnome.org/browse/gtk+/commit/?id=e9b0f9e81aab098462cfc0117c449e7597858438
Created attachment 203729 [details] Partially drawn toolbar in GIMP I can confirm that GIMP doesn't crash anymore, but the floating toolbar that appears doesn't always draw properly - see attached image.
Please open a new bug for the new problem.