so try starting darktable in a terminal with the command
"\Program Files\darktable\bin\darktable.exe" =d lua
```
The log will be in `%LOCALAPPDATA%\Microsoft\Windows\InetCache\darktable\darktable.log`
Let's see what that says
so try starting darktable in a terminal with the command
"\Program Files\darktable\bin\darktable.exe" =d lua
```
The log will be in `%LOCALAPPDATA%\Microsoft\Windows\InetCache\darktable\darktable.log`
Let's see what that says
You are on master
You meant -d lua
, I think. So
"\Program Files\darktable\bin\darktable.exe" -d lua
Yep.
Yep
Thank you for the answer!
Yes, I noticed the â=â
The response in darktable-log.txt is the following:
========================================
version: darktable 4.4.2
start: 2023:10:19 20:29:26
sqlite3 error: C:/msys64/home/bill/src/darktable-4.4.2/src/gui/presets.c:86, function dt_gui_presets_init(), query âDELETE FROM data.presets WHERE writeprotect = 1â: attempt to write a readonly database
sqlite3 error: C:/msys64/home/bill/src/darktable-4.4.2/src/libs/modulegroups.c:1352, function _preset_retrieve_old_presets(), query âDELETE FROM data.presets WHERE operation = âmodulelistâ AND op_version = 1â: attempt to write a readonly database
48,1318 LUA ERROR : cannot open C:\Users\MyUserName\AppData\Local\darktable\luarc: No such file or directory
In my âC:\Users\MyUserName\AppData\Local\darktable\folderâ however are only the two subfolders mentioned above, namely
C:\Users\MyUserName\AppData\Local\darktable\lua
C:\Users\MyUserName\AppData\Local\darktable\lua-scripts
and no âluarcâ subfolder - never has been such a folder âŚ
luarc is a file, not a folder. The lua-scripts folder can go away. The lua folder is where the lua-scripts are installed to.
The luarc file should contain the line require "tools/script_manager"
From a terminal in %LOCALAPPDATA%\darktable
type the command
echo require "tools/script_manager" > luarc
Yes, your âecho âŚâ command created the file, and now the script manager reappeared. Problem solved! Thank you!
The question here is, why the file disappeared in the first place. It must have been there before my script manager disappeared, and I did not erase it.
Now, thinking even further back in time, I remember having this problem a few times before, but restarting darktable resolved it, until this last time âŚ
Not related to Lua, but those
attempt to write a readonly database
log lines donât look good. Is your DB read-only?
Yes it is read-only, and I just turned the attribute off. Thank you for the notice!
I also noticed the following (also not related to lua): If I start darktable from the terminal (âcmdâ in Windows), then a log entry is written to the âdarktable-log.txtâ file, but if I start darktable from Windows shortcut (in Start menu), containing the same command line, nothing is written to the log file âŚ
Thanks, Bill - git pull updated the script and now all is well again. Thank you.