Version-Release number of selected component: darktable-1.4.2-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/darktable crash_function: _dt_sigsegv_handler executable: /usr/bin/darktable kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 _dt_sigsegv_handler at /usr/src/debug/darktable-1.4.2/src/common/darktable.c:188 #3 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:161 #4 memcpy at /usr/include/bits/string3.h:51 #5 process at /usr/src/debug/darktable-1.4.2/src/iop/sharpen.c:394 #6 dt_dev_pixelpipe_process_rec at /usr/src/debug/darktable-1.4.2/src/develop/pixelpipe_hb.c:1435 #23 dt_dev_pixelpipe_process_rec_and_backcopy at /usr/src/debug/darktable-1.4.2/src/develop/pixelpipe_hb.c:2060 #24 dt_dev_pixelpipe_process at /usr/src/debug/darktable-1.4.2/src/develop/pixelpipe_hb.c:2144 #25 dt_imageio_export_with_flags at /usr/src/debug/darktable-1.4.2/src/common/imageio.c:812 #26 _init_8 at /usr/src/debug/darktable-1.4.2/src/common/mipmap_cache.c:1323 #27 dt_mipmap_cache_read_get at /usr/src/debug/darktable-1.4.2/src/common/mipmap_cache.c:984
Created attachment 893708 [details] File: backtrace
Created attachment 893709 [details] File: cgroup
Created attachment 893710 [details] File: core_backtrace
Created attachment 893711 [details] File: dso_list
Created attachment 893712 [details] File: environ
Created attachment 893713 [details] File: exploitable
Created attachment 893714 [details] File: limits
Created attachment 893715 [details] File: maps
Created attachment 893716 [details] File: open_fds
Created attachment 893717 [details] File: proc_pid_status
Created attachment 893718 [details] File: var_log_messages
At the moment I can reproduce the crash by simply importing the folder I was working on.
Upstream bugreport http://www.darktable.org/redmine/issues/9949
*** Bug 1103497 has been marked as a duplicate of this bug. ***
In IRC, user LebedevRI said: "it is fixed in master". Can't we make a new package release to fix that bug?
Bugs are always fixed in master. Could you point me what commit fix your bug in master branch? So I can try to cherry pick the patch. I guess next darktable release will include this patch so, just have to wait.
(In reply to Edouard Bourguignon from comment #16) > Bugs are always fixed in master. Could you point me what commit fix your bug > in master branch? So I can try to cherry pick the patch. I guess next > darktable release will include this patch so, just have to wait. It should be https://github.com/darktable-org/darktable/commit/fcc874e98a6f00a0ae813b041bcfb71d4c039514
Hi, are there any news?
(In reply to Germano Massullo from comment #18) > Hi, are there any news?