GNOME Bugzilla – Bug 683147
Gimp crashes on launch when OS language is Japanese
Last modified: 2013-09-22 04:43:25 UTC
Created attachment 223122 [details] crash report Gimp crashes on launch on my machine (OS X 10.7.4) every time when my system's default language is set to Japanese. 1. Having booted with system language set to Japanese, launch Gimp. It crashes (see attached system log and crash report). 2. Open System Preferences > Language & Text. Drag English to the top of the preferred language list. 3. Launch Gimp. It loads successfully. Reverting the system language to Japanese will cause Gimp to crash on launch again.
Created attachment 223123 [details] system log
Hm, interesting. Is Japanese your default language? If so, could you please add "export LANG=ja" to the gimp launcher script inside of GIMP.app/Contents/MacOS, and see if that fixes the crashing. At the very least, if the system language it set to English, gimp should load in japanese, and it should not crash.
Japanese is my default language. The environment variable $LANG is set to "ja_JP.UTF-8" by default on my system. The startup process made it partway through (until the progress bar fills for the first time) before the crash, and the status messages showed up correctly in Japanese. I tried adding "export LANG=ja" to the Gimp launch script, and to my surprise it launched correctly. However I subsequently deleted that line from the script and it still launched correctly, so I don't think it made a difference (whatever caused the crash may have been fixed by the successful launch I managed to get when I temporarily set my system to English). I suspect there is some one-time-only setup relating to fonts that must be performed on the first launch. I would be happy to delete my existing settings and try again from a fresh setup, but I'm not sure where the Gimp settings are now kept (I have a ~/.gimp-2.6 but nothing newer).
If you're interested in further testing, the gimp files are now placed in ~/Library/GIMP/. It may be another path issue, or it could be because of the difference between ja_JP.UTF-8 and ja.
I tried removing ~/Library/GIMP, restarting with my usual system language settings (Japanese) and updating to Gimp 2.8.2-2, and the crash is still happening. Adding "export LANG=ja" to the launcher script doesn't help. It looks like my inability to reproduce the crash in my previous comment was due to my forgetting to set my system back to Japanese (you can temporarily change the default language for newly launched apps in System Preferences; it only takes effect for the entire system (and the LANG envar) upon logout-login or restart). At this point the situation is: 1. When the system language is Japanese, Gimp crashes on launch every time. Setting LANG=ja in the launch script has no effect. 2. When the system language is (temporarily) set to English, Gimp launches correctly. LANG is still ja_JP.UTF-8, so the UI is in Japanese (and displays correctly).
It looks like the darktable project has a massive addition to their build script that fixes the localization issue. I'll see how well it can be applied to GIMP. If you'd like to check it out yourself, download the experimental package they have released, and copy and paste the related parts of the scripts.
If the environment for apps is set up like that, then why not try saying LC_ALL=$LANG and start gimp? Aaron, can you try this?
*** Bug 689828 has been marked as a duplicate of this bug. ***
It's also on OS X 10.8.2 (Mountain Lion).
This issue seems to have resolved itself for me in version 2.8.4 (OS X 10.7.4).
Can anyone else confirm the issue being not a problem anymore? Sasamao who reported the same issue in Bug 689828 maybe? Aaron, still working all fine in Japanese with GIMP 2.8.6?
@Jehan Everything's fine with 2.8.6 for me. OS X 10.7.5.
Hi Aaron, I was hoping the other reporter from bug 689828 to confirm it was good for him too (or anyone else who may have experienced the same issue). But in the absence of other feedback, let's close the issue as RESOLVED > OBSOLETE. It's just too bad we did not get to the core reason of the issue. I would have preferred to have understood. If anyone experiences this bug again, do not hesitate to re-open this report.