Summary: | Digikam fails to start | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | pmanousis <pmanousis> |
Component: | Setup-Templates | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, caulier.gilles, gilant |
Priority: | NOR | ||
Version: | 1.5.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.3.0 | |
Sentry Crash Report: |
Description
pmanousis
2010-12-21 11:37:32 UTC
There might be some libs/files mismatch in your instalation after your libs upgrade. Please try to reinstall digiKam or try to update to today released digiKam 1.7.0 and report back. Thanks! I reinstalled digiKam as you told me but the error remains. Also I tried to compile digiKam 1.7 from sourceforge (http://sourceforge.net/projects/digikam/files/digikam/) but it seems that I can not: I ran this: "cmake -Wno-dev -DCMAKE_INSTALL_PREFIX=/usr/bin .", and got this: "Re-run cmake no build system arguments CMake Error at /usr/share/cmake/Modules/FindKDE4.cmake:98 (MESSAGE): ERROR: cmake/modules/FindKDE4Internal.cmake not found in /home/pit/.kde4/share/apps;/usr/share/kde4/apps;/etc/kde4/share/apps Call Stack (most recent call first): CMakeLists.txt:129 (FIND_PACKAGE) -- Configuring incomplete, errors occurred!" My cmake is: "cmake version 2.8.1" and the modules I have are: "FindBTCore.cmake FindCLucene.cmake FindSLP.cmake". I can not find the wanted module: "FindKDE4Internal.cmake" in yast (openSuse). :( Please try to follow this guide when compiling digiKam (sorry for not posting this earlier :) - http://www.digikam.org/drupal/download?q=download/tarball You should run in no problems at all when compiling by this guide. Also, don't forget to first uninstall your current digiKam package before compiling your own version! [Comment from a bug triager] This seems to be related to bug 246666 and bug 243107 (Read https://bugs.kde.org/show_bug.cgi?id=243107#c12) Regards Solved by the solution given in bug 243107! Thank you guys. *** This bug has been marked as a duplicate of bug 243107 *** *** Bug 267742 has been marked as a duplicate of this bug. *** Fixed with bug #243107 |