GNOME Bugzilla – Bug 161787
script-fu crashes in Windows' GIMP 2.2.0
Last modified: 2008-01-15 12:43:20 UTC
When the locale is some double-bytes charset (zh_CN, zh_TW, ja, ko, etc.), the script-fu engine will crash. (Oh, I haven't tried it in Linux, no time to compile yet.) Steps to testify: # Bring up the command line window and execute: cd \Program files\GIMP-2.2\bin set LANG=zh_CN (or LANG=ja or ....) gimp-2.2 # Windows should report errors when 1) GIMP has just started 2) Selecting menu "extn -> Script-fu -> ...."
You don't have traces of an old GIMP 2.0 installation, do you? 'LC_ALL=zh_CN.UTF-8 gimp-2.2' works w/o any problems here and also allows me to run Script-Fu scripts.
I can confirm this with 2.2.0 on WinXP - and since I relied on the installers to clean up or do the right thing (like the average user would, too) on this system, there might be traces left over. I'll try to check where exactly it crashes this evening.
I have tried to compile GIMP 2.2 on Linux. This bug didn't occur on Linux. Since the bug only occurs under multi-bytes locales, I tried to msgunfmt the zh_CN/gimp*.mo, remove some of the msgid/msgstr translations, and then re- msgfmt them. Finally, I found the problem is relatived with the translations of units in gimpunits.c: msgid "pica" msgstr "XX" # here X represents a Chinese character msgid "pixel" msgstr "XX" msgid "point" msgstr "X" ...... Here I found that if the translation of any unit's singular form contained only ONE Chinese character ("point"'s translation happens to be), the error would pop-up. If I changed the translation to some two characters Chinese word, the error would not pop-up. I tried to read the source code, but failed to understand it. So I could not tell how to solve the problem.
I also have the same problem. On Windows XP Pro SP2 Sinplified Chinese GTK+ 2 for Windows (version 2.4.14) The Gimp for Windows (version 2.2.0) If the script-fu.exe was replaced by the old version in GIMP 2.0 No error reported during startup. But when I refresh scripts, three error listed. I can't understand at all. I am very new to GIMP.
I also have the same problem. On Windows XP Version 5.1.2600 Service Pack 1 Nu 2600 French GTK+ 2 for Windows (version 2.4.14) The Gimp for Windows (version 2.2.0) It's a new installation on a new HDD. Script-Fu/Render/Lava... ran OK one time but not anymore even after reboot. The error reported is : AppName: script-fu.exe AppVer: 0.0.0.0 ModName: libgimpui-2.0-0.dll ModVer: 0.0.0.0 Offset: 00004e5d A txt file containing a lot of lines accompagned the reported error ; the last lines were : </EXE> <EXE NAME="libgimpui-2.0-0.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> <MATCHING_FILE NAME="libgimpui-2.0-0.dll" SIZE="113405" CHECKSUM="0x47817A6" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2A5EA" LINKER_VERSION="0x10000" LINK_DATE="12/19/2004 16:35:26" UPTO_LINK_DATE="12/19/2004 16:35:26" /> </EXE> <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> <MATCHING_FILE NAME="kernel32.dll" SIZE="995840" CHECKSUM="0x83280F5B" BIN_FILE_VERSION="5.1.2600.1560" BIN_PRODUCT_VERSION="5.1.2600.1560" PRODUCT_VERSION="5.1.2600.1560" FILE_DESCRIPTION="DLL du client API BASE Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Système d'exploitation Microsoft® Windows®" FILE_VERSION="5.1.2600.1560 (xpsp2_gdr.040517-1325)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Tous droits réservés." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF6104" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.1560" UPTO_BIN_PRODUCT_VERSION="5.1.2600.1560" LINK_DATE="06/17/2004 17:56:29" UPTO_LINK_DATE="06/17/2004 17:56:29" VER_LANGUAGE="Français (France) [0x40c]" /> </EXE> </DATABASE> : I can't understand what happened. I am new with GIMP and not a programmer ! I will try a new installation ...
Does this still happen with GIMP 2.2.3?
I think the first sentence of this bug report says it all. This is the same problem reported in bug #163212 and is a duplicate of bug #153747 (Script-Fu needs UTF-8 support).
Yes, the bug is still there.
*** This bug has been marked as a duplicate of 163212 ***