darktable-org / darktable-org/darktable

Consistent segfaults on starting program (appimage)

Open
#21,996 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: regression scope: UI
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

Attempting to start any of the appimage releases, either the current 5.6 or any nightly 5.7, will crash during the splashscreen with a segfault. The backtrace sometimes gives no useful information, only stating this is darktable 5.7.0+611~g66c56ab7da reporting a segfault:, but usually it will give something like the attached log below.

This happens nearly every time. It takes bruteforce attempts of reopening for Darktable to finally get past the splashscreen of loading library/modules. I've also had it work immediately after opening/closing the system 5.6 installation, but it's not guaranteed so I'm not sure if it actually has an effect or not.

Eventually after a few attempts Darktable will open, but it does to tend to crash on idle after an indeterminate period of time if I leave the program running once I'm finished editing. For example when making the issue it took the 4th attempt for Darktable to open. First attempt gave a useless log only stating what I wrote in the first paragraph; I tried again with a minute and got the log attached to the issue; 9 minutes later attempted again but opening through a different shell to test (fish instead of nushell); 4th attempt was about 9-10 minutes later where Darktable was

Steps to reproduce
  1. chmod +x ./dt.AppImage
  2. ./dt.AppImage
Expected behavior

No response

Logfile | Screenshot | Screencast

1st attempt: darktable_bt_7R86T3.txt

2nd attempt: darktable_bt_4THAU3.txt

3rd attempt: darktable_bt_GA1AU3.txt

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.7.0+611.g66c56ab7da-x86_64

What OS are you using?

Linux

What is the version of your OS?

Void Linux

Describe your system

CPU: AMD Ryzen 5 3600 (12) @ 4.21 GHz
GPU: AMD Radeon RX 5700 XT [Discrete]
RAM: 32GB
WM: niri 26.04 (Wayland) - this also happens on x11 w/bspwm
GTK: gtk+3-3.24.52_1, gtk4-4.22.4_1

Are you using OpenCL GPU in darktable?

I dont know

If yes, what is the GPU card and driver?

AMD Radeon RX 5700 XT [Discrete], 8GB, amdvlk-2025.Q1.3_1, linux-firmware-amd-20260810_1

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash with the AppImage commands in the issue and inspect the three attached backtraces. Compare the failing AppImage launches with the system installation, including the reported Wayland and X11 environments, to narrow down the startup path involved. Done means the AppImage starts reliably without the reported segfault and no longer crashes while idle under the reported conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.