GNOME Bugzilla – Bug 470304
Crash on startup after migrating gimp 2.2 prefs?
Last modified: 2008-10-30 19:57:44 UTC
From Debian bug report http://bugs.debian.org/439509. Gimp doesn't launch, but crashes with a segmentation fault instead. If I remove ~/.gimp*, gimp starts again, but not just if I remove ~/.gimp-2.3 or ~/.gimp-2.4. Error message: (script-fu:15308): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error Here is the output of GDB: Starting program: /usr/bin/gimp [Thread debugging using libthread_db enabled] [New Thread -1219848528 (LWP 15314)] [New Thread -1221854320 (LWP 15317)] [New Thread -1230247024 (LWP 15318)] Program received signal SIGSEGV, Segmentation fault.
+ Trace 157906
Thread NaN (LWP 15314)
It would be easier to debug this if we could get a copy of the ~/.gimp-2.2/ settings from the original reporter (as a compressed tarball). Looking at the stack trace, it is likely that tool_info->blurb is NULL or invalid, which would mean that some file in ~/.gimp-2.2/tool-options/ cannot be parsed correctly or contains suspicious stuff.
Unfortunately, the submitter says he deleted the original directory, so now he can't get it back.
Hmmm... That will be very difficult to analyze, then. I will keep this bug report open for a while, in case the submitter finds a backup copy or anything else that could be useful for us. There is a small chance that the bug could be found and fixed based on the information provided here, but this is unlikely given that the stack trace does not contain all debug symbols and we do not have the input files.
The submitter says he has been able to reproduce the problem on another computer. Attached is a tarball of all of his old .gimp* directories.
Created attachment 95657 [details] Tarball of old .gimp* directories
Created attachment 96069 [details] Stacktrace of crashed gimp backtrace of crash (with presumably the same problem but unpruned .gimp-2.4 dir - please see debian bug report if that matters to you)
Here is another instance of (what Ari believes to be) the same bug. This is reported as http://bugs.debian.org/443712 I have attached the backtrace here (see above). In the meantime I have found out that the problem persists even if I prune my ~/.gimp-2.4 to contain only the devicerc. I'll attach the devicerc below. I'm not sure whether this is important, but I did try uning a graphics tablet a while ago, it was not attached when I encountered this bug. Please to not hesitate to ask if I can be of assistance in tracking down this bug.
Created attachment 96070 [details] $HOME/.gimp-2.4/devicerc that causes gimp to crash
I have committed a workaround for the crash for 2.4.0-rc3. Should be investigated further: 2007-09-23 Sven Neumann <sven@gimp.org> * app/widgets/gimptooloptionseditor.c (gimp_tool_options_editor_get_title): avoid the crash reported in bug #470304.
Actually, the gimp (prior to Sven's patch) crashes if the following section is present in devicerc (GimpDeviceInfo "Core Pointer" (tool "gimp-magnify-tool") (brush "Circle (03)") (pattern "Pine") (gradient "FG to BG (RGB)") (mode screen) (axes 2 x y) (keys 0)) it does not crash anymore when I rename the device to "Core Pointerx" or somesuch.
This is the reason for the crash: 2006-02-20 Sven Neumann <sven@gimp.org> * app/tools/gimpmagnifytool.c: renamed to Zoom tool.
Well, the reason for the crash is that the code didn't deal gracefully with unknown tool identifiers in the devicerc file. This could always happen, not only because we renamed a tool. And it must not crash the application.
I think we can safely close this bug as FIXED now. I had a look at the code and it seems that other places should not be affected.