Created attachment 535924 [details]
backtrace of the segfault
After upgrading t darktable-2.4.3, it segfaults at start:
darktable 130 ↵
[defaults] found a 64-bit system with 12206284 kb ram and 4 cores (0 atom based)
[defaults] setting high quality defaults
[New LWP 455]
[New LWP 456]
[New LWP 457]
[New LWP 458]
[New LWP 499]
[New LWP 500]
[New LWP 501]
[New LWP 502]
[New LWP 503]
[New LWP 504]
[New LWP 505]
[New LWP 506]
[New LWP 507]
[New LWP 508]
[New LWP 509]
[New LWP 527]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f0092e46bac in __waitpid (pid=529, stat_loc=0x0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29
29 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
backtrace written to /tmp/darktable_bt_H4OMKZ.txt
 454 segmentation fault (core dumped)
I was asked whether I want to change some settings making the performance better, but it segfaults no matter which option I choose.
Created attachment 535926 [details]
backtrace with more debug symbols
I recompiled some packages with debug symbols to get more infromation, so here we are
Looks like this is a bug in the beignet openCL library. Starting darktable with `--disable-opencl` works, I even just removed beignet from my system.
I have a Intel(R) Core(TM) i7-4600U CPU with integrated graphics.