With gimp-2.6.6-4.fc12.i586, gimp-help-browser-2.6.6-4.fc12.i586, and everything else current from rawhide as of last night, selected context help from gimp menu and clicked on dodge / burn tool, and help-browser plugin crashed. See attached bug buddy report.
(In reply to comment #0) > See attached bug buddy report. Where?
(In reply to comment #1) > (In reply to comment #0) > > See attached bug buddy report. > > Where? There is no bug buddy report attached to this bug yet, would you please do so? It may even be that you see the issue described in bug #508301, would you please check if your problem still persists with gimp-2.6.6-6?
I am unable to test whether this problem still exists or reproduce it, because gimp now hangs on startup after printing these errors: GLib-GObject-WARNING **: specified class size for type `GimpOperationPointFilter' is smaller than the parent type's `GeglOperationPointFilter' class size (gimp:2808): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gimp:2808): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed (gimp:2808): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gimp:2808): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>' pstree shows that there are three gimp processes running, a parent and two children, and that all three are hung in a futex call. I tried moving all of my ~/.gimp* directories out of the way before launching gimp, and it didn't help. I have gimp-2.6.6-6.fc12.i586, along with all other current packages from today's Rawhide. Any suggestions?
The problem with starting gimp is fixed now, see bug #510209.