I would also suggest a darktable-cltest -d verbose
darktable-cltest will not give much result – I have no OpenCL capable device, i.e. execution is CPU only (and integrated GPU).
Output of darktable -d opencl -d cache -d pipe below; note that compared to yesterday I have (for other reasons) doubled RAM in my machine
dtdebug2.txt (97.8 KB)
I will also re-open the bug at Fedora on this, but that is more for completeness than that it will solve matters (I expect) – this post originally started with Bruce Williams reporting this issue on 4.8.0; he is not running Fedora (see first post). His report suggests that the issue is not linked to DT4.8.0 per se (it initially worked), but that it appeared in first week of July. My own notes suggest the same – I did export a dozen or so pictures using 4.8.0 and then ran into the issue on Jul 13.
1.8025 [opencl_init] opencl library 'libOpenCL.so.1' found on your system and loaded, preference 'default path'
1.8026 [opencl_init] 0 platforms detected, error: Unknown OpenCL error
1.8026 [opencl_init] FINALLY: opencl PREFERENCE=OFF is NOT AVAILABLE and NOT ENABLED.
There is an opencl library installed in your system and an openCL error. Is your CPU/iGPU an AMD one?
No, intel i5-9400
I checked your latest log file and atm can’t make anything out of that as it seems the crash happens in some gtk function gtk_widget_get_scale_factor()
I don’t think this is related to the issue mentioned above, i would appreciate if you could open a github issue about this. X11 or wayland ??
Don’t understand. Do you compile dt yourself and suspect any code change that triggers this issue? Or some fedora update? Do you take dt from the fedora repo?
I run X11 (use Xfce as desktop). I do not compile DT myself; install from Fedora’s repo’s only. I hold it for possible (suspect is too strong a word) that an update of another package caused this (as I did ran 4.8.0. succesful once or twice just testing it after the upgrade), but have been unable to identify which update would have caused this. Having said that at least one other person (bruce) saw the same issue on a different linux with (likely) different.
Issue created at Github: Darktable crashes in ~20s without doing anything · Issue #17322 · darktable-org/darktable · GitHub