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 crash with gmic library #4067
Comments
Probably somethink similar, DT crash when lauding image with " ... took 0,236 secs (0,422 CPU) to load the image. Platform :
Libgmic1 1.7.9+zart-4build3 |
When reverting to darktable version 3.1.0+308~g2f82a6e43, DT run nicely |
@kikoucalou, There two issues there: |
@jpverrue, your gmic version seems to be the last one. |
@jpverrue, did you open the lut3d module and select a compressed lut ? |
@jpverrue from the GMIC site the dependencies of the gmic library are the followings:
Could you check you have all of those (the run time ones) ? |
Updated to libgmic1 & libgmic-dev version 1:2.7.4+om-ubu18.04.1.1 and make a new build : Darktable 3.1.0+323~gaae21bfd5 is runing fine again |
👍 Other important point, when updating gmic library: do not forget to reset cmake (delete file CMakeCache.txt in build folder). If not it can keep the old library. |
I've found an issue. GMIC version is expressed with 3 or 4 numbers. And obviously 1.6.6.1 is above 2.7.0 ... I can fix that. |
You mean below/less/older, not above. |
Yes :) |
I use opensuse tumbleweed in the latest version (20200107). The installation tool is not apt-get, but zypper. The package names are also slightly different. So I can't easily check if the right packages are installed, but I trust zypper which handles dependencies very well. However, an error is always possible. How can I detect a possible missing dependency? |
@jpverrue before spending time looking at dependencies, I would like to check you have reset cmake after installing gmic 8.2 (deleting file CMakeCache.txt in build folder should be enough). When I run the test the first time, I've forgotten that and cmake still used the previous installed library, preventing dt to work. |
hmmm ... it seems that deleting the full content of build is safer. Playing some tests again I've seen that removing CMakeCache.txt were not always enough. |
I mainly compile Git versions. In order not to take any risk, I almost systematically remove the build directory before starting the compilation. Similarly, before installing, I remove the /opt/darktable directory. It's a bit heavy, but it's very secure. I have a script that does all this simply. It's only when I do tests in the code that I don't take these precautions. |
This means that cmake should consider your last installed version. But the crash message you get shows that either dt doesn't find the library, or it sees a library which is not the good one. With this commit there are 3 possibilities
In case 2.1 and 2.2, dt will crash if it doesn't find the library. I would (if you have time :-))
I've the impression dt doesn't see the (right) run time library ... but I don't know how to check this on linux. |
When I uninstall libgmic1 and libgmic-devel and then recompile darktable it no longer crashes. In the log of build.sh I have this message:
When I install libgmic1 and libgmic-devel and then recompile, darktable crashes, but now without even displaying the light table. In the log of build.sh I have this message : When the library is uninstalled a system-wide search does not find any files matching the gmic pattern (except of course the files
zypper confirms me that the installed version is 2.8.1-1.1 |
I reinstalled libgmic1 and libgmic-devel and recompiled darktable.
I uninstalled libgmic1 and libgmic-devel then restarted darktable. darktable doesn't crash anymore and I get the following error messages:
The same one you have on your system. |
So dt finds your library but doesn't like it. Remains to find why. |
Do you know where your gmic library comes from ? Who has built it ? |
@jpverrue - run
and it works just fine. |
And your library libgmic.so is 2.8.1 ? EDIT , sorry I thought answering to @jpverrue .... |
On my side i uninstall the libgmic and libgmic-dev from standard debian and install the last GMIC application (this gives the full app + library, including libgmic library). I don't (and I can't) let both. |
@jpverrue you have the wrong version of libgmic1 installed, 2.7.1-5.1,probably from http://download.opensuse.org/repositories/graphics/openSUSE_Tumbleweed/ the version you need, 2.8.1-1.1, is at http://download.opensuse.org/tumbleweed/repo/oss/ |
@phweyland : I reinstalled libgmic1 and libgmic-devel. I also installed the gmic interpreter. Here is the package information:
I then ran gmic version and I got this:
@ptilopteri : No, I got the right version as you can see. I don't have the
|
Please run the following commands:
and
Attach the dt-symbols.log here |
Here's the result:
There is no result for darktable because I compile it myself. |
This symbol is not in dt-symbols.zip. The closest one I've found is: EDIT: I've run |
Yep, it is a bug in libgmic ... |
Could you share more detail about this ? |
After reading https://discuss.pixls.us/t/gmic-lookup-symbol-err-on-opensuse-darktable-master-build/15827/8, I feel like I made quite a mess, don't you? |
This issue did not get any activity in the past 30 days and will be closed in 7 days if no update occurs. Please check if the master branch has fixed it since then. |
@phweyland
Describe the bug
I just installed the gmic library needed for the new 3D lut module, then I recompiled it without any problem. But since then, darktable crashes whenever I try to do anything. More precisely, I can launch darktable without any problem, the LT interface is displayed, I can open and close modules, scroll in my pictures, but as soon as I try to go to DR, zoom an image (W), launch an export and "à priori" any action (I haven't tested everything), darktable crashes with the following error message :
Platform (please complete the following information):
Additional context
Packages loaded
I removed the packages and recompiled. darktable is working again without any problem.
The text was updated successfully, but these errors were encountered: