| Summary: | digikam crashed when scanned for new images | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Tamas KOOS <tamas> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | caulier.gilles, languitar, montosh.bisht, msp, sam.chola+kdebugs, tamas |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 8.0.0 | |
| Sentry Crash Report: | |||
This entry is invalid. Use 1.0.0 final release published few day ago. note: A report like this have been already seen there. Gilles Caulier Well, dear Gilles... I have spent about an hour to make this report useful. Installed packages, and wrote all I could. I find this comment you wrote very unfriendly and it makes me ask myself: should I ever try to send a crash report again? Please, explain to me, why is this report invalid, what is 1.0.0 final release I am supposed to use and how could I set back the little images I used to have for all folders on the left bar. And... I would be glad to make useful and valid reports in case of crash. As I am rather new in this reporting system... some more friendly welcome and support would do good to me. It is our common interest, I think, to have good programs what would not crash... so, what about being friendly and nice to each other? And... again: what may I do to assist better the developpers? Thanks. Have an excellent holiday season... and a happy 2010. Tamas It's not quite your fault, especially if you're unexperienced, but Ubuntu's. We have received dozens of bug reports, for one special crash almost 100 duplicate reports, for the beta5 version which is unstable and old. And that is only because Ubuntu chose to package the explicitly unstable and experimental version beta5 in its stable release. Please understand that we cannot spend time fixing bugs that have likely been fixed months ago. The stable version 1.0 has been released a few days ago. We strongly recommend to use that version and not beta5. Thanks, Marcel. Of course, I had no idea about all that... So, I am using an old version... and there is now a better, a stable one available. GREAT! Now... I would like to install the new version, the 1.0.0. I went to the page: http://www.digikam.org/drupal/download ... and at the Ubuntu package there is only the same "old" beta... How can the new version be activated easily (so, in a way what even I can follow and do... )?? The tarball description seems to be... rather complicated, isn't it? Is there a way from within DigiKam to upgrade? Or version check? Or... anything easy? Thanks a lot... and I am sorry I had sent the same report what many others had sent already before me... without knowing about it. Friendly greetings, Tamas Well, I have started to follwo the description... downloaded...
and here I am with this error:
light@mind:~/from-the-net/DigiKam/digikam-1.0.0/building$ cmake -DCMAKE_BUILD_TYPE=relwithdebinfo -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..
-- The C compiler identification is GNU
-- The CXX compiler identification is unknown
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found. Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
CMake Error at /usr/share/cmake-2.6/Modules/FindKDE4.cmake:84 (MESSAGE):
ERROR: cmake/modules/FindKDE4Internal.cmake not found in
/home/light/.kde/share/apps;/usr/share/kde4/apps
Call Stack (most recent call first):
CMakeLists.txt:56 (FIND_PACKAGE)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.6)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
light@mind:~/from-the-net/DigiKam/digikam-1.0.0/building$
(I had to install cmake, as I did not have it on my computer...)
So, how may I continue??
Thanks,
Tamas
I think you need to install build-essentials on ubuntu and another bunch of other packages ending with -dev. But after you have installed build-essentials you should get a better error message from cmake. And please read README file to see all depencies... Gilles Caulier Tamas, You can find the released version (1.0.0) available for ubuntu here: http://packages.ubuntu.com/lucid/digikam Mark Hi Mark, THANKS a lot!!! Great! However, when I download... Package Installer says with red: Error: Breaks existing package 'showfoto' dependency digikam (= 2:1.0.0~beta5-1ubuntu1) WHAT TO DO WITH THIS??? Thanks Johannes and Gilles, too... If possible, I would like to install with the installer... Greetings, Tamas Tamas, If you do not wish to upgrade to lucid, then you must install required packages individually or you could upgrade to the karmic-backports listed above. But that the karmic-backports only has RC, not 1.0.0 final available. Mark Thanks, Mark being with me... Well I went to the page you gave to me: http://packages.ubuntu.com/lucid/digikam and at the bottom I found this: Download digikam Download for all available architectures Architecture Package Size Installed Size Files amd64 7,580.0 kB 31760 kB [list of files] i386 7,596.0 kB 31392 kB [list of files] So, I went for the i386... what gave me the error code. Sorry, I have no idea what this means: "If you do not wish to upgrade to lucid"... What is lucid? And why would not I want to? I just followd the link you gave to me... and got an error code... May be on the page you gave me... I should download from somewhere else???? I find it rather complicated to get the new version of DigiKam... Is it only me? Or it is really complex and complicated? Or I just got used to simple installation with Ubuntu??? Anyhow... thanks again for all your help (you and all others, too... ) And I hope... it will work soon. (As I am a photographer ... I would love to work with the newest ans stable version...) Greetings Tamas Oh, I found it... The Lucid Lynx... the new version coming out in April 2010... :-) I would gladly use DigiKam from there! Tamas, Ubuntu ships with different versions of digikam at different times: http://packages.debian.org/digikam Unfortunately karmic (oct 09) was released with digikam 1.0.0-beta5 which has some serious issues and should of never been released by the Ubuntu team. TO make matters even worse, the crash was fixed shortly by the digikam team as 1.0.0-beta6, but the ubuntu team didn't upgrade and thus there are thousands of ubuntu karmic users who have the broken digikam 1.0.0-beta5 installed . Ubuntu have made a release of digikam 1.0.0-rc (release candidate) available via karmic-backports, which you could install on your system, but I wouldn't recommend that as there were fixes made between 1.0.0-rc and 1.0.0 final. Unfortunately ubuntu have only released digikam 1.0.0 in the lucid release/. As you have encountered there are some dependencies, such as showfoto which must be kept in sync. So I would recommend you also obtain the showfoto .deb for lucid and then install both packages. http://packages.ubuntu.com/showfoto As well as any other packages that are needed.. Personally I don't recommend ubuntu, I'm debian myself. Hello Mark, Thanks for the answer, again and again. I am lost... It seems to me that there is a tention between DigiKam and Ubuntu or between Debian and Ubuntu... what is... for me, rather sad. In the world of OpenSource software... would be so nice to do things together... without ... well... better to say: with respect and care. I am satisfied with Ubuntu. It works fine for me. Of course, I came from Windows... and I am very-very happy for the change from the MS world to the OpenSource world. Should I change to Debian? Why not... it is possible... however, today I live with ubuntu... and it seems to me a very powerful and friendly thing. It seems, that I still cannot install the stable version of DigiKam. How do other simple users do it? I have no idea... I downloaded showfoto, as you indicted... and I got the same red error message... Should I install both of them, even, if they have this red error messages? Will they be "happy" to find eachother afterwards? I do not dear to do to much, as I am still using the program... and, as a photographer... I need it to work with my thousands of images (ten or even hundred thousand of them). All help is welcome... Thnaks and greetings, Tamas On Monday 28 December 2009 20:24:19 Tamas KOOS wrote:
> It seems, that I still cannot install the stable version of DigiKam. How do
> other simple users do it? I have no idea...
>
> I downloaded showfoto, as you indicted... and I got the same red error
> message...
>
> Should I install both of them, even, if they have this red error messages?
> Will they be "happy" to find eachother afterwards?
>
Yes I would install them both.
If it doesn't work out for your then you can go back to the old version.
Mark
Greetings! Thanks to all of you... At the Ubuntu forum I have got an easy solution from Philip ------ If you still use 9.10/Karmic and want to use the latest Digikam 1.0.0 (and kipi-plugins 1.0) then you could grab the packages from my repo: https://launchpad.net/~philip5/+archive/extra --------- You may read the story here: http://ubuntuforums.org/showthread.php?p=8616351#post8616351 And it WORKS fine! Good luck to all! I hope it is useful... Tamas *** Bug 250418 has been marked as a duplicate of this bug. *** *** Bug 285665 has been marked as a duplicate of this bug. *** |
Application that crashed: digikam Version of the application: 1.0.0-beta5 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: When I started digikam, it was searching for new images, I think... and crashed. I use the database from the prvious Kubuntu installation, however, I have already a new Ubuntu. Thanks. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0xb77bb700 (LWP 3126))] Thread 7 (Thread 0xb40c4b70 (LWP 3134)): #0 0x00eeae06 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0x01a2fbf3 in QTimerInfoList::getTime (this=0x8c06acc, t=...) at kernel/qeventdispatcher_unix.cpp:339 #2 0x01a2fde1 in QTimerInfoList::updateCurrentTime (this=0x8c06acc) at kernel/qeventdispatcher_unix.cpp:297 #3 0x01a3088c in QTimerInfoList::timerWait (this=0x8c06acc, tm=...) at kernel/qeventdispatcher_unix.cpp:420 #4 0x01a2e210 in timerSourcePrepare (source=0x8c06a98, timeout=0xb40c413c) at kernel/qeventdispatcher_glib.cpp:141 #5 0x03210f90 in g_main_context_prepare () from /lib/libglib-2.0.so.0 #6 0x03211351 in ?? () from /lib/libglib-2.0.so.0 #7 0x03211863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #8 0x01a2e067 in QEventDispatcherGlib::processEvents (this=0x8c069a8, flags=...) at kernel/qeventdispatcher_glib.cpp:329 #9 0x01a01c79 in QEventLoop::processEvents (this=0xb40c4304, flags=) at kernel/qeventloop.cpp:149 #10 0x01a020ca in QEventLoop::exec (this=0xb40c4304, flags=...) at kernel/qeventloop.cpp:201 #11 0x0190fb73 in QThread::exec (this=0x8c05e40) at thread/qthread.cpp:487 #12 0x01912e32 in QThreadPrivate::start (arg=0x8c05e40) at thread/qthread_unix.cpp:188 #13 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #14 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 6 (Thread 0xb38c3b70 (LWP 3135)): #0 0x01cc2920 in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6 #1 0x03210d0c in g_main_context_check () from /lib/libglib-2.0.so.0 #2 0x0321147c in ?? () from /lib/libglib-2.0.so.0 #3 0x03211863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #4 0x01a2e067 in QEventDispatcherGlib::processEvents (this=0x8cb1a58, flags=...) at kernel/qeventdispatcher_glib.cpp:329 #5 0x01a01c79 in QEventLoop::processEvents (this=0xb38c3304, flags=) at kernel/qeventloop.cpp:149 #6 0x01a020ca in QEventLoop::exec (this=0xb38c3304, flags=...) at kernel/qeventloop.cpp:201 #7 0x0190fb73 in QThread::exec (this=0x8bf9740) at thread/qthread.cpp:487 #8 0x01912e32 in QThreadPrivate::start (arg=0x8bf9740) at thread/qthread_unix.cpp:188 #9 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #10 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 5 (Thread 0xb0c3eb70 (LWP 3148)): #0 0x002cd422 in __kernel_vsyscall () #1 0x00f54142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x01cc27e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6 #3 0x037979ff in ?? () from /usr/lib/libxine.so.1 #4 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 4 (Thread 0xaf831b70 (LWP 3152)): #0 0x00f51d54 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 #1 0x01cc2956 in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6 #2 0x0320f712 in g_main_context_release () from /lib/libglib-2.0.so.0 #3 0x03211491 in ?? () from /lib/libglib-2.0.so.0 #4 0x03211863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x01a2e067 in QEventDispatcherGlib::processEvents (this=0x8a0b408, flags=...) at kernel/qeventdispatcher_glib.cpp:329 #6 0x01a01c79 in QEventLoop::processEvents (this=0xaf8312b4, flags=) at kernel/qeventloop.cpp:149 #7 0x01a020ca in QEventLoop::exec (this=0xaf8312b4, flags=...) at kernel/qeventloop.cpp:201 #8 0x0190fb73 in QThread::exec (this=0x9203358) at thread/qthread.cpp:487 #9 0x06dbd20a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so #10 0x01912e32 in QThreadPrivate::start (arg=0x9203358) at thread/qthread_unix.cpp:188 #11 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 3 (Thread 0xa7dfeb70 (LWP 3173)): #0 0x002cd422 in __kernel_vsyscall () #1 0x00f53e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x01cc278d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0x01913e67 in QWaitConditionPrivate::wait (this=0x965f8c0, mutex=0x965f8bc, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0x965f8c0, mutex=0x965f8bc, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0x024fabfa in Digikam::LoadSaveThread::run (this=0x965f8b0) at /build/buildd/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136 #6 0x01912e32 in QThreadPrivate::start (arg=0x965f8b0) at thread/qthread_unix.cpp:188 #7 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #8 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xa71ffb70 (LWP 3181)): #0 0x002cd422 in __kernel_vsyscall () #1 0x00f53e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x01cc278d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0x01913e67 in QWaitConditionPrivate::wait (this=0xa552280, mutex=0xa55227c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0xa552280, mutex=0xa55227c, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0x024fabfa in Digikam::LoadSaveThread::run (this=0xa552270) at /build/buildd/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136 #6 0x01912e32 in QThreadPrivate::start (arg=0xa552270) at thread/qthread_unix.cpp:188 #7 0x00f4f80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #8 0x01cb57ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb77bb700 (LWP 3126)): [KCrash Handler] #6 0x082b1e8d in Digikam::DigikamView::refreshView (this=0x8bd9230) at /build/buildd/digikam-1.0.0~beta5/digikam/digikamview.cpp:309 #7 0x0828eaa0 in Digikam::DigikamApp::slotDatabaseRescan (this=0x8bd18f0) at /build/buildd/digikam-1.0.0~beta5/digikam/digikamapp.cpp:2504 #8 0x082abf4d in Digikam::DigikamApp::qt_metacall (this=0x8bd18f0, _c=QMetaObject::InvokeMetaMethod, _id=120, _a=0xbf9e49d8) at /build/buildd/digikam-1.0.0~beta5/obj-i486-linux-gnu/digikam/digikamapp.moc:228 #9 0x01a19263 in QMetaObject::activate (sender=0xb0ca0a8, from_signal_index=5, to_signal_index=6, argv=0xbf9e49d8) at kernel/qobject.cpp:3113 #10 0x01a196d8 in QMetaObject::activate (sender=0xb0ca0a8, m=0x849dac8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbf9e49d8) at kernel/qobject.cpp:3207 #11 0x028119b1 in QAction::triggered (this=0xb0ca0a8, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #12 0x02812f32 in QAction::activate (this=0xb0ca0a8, event=QAction::Trigger) at kernel/qaction.cpp:1160 #13 0x02c609cc in QMenuPrivate::activateCausedStack (this=0xb0d4dc8, causedStack=..., action=0xb0ca0a8, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:967 #14 0x02c6703b in QMenuPrivate::activateAction (this=0xb0d4dc8, action=0xb0ca0a8, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1060 #15 0x02c67bf7 in QMenu::mouseReleaseEvent (this=0xb0f8de8, e=0xbf9e5130) at widgets/qmenu.cpp:2254 #16 0x0209a1c5 in KMenu::mouseReleaseEvent (this=0xb0f8de8, e=0xbf9e5130) at ../../kdeui/widgets/kmenu.cpp:456 #17 0x0286d012 in QWidget::event (this=0xb0f8de8, event=0xbf9e5130) at kernel/qwidget.cpp:7549 #18 0x02c69e34 in QMenu::event (this=0xb0f8de8, e=0xbf9e5130) at widgets/qmenu.cpp:2353 #19 0x02817f54 in QApplicationPrivate::notify_helper (this=0x89b2ad0, receiver=0xb0f8de8, e=0xbf9e5130) at kernel/qapplication.cpp:4056 #20 0x02820033 in QApplication::notify (this=0xbf9e6b2c, receiver=0xb0f8de8, e=0xbf9e5130) at kernel/qapplication.cpp:3758 #21 0x01fafbfa in KApplication::notify (this=0xbf9e6b2c, receiver=0xb0f8de8, event=0xbf9e5130) at ../../kdeui/kernel/kapplication.cpp:302 #22 0x01a036cb in QCoreApplication::notifyInternal (this=0xbf9e6b2c, receiver=0xb0f8de8, event=0xbf9e5130) at kernel/qcoreapplication.cpp:610 #23 0x0281ef6e in QCoreApplication::sendSpontaneousEvent (receiver=0xb0f8de8, event=0xbf9e5130, alienWidget=0x0, nativeWidget=0xb0f8de8, buttonDown=0x3092aa0, lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #24 QApplicationPrivate::sendMouseEvent (receiver=0xb0f8de8, event=0xbf9e5130, alienWidget=0x0, nativeWidget=0xb0f8de8, buttonDown=0x3092aa0, lastMouseReceiver=...) at kernel/qapplication.cpp:2924 #25 0x0288dc87 in QETWidget::translateMouseEvent (this=0xb0f8de8, event=0xbf9e677c) at kernel/qapplication_x11.cpp:4343 #26 0x0288cc4b in QApplication::x11ProcessEvent (this=0xbf9e6b2c, event=0xbf9e677c) at kernel/qapplication_x11.cpp:3428 #27 0x028b9502 in x11EventSourceDispatch (s=0x89b5d00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #28 0x0320de88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x03211730 in ?? () from /lib/libglib-2.0.so.0 #30 0x03211863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x01a2e02c in QEventDispatcherGlib::processEvents (this=0x898ce80, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #32 0x028b8be5 in QGuiEventDispatcherGlib::processEvents (this=0x898ce80, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #33 0x01a01c79 in QEventLoop::processEvents (this=0xbf9e6a74, flags=) at kernel/qeventloop.cpp:149 #34 0x01a020ca in QEventLoop::exec (this=0xbf9e6a74, flags=...) at kernel/qeventloop.cpp:201 #35 0x01a0453f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #36 0x02817dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #37 0x083a4da3 in main (argc=5, argv=0xbf9e6f84) at /build/buildd/digikam-1.0.0~beta5/digikam/main.cpp:186 Reported using DrKonqi