Windows: Crash on entering darkroom
Describe the bug
When selecting the raw image for post production, or when switching/clicking in the "darkroom" the program closes completely without the possibility of working on the images
Steps to reproduce
- Selecting the raw image for post production
- The program stops
Expected behavior
No response
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
downloaded from www.darktable.org
darktable version
darktable 4.6.1
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
without more information no one can help since it’s not a general issue. so give some more information, logfile, … see https://www.darktable.org/about/faq/#faq-windows-logs
I don't know how to explain it in other ways because the problem is very simple. When I want to select a RAW image directly from Darktable from the folders on my desktop and go to the "Darkroom" section (to then start my edits), the Darktable program stops
Il sab 11 mag 2024, 21:42 Martin Straeten @.***> ha scritto:
without more information no one can help since it’s not a general issue. so give some more information, logfile, … see https://www.darktable.org/about/faq/#faq-windows-logs
— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/16768#issuecomment-2106002372, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEKLU3PQMZEHOUCK5N3DQTZBZYDFAVCNFSM6AAAAABHSELISGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAYDEMZXGI . You are receiving this because you authored the thread.Message ID: @.***>
Telling us that the program crashes is no more useful in getting the bug addressed than telling a mechanic that your car doesn't work. Please provide the requested logs so that we can understand what the actual problem is.
Does the crash happen for any raw file from any camera? Any raw file, but only from a specific camera model? Only specific raw files? (you can download files from many different camera models from raw.pixls.us) Does the crash happen with JPEGs? Does the crash happen with images in a different folder? (special characters in the path have caused problems in the past) Does the crash happen if you reset darktable's configuration? (rename the .config/darktable directory to something else)
Does the crash occur with any raw file from any camera? - I have a camera and I only use this one so I don't know what happens to other cameras.
Some raw files, but only from a specific camera model? - I only use one camera
Only specific raw files? - 90% of RAW files don't work
Does the crash occur with JPEGs? - No
Does the crash occur with images in a different folder? - Yes
Does the crash occur if you reset the darktable configuration? - I don't know how I could do it but I uninstalled Darktable and redownloaded it 3 times
Il dom 12 mag 2024, 05:50 Ralf Brown @.***> ha scritto:
Telling us that the program crashes is no more useful in getting the bug addressed than telling a mechanic that your car doesn't work. Please provide the requested logs so that we can understand what the actual problem is.
Does the crash happen for any raw file from any camera? Any raw file, but only from a specific camera model? Only specific raw files? (you can download files from many different camera models from raw.pixls.us) Does the crash happen with JPEGs? Does the crash happen with images in a different folder? (special characters in the path have caused problems in the past) Does the crash happen if you reset darktable's configuration? (rename the .config/darktable directory to something else)
— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/16768#issuecomment-2106108018, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEKLUYWZ4B76AHB2FO4JXLZB3RG7AVCNFSM6AAAAABHSELISGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGEYDQMBRHA . You are receiving this because you authored the thread.Message ID: @.***>
giving more unspecific information doesn’t help. I can edit images from several cams every day on a windows machine without such issues. Does this information help in your case - obviously not. So if you’re interested to get help, be more specific, provide raw files that fails, log files - help the developers to reproduce your case (not my or their scenario) but keep in mind: most of them aren’t using windows and so they need log files to get an idea what might happen on your machine.
please read the windows related chapters of the faq: just uninstall/reinstall doesn’t affect your configuration - you need to do this manually
I would like to be more specific but I don't know where to get and how to verify the information you need.
If you can tell me what exactly the information you need would be, I will gladly try to provide it to you
Il dom 12 mag 2024, 10:53 Martin Straeten @.***> ha scritto:
giving more unspecific information doesn’t help. I can edit images from several cams every day on a windows machine without such issues. Does this information help in your case - obviously not. So if you’re interested to get help, be more specific, provide raw files that fails, log files - help the developers to reproduce your case (not my or their scenario) but keep in mind: most of them aren’t using windows and so they need log files to get an idea what might happen on your machine.
please read the windows related chapters of the faq: just uninstall/reinstall doesn’t affect your configuration - you need to do this manually
— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/16768#issuecomment-2106171765, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEKLU4YE3LSZFKZETFQL3LZB4U2DAVCNFSM6AAAAABHSELISGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGE3TCNZWGU . You are receiving this because you authored the thread.Message ID: @.***>
If you can tell me what exactly the information you need would be, I will gladly try to provide it to you
Did we not explain clearly enough how to get the necessary information or have you lost interest in this issue?
I'm sorry but I'm not able to go into specifics and provide specific files or code or anything.
The only thing I could possibly do is just a demo recorded screen video to show the moment it breaks.
For this reason I prefer not to waste your time, sorry.
Il gio 23 mag 2024, 20:43 Victor Forsiuk @.***> ha scritto:
If you can tell me what exactly the information you need would be, I will gladly try to provide it to you
Did we not explain clearly enough how to get the necessary information or have you lost interest in this issue?
— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/16768#issuecomment-2127813490, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEKLU4XXLH4BAMW6QY4ND3ZDY2FHAVCNFSM6AAAAABHSELISGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXHAYTGNBZGA . You are receiving this because you authored the thread.Message ID: @.***>
The only thing I could possibly do is just a demo recorded screen video to show the moment it breaks.
So you're a better Windows user than I am, because I still need to figure out which programs in Windows make screen videos. 🙂 But the video of the screen will not give us any information we need, it only visualizes the fact that the program crashes.
I'm sorry but I'm not able to go into specifics and provide specific files or code or anything.
No code or anything needed. Just specific file. You need to enter %LOCALAPPDATA%\Microsoft\Windows\InetCache\darktable in the path field of File Explorer. You probably can't navigate to this folder in File Explorer because the path to it contains hidden folder that aren't shown in File Explorer by default. In the open folder you will see the darktable-log.txt file. After that, we may also ask you to run certain programs from the command line.
If this is difficult for you, then first disable OpenCL in the darktable settings (processing > OpenCL) and check if this helps to avoid crashes. There are chances that it can help in your case.
I still don't understand what is going on and what is the problem with providing the specified file if there is an instruction with all the necessary steps for this, but since no information has been provided, I have to close this issue.