GNOME Bugzilla – Bug 794818
2.10RC1 does not start (ArchLinux)
Last modified: 2018-04-18 11:19:04 UTC
GIMP crashed with a fatal error: fatal error: Segmentation fault
Gimp can't get to start up at all on fully updated Arch
GNU Image Manipulation Program version 2.10.0-RC1
Using built-in specs.
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --enable-default-pie --enable-default-ssp
Thread model: posix
gcc version 7.3.1 20180312 (GCC)
using GEGL version 0.3.31 (compiled against version 0.3.31)
using GLib version 2.56.0 (compiled against version 2.56.0)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.41.1 (compiled against version 1.41.1)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.15.11 (compiled against version 1.15.11)
> fatal error: Segmentation fault
[New LWP 2504]
[New LWP 2505]
[New LWP 2508]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f650eedb988 in read () from /usr/lib/libpthread.so.0
Thanks for the report. This very much look like a duplicate of bug 794752 (though your traces have less details, so I cannot be 100% sure).
How did you install GIMP? Did you build it yourself? If so, you probably installed mypaint-brushes v2 (master branch), not the version 1, which should not happen. Did you tweak our configure script (or mypaint-brushes pkg-config file) to force the brushes v2 being accepted as v1?
Or if you installed from an Arch package, could you please open a bug report and ask them if they did what I am telling above (installed mypaint-brushes v2, i.e. the master branch, and not the v1.3.0 branch as requested in our INSTALL file)?
If you open a bug report, please post the link here, if possible!
Jehan, your comments led me to a resolution. Installing from AUR did not pull in libmypaint 1.3.0 but only mypaint-brushes. I went back and installed libmypaint from AUR and Gimp now starts normally. This seems to be more an Arch packaging issue rather than a Gimp bug.
Thanks a lot for your speedy response, much appreciated!
(In reply to newmikey from comment #2)
> Jehan, your comments led me to a resolution. Installing from AUR did not
> pull in libmypaint 1.3.0 but only mypaint-brushes. I went back and installed
> libmypaint from AUR and Gimp now starts normally. This seems to be more an
> Arch packaging issue rather than a Gimp bug.
Can I suggest to open a bug report to Arch then so that they can fix the packaging bug? :-)
> Thanks a lot for your speedy response, much appreciated!
No prob. Thanks for the report! :-)
*** Bug 795353 has been marked as a duplicate of this bug. ***
*** Bug 794865 has been marked as a duplicate of this bug. ***