FYI : Darktable segfaulton latest -current

lougavulin · 12-20-2020, 12:55 PM

Hello,

I don't think this is going to "SBo scripts not building on current" thread, as Darktable compile.
But latest darktable 3.2.1 or darktable 3.0.2 from Ponce's slackbuild repo does a segmentation fault at the beginning when launched.

To be able to run darktable, I had to downgrade mesa to 20.2.3 version. The previous 20.3.0 version does not solve the issue.
I built the latest pugixml version and used lensfun from -current.

ponce · 12-20-2020, 01:38 PM

you can open an issue upstream

https://github.com/darktable-org/darktable/issues

EDIT: FWIW I just built its latest version (3.2.1) together with its dependency pugixml and doesn't crash here when launched.

USUARIONUEVO · 12-20-2020, 02:16 PM

Some people experiencing issues with mesa branch 20.3.x , i got some of this segfaults on my laptop under i7500u with integrated graphics.

lougavulin · 12-20-2020, 02:41 PM

Quote:

Originally Posted by ponce

you can open an issue upstream

I just open an issue upstream, providing gdb backtrace and my graphic card model (Intel Corporation Skylake GT2 [HD Graphics 520] integrated with i7-6500U).

Quote:

Originally Posted by ponce

EDIT: FWIW I just built its latest version (3.2.1) together with its dependency pugixml and doesn't crash here when launched.

I hope it would be useful and I don't bother them...

sunjob · 11-04-2023, 02:10 PM

I confirm the problem

Code:

- Lenovo T460

- Operating System: Slackware 15.0
- KDE Plasma Version    : 5.23.5
- KDE Frameworks Version: 5.90.0
- Qt Version            : 5.15.3
- Kernel Version        : 5.15.19 (64-bit)
- Graphics Platform: X11
- Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
- Memory    : 15.1 GiB of RAM
- Graphics Processor: Mesa Intel® HD Graphics 520

- tde-4.0.13 (add check)

- darktable ver. 3.6.1, 3.8.1, 4.2.1
- mesa-21.3.5-x86_64-2
- pugixml-1.14-x86_64-1_SBo
- argyllcms-2.3.1-x86_64-1_SBo.tgz
- colord-1.4.6-x86_64-1_SBo.tgz
- colord-gtk-0.3.0-x86_64-1_SBo.tgz
- gmic-2.9.4-x86_64-2_SBo.tgz
- jam-2.5-x86_64-2_SBo.tgz
- lensfun03-0.3.3-x86_64-2_SBo.tgz
- libdatrie-0.2.11-x86_64-3_SBo.tgz
- libgusb-0.4.7-x86_64-1_SBo.tgz
- libthai-0.1.28-x86_64-2_SBo.tgz
- pugixml-1.14-x86_64-1_SBo.tgz
- python-importlib_metadata-4.10.1-x86_64-1_SBo.tgz
- python-zipp-3.8.0-x86_64-1_SBo.tgz
- python3-attrs-21.4.0-x86_64-1_SBo.tgz
- python3-build-1.0.3-x86_64-1_SBo.tgz
- python3-calver-2022.6.26-x86_64-1_SBo.tgz
- python3-editables-0.5-x86_64-1_SBo.tgz
- python3-fastjsonschema-2.17.1-x86_64-1_SBo.tgz
- python3-flit_core-3.9.0-x86_64-1_SBo.tgz
- python3-hatch_fancy_pypi_readme-23.1.0-x86_64-1_SBo.tgz
- python3-hatch_vcs-0.3.0-x86_64-1_SBo.tgz
- python3-hatchling-1.18.0-x86_64-1_SBo.tgz
- python3-installer-0.7.0-x86_64-1_SBo.tgz
- python3-jsonschema-4.17.3-x86_64-1_SBo.tgz
- python3-pathspec-0.11.2-x86_64-1_SBo.tgz
- python3-pluggy-1.3.0-x86_64-1_SBo.tgz
- python3-pyproject-hooks-1.0.0-x86_64-1_SBo.tgz
- python3-pyrsistent-0.19.3-x86_64-1_SBo.tgz
- python3-trove-classifiers-2023.10.18-x86_64-1_SBo.tgz
- python3-wheel-0.41.2-x86_64-1_SBo.tgz

metageek · 01-25-2024, 12:25 PM

I also see this problem, even after upgrading to 4.2.1.
I managed to get it running by calling it with

Code:

darktable --disable-opencl

which I suppose disables using GPUs