@T70 I need a little more information so that I can help.
What version of windows?
Where did you get darktable from?
How were you starting darktable? From the menu, double clicking on an image, opening a raw file in gimp and gimp starting darktable?
Can you open a windows command prompt and do the following:
Where did you get darktable from? Github, $ sha256sum darktable-3.4.0.exe
29dee565292a4a72443874bb970663d46420f5a9ba74a5acfcb3251a48c86f7c darktable-3.4.0.exe
How were you starting darktable? From the menu, double clicking on an image, opening a raw file in gimp and gimp starting darktable? From the menu or from the Desktop with Windows shortcut.
Can you open a windows command prompt and do the following:
No, it gives me an error message:
C:\Users\surf>C:\Program Files\darktable\bin\darktable.exe" -d lua > crash.txt
Der Befehl “C:\Program” ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
I tried the german version C:\Programme… with the same result.
I used the option to uninstall the previous version when installing 3.4.0
Because the directory name “Program Files” contains a space character, it needs to be properly quoted, so that the CMD shell treats the whole path as a single element.
Oh, ok… here it is:
[init] can’t rename style_items to s
[init] attempt to write a readonly database
[init] database `C:\Users\surf\AppData\Local\darktable/data.db’ couldn’t be upgraded from version 4 to 8. aborting
first rename your C:\Users\surf\AppData\Local\darktable
directory to darktable.old just to check if darktable can start with defaults.
If thats ok you might replace the new generated data.db and library.db with the files from the darktable.old directory. If thats also ok, you might compare the darktablerc files to find differences …
no matter, it’s just starting with a plain config to exclude config issues. So see „first“ as first step to find the issue …
Since dt couldn’t write to data.db it should be ok
Yes, it starts, but without any specific settings, of course…
I have old versions of database files like data.db-pre-3.0.0 and data.db-pre-3.0.2 and data.db-pre-3.4.0 in the old folder. Could I use them for restauration?
One thing to remark: I am logged in as a restricted Windows user, not as admin. Does that matter?
Next step ist to copy back library.db and data.db-pre3.4 (rename it to data.db), darktablerc and the subdirectories. If dt start is successful then it seemed to be some security side effects that prohibited write access to the database files.
I did. Then I controlled file properties of all that files and some were write-protected by Windows! I never did that. I switched write protection off and it started ONE TIME.
In the next start it froze again
I manually deleted two lock files, but no next start.
C:\Users\surf>“C:\Program Files\darktable\bin\darktable.exe” -d lua > crash.txt
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 0 to 2097152
Magick: Unable to access configuration file (delegates.mgk) [No such file or directory].
[dt_imageio_export_with_flags] mipmap allocation for unused' failed [dt_imageio_export_with_flags] mipmap allocation for unused’ failed
[dt_imageio_export_with_flags] mipmap allocation for unused' failed [dt_imageio_export_with_flags] mipmap allocation for unused’ failed
[dt_imageio_export_with_flags] mipmap allocation for unused' failed [dt_imageio_export_with_flags] mipmap allocation for unused’ failed
[dt_imageio_export_with_flags] mipmap allocation for `unused’ failed
To get a working DT again, I restored a backup of my appdata folder and installed DT 3.2.1 “again”. Then I saw that 3.2.1 had to convert the restored database, so my last version must have been 3.0.2, not 3.2.1, when I tried to install 3.4.0.
But 3.2.1 also gives me a problem message, see the attached file, and does not start a second time.
And by the way, that last crash (of Darktable 3.2.1) even happens without a darktable appdata folder, it seems to have nothing to do with database conversion.
The trace back file you supplied shows darktable crashing on a string compare in the luarc file. But, if it ran correctly once, why is it crashing on the second run? And the fact that it runs correctly after a reboot says the file is OK.
I don’t really have a way to troubleshoot this. I run Win7 in a VM for testing and don’t have access to Win10.
I wonder what changes between runs. Can you try disabling any antivirus/protection software and see if you can get two runs without a crash. You can disconnect your computer from any networks, if you are concerned about threats, since darktable doesn’t require a network interface to run.
Yes, definitely! I only use the original built-in Windows Defender and switching its real time protection off made multiple starts possible! For the moment I made an exclusion for the darktable.exe.
And now I updated from 3.2.1 to 3.4.0 and still have no crashes on startup, thanks to the exclusion. There seems to be a conflict with the Windows virus scanner, indeed.