![]() ![]() I'm curious if anyone else experiencing this issue can reproduce this behavior, and perhaps shed some light on what the problem may be. So far in my case the behavior described above is 100% reproducible. now no matter where I open a file from the UI will be brokenĪnd conversely, if I do the same thing but starting from opening the file from my C: drive, the UI is 'stuck' in a working state no matter where I open a file from. ![]() ![]() edit file and close darktable, file opens in GIMP.darktable gets called to open, UI is broken.open a RAW file from my SD card to GIMP.Additionally, whichever method I use seems to 'stick' if I leave the file open in GIMP after editing in darktable. If I first move the RAW file to my C: drive and open it the same way, the UI opens correctly. It seems that the UI only breaks if opening a RAW file directly from my SD card to GIMP which then calls darktable to open. Perhaps someone smarter than myself can figure it out. I believe I've found a workaround, but I still don't know what the root cause is or why this fixes it. If it does (I think it will, because there is not much difference between the 2 branches, regarding this plug-in): Would you mind testing if the issue also exists on the development build ? The CI is currently running, once it finishes, you can probably just swap the binaries for the plug-in.īut I realize we still have not updated the CI to build for Windows on the 2.10.x branch. So since this code was already there, I added the environment list, and even pushed it to our main branches (2.10.x and 2.99.x). Sorry all for the late intervention! This start of 2021 has made me late on quite some things!Īnyway I just looked at the code and saw that the stdout and stderr were already printed to stdout if DARKTABLE_DEBUG environment variable was set. I'm sorry, I don't know how to do a backtrace on Windows, but if you need more info about the bug, I will try to provide it. Processor: Intel(R) Core(TM) i7-10750H CPU 2.60GHz (12 CPUs), ~2.6GHzĬard name: NVIDIA GeForce GTX 1660 Ti with Max-Q Design System Model: HP Pavilion Gaming Laptop 17-cd1xxx See below for a ink to one of my NEF files: I have replicated the issue with more than one NEF file. I have replicated this same issue on both my desktop and laptop. See below for images illustrating the bugs: Also, the lines are present as usual on the base curve module. Note that these issues do not occur when I open darktable independent of GIMP, nor do they occur when I roll back to a previous version of Darktable (3.0.2) with all other factors remaining the same. Also, the horizontal line on the sliders in various modules are missing, for example, in the 'Tone equalizer' module, or the 'White balance' module. Since updating, when opening a NEF file in GIMP while having darktable set as my RAW image importer, some elements of the GUI are missing, for example, the gridlines on the 'Tone curve' module, plus the diagonal adjustment line are missing. Forgive me, I'm a bit of a layman when it comes to GitHub and developing, but I'm trying to make this a useful bug report.īug details: I recently upgraded to both of the latest versions of GIMP and darktable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |