darktable icon indicating copy to clipboard operation
darktable copied to clipboard

`Flickr script` causes Darkable to crash

Open jtmart opened this issue 11 months ago • 5 comments

Describe the bug

I installed the Flickr exporter Lua script from https://github.com/arru/darktable-scripts. The installation went fine, but when running it causes Darktable to crash. I guess the Lua script might be outdated, in this case is there anything up to date I can use?

Steps to reproduce

  1. Open Darktable in normal or debug mode (i.e. "C:\Program Files\darktable\bin\darktable.exe" -d all)
  2. Go to "export" module/pane
  3. Select "Flickr script"
  4. Click "export"

Expected behavior

Not crash...

Logfile | Screenshot | Screencast

darktable-log.txt

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

5.0.0

What OS are you using?

Windows

What is the version of your OS?

Windows 11

Describe your system?

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

jtmart avatar Jan 01 '25 15:01 jtmart

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Mar 03 '25 00:03 github-actions[bot]

According to the attached log the flickr script wasn't found and didn't load.

    58.6475 LUA ERROR : C:\Users\jtm\AppData\Local\darktable\luarc:2: module 'flickr' not found:
	no field package.preload['flickr']
	no file 'C:\Program Files\darktable\bin\..\share\lua\5.4\flickr.lua'
	no file 'C:\Program Files\darktable\bin\..\share\lua\5.4\flickr\init.lua'
	no file 'C:\Program Files\darktable\bin\..\lib\lua\5.4\flickr.lua'
	no file 'C:\Program Files\darktable\bin\..\lib\lua\5.4\flickr\init.lua'
	no file '.\flickr.lua'
	no file '.\flickr\init.lua'
	no file 'C:\Program Files\darktable\share\darktable/lua/flickr.lua'
	no file 'C:\Users\jtm\AppData\Local\darktable/lua/flickr.lua'
	no file 'C:\Users\jtm\AppData\Local\darktable\lua/flickr.lua'
	no file 'C:\Program Files\darktable\bin\..\lib\lua\5.4\flickr.dll'
	no file 'C:\Program Files\darktable\bin\..\lib\lua\5.4\loadall.dll'
	no file '.\flickr.dll'

Where did you install the script to?

Are you using script_manager or are you manually editing the luarc file?

wpferguson avatar Mar 03 '25 00:03 wpferguson

Spun up a new darktable install and added the flickr script. Started, stopped, and restarted darktable with the flickr script enabled and no crashes.

wpferguson avatar Mar 04 '25 04:03 wpferguson

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar May 04 '25 00:05 github-actions[bot]

What puzzled me is how the "Flickr script" target could appear in the export module, if the log shows that this script was not found and did not load.

victoryforce avatar Jun 21 '25 10:06 victoryforce

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Aug 22 '25 00:08 github-actions[bot]

I'm closing the issue for the following reasons:

  • Not reproducible when following the steps in the issue description

  • It's not even clear how what was described in the issue could have happened (the attached log shows that the script was not found and was not loaded, and the steps for reproducing describe that the corresponding target in the export appeared - it just can't be)

  • No additional comments from the issue author.

There's simply no point in keeping the issue open, as it's unlikely that new information will be provided. If this happens, the issue can always be reopened.

victoryforce avatar Oct 04 '25 19:10 victoryforce