Bug 2297697

Summary: Darktable crashes in 15s, even if doing nothing
Product: [Fedora] Fedora Reporter: pindakoe
Component: darktableAssignee: Germano Massullo (Thetra) <germano.massullo>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 40CC: aekoroglu, asn, germano.massullo, klember, madko, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: darktable-4.8.1-1.fc40 darktable-4.8.1-1.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-08-12 01:37:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Trace Darktable 4.8.0 crash none

Description pindakoe 2024-07-13 10:54:38 UTC
Description of problem:
Darktable crashes after ~15 second, even if doing nothing

Version-Release number of selected component (if applicable):
darkatble-4.8.0-1

How reproducible:
always

Steps to Reproduce:
1. Start darktable (either from menu or from commandline)
2. Do nothing
3. DT crashes after ~15s with following message

>  darktable
an error occurred while trying to execute gdb. please check if gdb is installed on your system.
backtrace written to /tmp/darktable_bt_FY50Q2.txt
Segmentation fault (core dumped)

Note that NO backtrace is actually in /tmp (and it has free space).

Actual results:
DT crashes

Expected results:
DT can be used

Additional info:
Running Xfc4 4.18 as DE, problem appears with ot kernel kernel 6.9.7 and 6.9.8. Hardware unchanged and ample, using i5-9400 integrated video, so no OpenCL issue. Issue noticed today for first time, was not yet present on Jul 9. Have not yet been able to validate if any of these upgrades has a bearing on this issue.

Comment 1 pindakoe 2024-07-13 11:08:49 UTC
gdb installed and no have a backtrace if desired

Comment 2 Germano Massullo (Thetra) 2024-07-13 11:20:43 UTC
Please run as root, the following commands

# dnf debuginfo-install darktable
# coredumpctl list
there is one line that is about darktable crash. Get the PID shown there, then
# coredumpctl gdb PID_OF_DARTKABLE_CRASH
if asked "Enable debuginfod for this session? (y or [n])" say yes
if prompted "--Type <RET> for more, q to quit, c to continue without paging--" press c
then enter following commands
(gdb) set height 0
(gdb) set print elements 0
(gdb) set print frame-arguments all
(gdb) thread apply all backtrace

Save the output and attach it in this bugreport

Comment 3 pindakoe 2024-07-14 08:36:11 UTC
Created attachment 2039520 [details]
Trace Darktable 4.8.0 crash

Comment 4 pindakoe 2024-07-14 08:38:51 UTC
Comment on attachment 2039520 [details]
Trace Darktable 4.8.0 crash

For reasons unknown gdb did not prompt me to enable debuginfod. I have tried to force this using set debuginfod enabled on in /root/.gdbinit and ~/.gdbinit as well as 'teeing' the output to file. Hope the result is the output what you were asking for otherwise pls advise and I will dig deeper

Comment 5 pindakoe 2024-07-14 15:14:55 UTC
Looks similar to https://github.com/darktable-org/darktable/issues/17124 and fix being worked on by jenshannoschwalm.

Comment 6 pindakoe 2024-07-15 18:06:28 UTC
Hi Germano. Work on pixls.us (https://discuss.pixls.us/t/darktable-is-suddenly-crashing-without-warning/44545/46) resulted in a workaround which eliminates the segfault:

* Open ~/.config/darktable/darktablerc
* Locate the line starting with backthumbs_mipsize
* replace the value to never (i.e. backthumbs_mipsize=never)

Comment 7 Germano Massullo (Thetra) 2024-07-16 10:32:49 UTC
(In reply to pindakoe from comment #5)
> Looks similar to https://github.com/darktable-org/darktable/issues/17124 and
> fix being worked on by jenshannoschwalm.

I wrote to darktable developers and one developer confirmed that your crashreport seems to be related to 17124 Github bugreport

Comment 8 Fedora Update System 2024-08-03 14:13:02 UTC
FEDORA-2024-305bbff91d (darktable-4.8.1-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-305bbff91d

Comment 9 Fedora Update System 2024-08-03 14:13:03 UTC
FEDORA-2024-7df5300bc3 (darktable-4.8.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-7df5300bc3

Comment 10 Fedora Update System 2024-08-04 01:16:54 UTC
FEDORA-2024-305bbff91d has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-305bbff91d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-305bbff91d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2024-08-04 01:52:11 UTC
FEDORA-2024-7df5300bc3 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7df5300bc3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7df5300bc3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2024-08-12 01:37:24 UTC
FEDORA-2024-7df5300bc3 (darktable-4.8.1-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-08-12 04:58:17 UTC
FEDORA-2024-305bbff91d (darktable-4.8.1-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 pindakoe 2024-08-12 10:03:17 UTC
Have been out for a week so could not respond earlier. I have now installed DT4.8.1 and get same result: DT crashes with a segfault some time after opening.

Comment 15 pindakoe 2024-08-12 10:07:46 UTC
As before setting `backthumbs_mipsize` to never in darktablerc avoids the crash.