You are not logged in.
Since upgrading Gimp to 2.10, it has segfaulted on launch. I recompiled it with debugging symbols and ran it with gdb, which gave the following:
$ gdb gimp
GNU gdb (GDB) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gimp...done.
(gdb) run
Starting program: /usr/bin/gimp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
(gimp:49767): GLib-GObject-CRITICAL **: 18:29:38.600: g_param_spec_int: assertion 'default_value >= minimum && default_value <= maximum' failed
(gimp:49767): GLib-GObject-CRITICAL **: 18:29:38.601: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
(gimp:49767): Gtk-WARNING **: 18:29:39.788: Unable to locate theme engine in module_path: "adwaita",
(gimp:49767): Gtk-WARNING **: 18:29:39.795: Unable to locate theme engine in module_path: "adwaita",
[New Thread 0x7fffe8b1c700 (LWP 49788)]
[New Thread 0x7fffe831b700 (LWP 49789)]
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description
*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
Thread 1 "gimp" received signal SIGSEGV, Segmentation fault.
gimp_gegl_config_class_init (klass=0x555556213740) at gimpgeglconfig.c:137
137 gimpgeglconfig.c: No such file or directory.
(gdb) quit
A debugging session is active.
Inferior 1 [process 49767] will be killed.
Quit anyway? (y or n) yThe aforementioned file and line follow: gimp/tree/app/config/gimpgeglconfig.c. I'll paste the troublesome line to save you from following the link:
max_n_threads =
G_PARAM_SPEC_INT (g_object_class_find_property (G_OBJECT_GET_CLASS (gegl_config ()),
"threads"))->maximum;The segfault seems to be the result of not being able to find the gegl configuration for threads, which makes me think one of my configs has become corrupted. Before I file a bug report and am told it is a matter with my configuration, can anybody point me to where the gegl config should be or what files I may delete so Gimp will restore them to their defaults?
Last edited by deltaecho (2018-05-22 18:02:45)
Dylon
Offline
I don't think gegl has it's own configuration files (although you could check ~/.local/share/gegl*), but the number of threads would be configured by whatever application uses the gegl library.
You could try setting the 'num-processors' in ~/.config/GIMP/2.10/gimprc (see /etc/gimp/2.0/gimprc for reference). Looks like it defaults to $nproc, if not configured to some other value.
Offline
Thanks for the tip. I tried setting num-processors to 1 in my gimprc, but that didn't affect the outcome. The best I can tell from the release notes, Gimp will crash when you have more than 64 cores, which is the case on the workstation I'm trying to use. I've filed a bug report, here: https://bugzilla.gnome.org/show_bug.cgi?id=796289
Dylon
Offline
It was a bug in GEGL that will be resolved in its next release.
Dylon
Offline