Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

darktable-cli crashes when opening folders #3175

Closed
Ruderknecht opened this issue Oct 16, 2019 · 5 comments
Closed

darktable-cli crashes when opening folders #3175

Ruderknecht opened this issue Oct 16, 2019 · 5 comments
Assignees
Labels
bugfix pull request fixing a bug
Milestone

Comments

@Ruderknecht
Copy link

Hi all,

i try to run a script, which should run darktable-cli on folders.

I try to run the following command:

darktable-cli /home/lutzifer/Bilder/NEF/tmp1 /home/lutzifer/Downloads/bench.SRW.xmp /home/lutzifer/Bilder/JPG3/$FILE_NAME.png --hq 1 --core --library :memory: -t 8 --conf opencl_device_priority='1/1/1/1'

Giving a single Image as input it will not crash.
The interesting thing is that this command without the "opencl_device_priority='1/1/1/1'" also crashes on a second linux system.

The two systems are:
Intel E5-2667v2
Opensuse 15.1
Darktable 2.6.2 (also a user repo 2.7.0-....)

Intel E5-2630v2
Ubuntu 18.04.3
Darktable 2.4.2

Here are the backtrace files from darktable.
darktable_bt_OpenSuse15.1.txt
dartable_bt_Ubuntu18.04.3.txt

@Ruderknecht
Copy link
Author

Ruderknecht commented Oct 21, 2019

Similar behaviour was reported before 9 month in:

#2008

On a Windows10 with Darktable 2.4.4 amd 2.6.2 it works.

@Ruderknecht
Copy link
Author

All builds since 20 days including 3.0rc0 showing the same behavior.

Opening only a folder with darktable-cli like described in man-pages chrashes with linux.

@TurboGit
Copy link
Member

TurboGit commented Nov 4, 2019

Should be fixed.

@TurboGit TurboGit added the bugfix pull request fixing a bug label Nov 4, 2019
@TurboGit TurboGit self-assigned this Nov 4, 2019
@TurboGit TurboGit added this to the 3.0 milestone Nov 4, 2019
@Ruderknecht
Copy link
Author

I can confirm that it is fixed.

Is it only fixed in 3.0 or also in 2.6.3? Thanks a lot!

@TurboGit
Copy link
Member

TurboGit commented Nov 5, 2019

Will be in final 3.0 only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix pull request fixing a bug
Projects
None yet
Development

No branches or pull requests

2 participants