darktable-org / darktable-org/darktable

dt crash after system sleep

Open
#20,693 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
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

dt current master. If I leave dt running and the desktop goes to sleep, dt will crash when I return from the sleep state.

I suspect is it a Wayland / Kwin issue. dt logs show nothing.

I asked in the darktable irc channel and others cannot reproduce on X11.

Steps to reproduce
  1. Start dt and leave it running.
  2. Prompt your OS to go into sleep.
  3. Restart from sleep.
Expected behavior

No response

Logfile | Screenshot | Screencast

backtrace.txt

Commit

No response

Where did you obtain darktable from?

OBS build

darktable version

5.5.0~git792.b204f407

What OS are you using?

Linux

What is the version of your OS?

Fedora 43 KDE Wayland Kwin

Describe your system

Fedora 43 KDE Wayland Kwin Nvidia 3060 GPU

Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.8-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 3060
Graphics Processor 2: AMD Radeon Graphics

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

Nvidia 3060 580.126.18

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

It happens with -disable-opencl.
No Lua scripts.
I self compiled and it also crashes.

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 with the attached backtrace.txt and reproduce the crash by leaving darktable running through sleep and resume on Fedora KDE Wayland. Compare behavior with and without OpenCL as reported, and consider the issue done when the sleep/resume crash is identified and no longer occurs in the reported setup.

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
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.