-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Git master : darktable action gives death skull icon in lighttable : import of tiff gives death skull in lighttable : two issues #17536
Comments
@KarlMagnusLarsson : Can you test #17537? It should fixes your issue. |
I have the same issue on darktable 4.9.0~git581.7970d714-11987.2 and came here to open an issue. If needed, happy to provide more logs/info. Operating System: openSUSE Tumbleweed 20240924 |
Describe the bug
There are two issues pointing to the same commit when I bisect:
Steps to reproduce
Expected behavior
Darktable should display lighttable icons as usual when raw (or jpg) files are changes in darktable. TIFF-files should display normally as icons in lighttable after import.
Logfile | Screenshot | Screencast
Git bisect gives me this:
Commit
7dc0faf is the first bad commit
Where did you obtain darktable from?
self compiled
darktable version
release-4.9.0-580-g3b57b3301e
What OS are you using?
Linux
What is the version of your OS?
Linux Debian 12.7
Describe your system?
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
NVIDIA Corporation TU104GL [Quadro RTX 4000], 535.183.01-1~deb12u1 amd64
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
**Can you reproduce with another darktable version(s)? 7dc0faf is the first bad commit
Can you reproduce with a RAW or Jpeg or both? raw, jpg and tiff behaves differently as stated in describe the bug. Raw and jpg import nicely to lighttable but get a death skull if manipulated in darkroom. Imported TIFF get a death skull in lighttable directly after import
Are the steps above reproducible with a fresh edit (i.e. after discarding history)? yes
If the issue is with the output image, attach an XMP file if (you'll have to change the extension to .txt)
Is the issue still present using an empty/new config-dir (e.g. start darktable with --configdir "/tmp")? yes
Do you use lua scripts? no
Open CL: Open CL on or off does not matter.
The text was updated successfully, but these errors were encountered: