Segmentation fault when clicking on filter options in lighttable

[hannonq]

Describe the bug

After recently upgrading to darktable 4.8, I experience crashes in different places in lighttable.

Steps to reproduce

1. Open darktable
2. Click on Filter Preferences -> New Filter
3. Darktable crashes with segmentation fault
4. Same happens when clicking on Sort by and trying to change from the default "filename"

Expected behavior

darktable should offer the expected options from the menus and not crash

Logfile | Screenshot | Screencast

Crash happens when clicking on the "New filter" arrow here:

Log file:
darktable-logs.txt

Commit

No response

Where did you obtain darktable from?

I dont know

darktable version

darktable 4.8.0

What OS are you using?

Linux

What is the version of your OS?

EndevourOS

Describe your system?

System:
Intel i7
32GB RAM
NVIDIA GeForce GTX 1650 Ti
Gnome Shell on Wayland

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce GTX 1650 Ti 4GB, NVIDIA Driver Version 555.58.02

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

Darktable was installed using yay, but I chose "I don't know" because I'm not sure which option fits best from the dropdown menu. Issue didn't happen in previous version of darktable, but started happening after updating darktable via yay

Issue still happens if I run darktable with opencl disabled e.g. darktable --disable-opencl

Issue persists after removing my old library.db and (later) ~/.conf/darktable and adding a small collection of new photos.

Is the issue still present using an empty/new config-dir

Yes.

I saw this bug report, but it looks like it's a different issue.

[ralfbrown]

Unfortunately, it seems your executable has been stripped of debug info, so the only thing that can be determined from the log is that the crash happened somewhere deep inside the GUI toolkit darktable uses....

Wayland has been problematic in the past, but I'll need to leave it to others to say whether it's still an issue with 4.8.

[hannonq]

Unfortunately, it seems your executable has been stripped of debug info

Is there a flag I can use to run darktable with better debug logs?

[ralfbrown]

The best info for tracking down a crash comes from the backtrace - what you have in the log you uploaded. But only if it also includes line-number information, which your log doesn't, and there's no way to enable it without recompiling.

Adding commandline flags like "-d common" can help narrow down the problem by telling us that darktable got at least as far as point X, but doesn't pinpoint it like a full backtrace does.

[jenshannoschwalm]

Adding commandline flags like "-d common" can help narrow down the problem by telling us that darktable got at least as far as point X, but doesn't pinpoint it like a full backtrace does.

Please note there is a bug in 4.8 that will crash dt when -d imageio is enabled.

[victoryforce]

@hannonq I can't reproduce the crash on Windows and Ubuntu.

I suggest you download AppImage from the official website, make it executable and run . If it works without problems (which I hope it will), then it's a problem with the darktable build in your distro. If AppImage also crashes, I can only suspect another problem with Wayland.

[hannonq]

I ended up (hopefully temporarily) switching to Windows because I also have other Wayland issues (for example, I can't add tags when running on Wayland like mentioned on this issue).

I need to find a working solution for DE with (fractional) scaling first :(

I'll close this issue for now. Thanks for your input, everyone.