Summary: | crashes opening the image editor for raw images (mrw). Embedded editor does not work | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | bogdan |
Component: | Plugin-RawImport-Native | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | big-nikita, marcel.wiesweg |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.10.0 | |
Sentry Crash Report: |
Description
bogdan
2008-11-14 04:42:16 UTC
Thi sis not reproductible here. I work everyday with MRW files and i canot see any crash here. Do you use last code from KDE trunk subversion repository about: - libkdcraw - libkdexiv2 - digikam Gilles Caulier Yes, I followed the instructions on the digikam site. The crash only appeared after I upgraded Kde4 from 4.1.3 to 4.1.73. However,the embedded image did never work for me for neither of JPG or MRW. Another thing I noticed then wars that the in a slide show the MRW images appear blurry, whereas, the JPG are sharp. I don't experience the bug anymore after I downgraded KDE4 from 4.1.73 (trunk) to 4.1.3 (4.1 branch). and after I took a new svn snapshot from today. However, I had to trick the CMakeLists.txt in the digikam directory because it would not recognize that I have the proper version of libkexiv2. I guess it has something to do with checking the version: IF(NOT WIN32) FIND_PACKAGE(PkgConfig) PKG_CHECK_MODULES(Kexiv2 libkexiv2>=0.5.0) Did you change only kdelibs, or other packages as well? Which version of kdegraphics/libs do you have installed? Maybe there are old versions around? Your configuration problem may indicate a problem in that area. I have only one version of of kdegraphics, the one from SVN. I compiled it and did a make install. I verified that it is the new one installed an no other is laying around. I compiled the graphics directory ( including digikam ), but it complains about the libkexiv2. I had to get around it by forcing cmake to set it to true. It may have something to do that my other libs are from 4.1.3 branch and digikam/kdegraphics code is from the trunk? Given your KDE4 is installed in /usr (like OpenSuse) you should have ldd /usr/bin/digikam | grep kexiv2 libkexiv2.so.7 => /usr/lib/libkexiv2.so.7 (0xb58af000) ldd /usr/bin/digikam | grep kdcraw libkdcraw.so.7 => /usr/lib/libkdcraw.so.7 (0xb57d3000) pkg-config --modversion libkexiv2 0.5.0 ls /usr/lib/libkexiv2.so* /usr/lib/libkexiv2.so /usr/lib/libkexiv2.so.7 /usr/lib/libkexiv2.so.7.2.0 ls /usr/lib/libkdcraw.so* /usr/lib/libkdcraw.so /usr/lib/libkdcraw.so.7 /usr/lib/libkdcraw.so.7.0.0 First of all I have 64 bits OS, whereas you have 32 bits OS. high:/home/bogdan # ldd /usr/bin/digikam | grep kexiv2 libkexiv2.so.7 => /usr/lib64/libkexiv2.so.7 (0x00007f9ac94df000) high:/home/bogdan # ldd /usr/bin/digikam | grep kdcraw libkdcraw.so.7 => /usr/local/lib/libkdcraw.so.7 (0x00007f7c14312000) This is the problem, ==================== high:/home/bogdan # pkg-config --modversion libkexiv2 0.4.0 but I don't understand why it comes beck with 0.4.0 as I have installed the latest. Libs ===== high:/home/bogdan # ls /usr/lib64/libkexiv2.so* /usr/lib64/libkexiv2.so /usr/lib64/libkexiv2.so.7 /usr/lib64/libkexiv2.so.7.2.0 high:/home/bogdan # ls /usr/lib64/libkdcraw.so* /usr/lib64/libkdcraw.so /usr/lib64/libkdcraw.so.7 /usr/lib64/libkdcraw.so.7.0.0 I don't have the 32 bit libraries ================================ ls /usr/lib/libkexiv2.so* ls: cannot access /usr/lib/libkexiv2.so*: No such file or directory I did more research and I fond that the libkexiv2.pc in the source files is correct, but I believe that it is not copied in the /usr/lib64/pkgconfig directory by "make install" where is still 0.4.0 although the timestamp is good. high:/home/software/installed/digikam/kdegraphics/libs/libkexiv2 # cat libkexiv2.pc prefix=/usr exec_prefix=/usr/bin libdir=/usr/lib64 includedir=/usr/include Name: libkexiv2 Description: A C++ library to manipulate EXIF/IPTC/XMP metadata using Exiv2 library. This library is used by digiKam and kipi-plugins. URL: http://www.kipi-plugins.org Requires: Version: 0.5.0 Libs: -L/usr/lib64 -lkexiv2 Cflags: -I/usr/include Even with high:/home/software/installed/digikam/graphics # pkg-config --modversion libkexiv2 0.5.0 I still get the same error: -- libkexiv2 library found............. NO -- CMake Error at digikam/CMakeLists.txt:181 (MESSAGE): digiKam needs libkexiv2 library >= 0.5.0. You need to install libkexiv2 first Did you ever test a 64 bit system, maybe there is a cmake configuration problem related to these systems? Although I can't see how. Remove CMake cache file and try again. Gilles Caulier Removing CMakeCache.txt worked. There is only one problem left, I guess, the libkexiv2.pc is not copied to /usr/lib64/pkgconfig as I had the 0.4.0 and I had to manually copy it. Also the SVN build does not work with the 4.1.3 branch libraries. It crashes when loading plugins, as I stated when filing for this bug. Sound like a broken binary compatibility with another shared libs from kdegraphics, where libkdcraw, libkexiv, and likipi are. Look here for info : http://www.digikam.org/sharedlibs I recommend to checkout theses libs using KDE svn from trunk, compile and install. After that, checkout kipi-plugins and digiKam from trunk, compile it and install. http://www.digikam.org/download/svn#checkout-kde4 Gilles I actually did all that. I have all the KDE4 libs from SuSE's 4.1.3 branch, but the kdegraphics is from SVN Ok let's take a step back. What you describe as broken preview most likely is the infamous splitter bug 173746, and you have to drag the splitter upwards from the lower edge. The other thing is the crash, do you still have the crash? I now became aware that the backtrace you provide is really strange because the same code path is listed three times, as if called recursively. Did you get the trace from the dialog popping up or by running digikam under GDB? The output is from the crash box not from GDB. However, I can not reproduce this anymore since I can not start it since is crashing when loading plugins bug 175844 *** Bug 177396 has been marked as a duplicate of this bug. *** Bug #177396 has exactly the same backtrace and was fixed by Gilles. (More precisely, 177396 was a dup of this, but someone decided it was not) |