(Solved) Lua not present in my dt install - how to correct this ?

Software darktable
1

Apologies if this post should have been made in my distro support forum - but responses here are very thorough and helpful.

Running Mint 22.3 with dt 5.2.1 installed from OBS using ‘Add repository and install manually’, for Ubuntu 24.04 base. Lua scripts installed via git clone into ~/.config/darktable as per the manual. (Previously installed AppImage version renamed).

dt launched from menu; functions as expected but there is no Lua module in lighttable. Is this my error? If so, what should I be doing to correct it?

2

Thank you for asking! I have the same: no lua.

I am running the same Linux, dt from the same source, but master branch. So 5.3. I won’t check the exact release right now, it doesn’t matter as I haven’t noticed lua for ages. I do not yet use it, so it is not a big thing thing for me, but one day I might, and some days I wonder how to resurrect it.

3

The module is called scripts and should default to appearing at the bottom of the left-hand mouldes panel. If it is not there, one thing to try is to right-click in an empty area in the left-hand module panel and ensure that scripts is ticked.

1 Like
4

Very interesting; thank you. Right clicking thus reveals a list of ‘modules’ which does NOT includes ‘scripts’ or anything that has equivalent meaning.

1 Like
5

There are several suggestions in another thread, so if you’ve not already tried them they may give some ideas:

6

i just had the same effect. When I start one of the nightly builds of version 5.3.0 and afterwards open 5.2.0, the script manager is gone. There is a message shown to restart darktable to get the right versions of the scripts, but this message can be missed easily…

1 Like
7

This was useful: I read most of it, noting the advice to start dt with the ‘-d lua’ option from the command line. This immediately revealed the ‘scripts’ module. I then ran dt without any options from the command line. Again, the ‘scripts’ module was available. Finally I ran dt using my menu launcher; again the ‘scripts’ module was available.

So, while I have no real understanding of what changes, if any, to luarc (or even darktablerc) have been made by these attempts, I now seem to have an install of dt 5.2.1, from the OBS, with lua scripts available.

Thanks for your help. I think there is no option to (i) indicate this problem is now solved or (ii) close the topic - correct?

1 Like
8

I think you are probably right. I see some topics have their subject line changed to include [Solved] but I don’t know who can edit subject lines.

9

Original poster and moderators should be able to change the title of a thread?
@LateJunction could try to edit his original post…

Closing a subject is usually reserved for (some) moderators.

1 Like
10

The lua-scripts try to be “self-healing” and self updating to minimize the amount of manual interaction required to get them running.

Some things you can try if you have problems

  • Go to your config directory and rename the luarc file to something else. This should cause the scripts installer to start the next time you start darktable and let you do a fresh install of the scripts
  • Go to the config directory, make a backup of your darktablerc file, then edit it and remove all the lines with lua in them. That way you still have your everything installed but you start with a fresh lua configuration.
  • The -d lua flag will give you information.
11

this was the answer for me.

I linuxed the path to ~/.config/darktable/lua , went to that directory and did the git pull

I have scripts again :slight_smile:

12

@wpferguson Could you explain the behavior I noticed when switching from 5.3.0 dev versions back to 5.2.0? The script manager does not show up, but the scripts are still there in the lua folder. After starting darktable 5.2.0 a second time everything works fine again.

13

The API changed in 5.3 to 9.6.0. 5.2.0 is 9.5.0. script_manager automatically updates the script to the latest compatible version, to when you ran 5.3 it upgraded to a version not compatible with 5.2.0. When you restarted script_manager fixed it.

3 Likes