Hi Jan,
did you try with an empty ~/.config/darktable (backup first !!!).
Sometimes weird things happen when darktablerc or database is corrupted
(or contains corrupted entries).
As far as I remember 3.4.1.1 is a *windows-only* bugfix. Not sure what
happens if you try to run it on Manjaro Linux.
Best regards Peter
Am 18.04.21 um 23:18 schrieb Solarer:
Hi Peter,
OpenCL was not installed/enabled, but doing that did not fix the issue.
I also generated the thumbnail images with darktable-generate-cache
--max-mip 8 - same result.
The problem occurs on Manjaro Linux (git master 3.5.0+1747~gc22f6a90e)
and also the non-git release (3.5.0+1681~g6de42c792-dirty).
But not on my Windows 3.4.1.1 (non-git) installation using the same
hardware (dual-boot installation).
I tried to checkout the 3.4.1.1 release on Manjaro as well but I get a
segmentation fault - can't roll back that far. When I rolled back a few
100 commits to about 3.5.0+13xx the problem still occured. So it is not
a new change that is responsible.
My hardware is:
Nvidia 970GTX
AMD 3700X
Gigabyte X570 Pro
Please find attached the seg fault from when I tried to checkout 3.4.1.1
(git checkout 3641764ed2a2443a495d6769355d644bf9cb7710). If I could test
that version on Manjaro we might learn more.
Thanks and best regards,
Jan
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
