| Summary: | Database synchronisation segfaulted, albums disappeared | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Georg Greve <greve> |
| Component: | Database-Albums | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | caulier.gilles, modax |
| Priority: | NOR | ||
| Version: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.10.0 | |
| Sentry Crash Report: | |||
Georg, We are in 0.10.0-beta6 now. There is a huge list of fixed bugs since beta2. Please try again using this last beta. Thanks in advance Gilles Caulier I wish I could. Unfortunately, digikam does not easily compile on Debian sid/experimental, there are some dependency issues that seem non-trivial to resolve. I sent an email to Debian - if anyone can point me to a packaged version somewhere, I'll gladly give it a try. On #digikam irc channel, there are Debian users if you want help. Gilles Caulier Georg, digiKam 0.10.0-beta7 is out, with more than 120 bug reports fixed since beta6. Please, please, please, try again with this version... Gilles Caulier Dear Gilles, Thanks a lot for the update and for your work. I really wish I could give it a try, unfortunately Debian experimental is stuck on 2:0.10.0~beta2 and compiling by hand quickly seems to end in dependency hell. So until someone updates the digikam package in Debian, there is very little I can do unless someone can give me a hint about an up to date Debian package that I can install. Best regards, Georg Georg, as far as I know, it is not possible to upgrade digikam in experimental. You have to upgrade to KDE 4.2 prerelease packages if you want to test newer digikam. Modestas, the newest version of KDE I can find in any Debian repository is 4.1.3. Is there a repository that I am missing? Building all of KDE on my laptop is a bit beyond what I can do right now. I dont see much sense in investigating this bug which occurred with beta2 any more. We have pretty good beta testing coverage since then (and released six more beta versions). Suggest for closing in two weeks unless new information comes up. Following Marcel, suggestions from #8, I close this file now. Note: digiKam 0.10.0-rc1 is out. Gilles Caulier |
Version: 2:0.10.0~beta2-1 (using KDE 4.1.3) OS: Linux Installed from: Debian testing/unstable Packages I have a fairly large number of pictures, which I had begun cataloging with digikam. At some point I wanted to make sure that changes were not lost and selected "Synchronise images with database" at which point digikam segfaulted. After a restart, digikam no longer shows any albums in the album selection although in the settings dialogue it still lists the correct path as root for the collection. Update, rescan & co have no effect: No albums, no pictures. When trying another "Synchronise images with database" I get occasional segfaults - the dump of which is attached below. I'd hate to lose all the tagging that was done, so I'll stop fiddling now. If you need more information, please let me know. Application: digiKam (digikam), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb4bfb6c0 (LWP 21555)] [New Thread 0xabc26b90 (LWP 21568)] [New Thread 0xac4a4b90 (LWP 21567)] [New Thread 0xacd42b90 (LWP 21566)] [New Thread 0xad543b90 (LWP 21565)] [New Thread 0xae14fb90 (LWP 21564)] [New Thread 0xaeb51b90 (LWP 21562)] [New Thread 0xaf3f5b90 (LWP 21561)] [New Thread 0xb2a4cb90 (LWP 21560)] [New Thread 0xb224bb90 (LWP 21559)] [New Thread 0xb357ab90 (LWP 21556)] [KCrash handler] #6 Digikam::Album::title (this=0xb22bd18) at /usr/include/qt4/QtCore/qatomic_i386.h:122 #7 0x082158ad in Digikam::AlbumHistory::getBackwardHistory (this=0xd3e8f68, list=@0xbfdfd8f8) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~beta2/digikam/albumhistory.cpp:233 #8 0x082463be in Digikam::DigikamApp::slotAboutToShowBackwardMenu ( this=0x99031a0) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~beta2/digikam/digikamapp.cpp:1102 #9 0x0825e76d in Digikam::DigikamApp::qt_metacall (this=0x99031a0, _c=QMetaObject::InvokeMetaMethod, _id=22, _a=0xbfdfd9b8) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~beta2/obj-i486-linux-gnu/digikam/digikamapp.moc:191 #10 0xb6133bd0 in QMetaObject::activate (sender=0xd493778, from_signal_index=27, to_signal_index=27, argv=0x0) at kernel/qobject.cpp:3031 #11 0xb6134952 in QMetaObject::activate (sender=0xd493778, m=0x83573d8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101 #12 0xb6889577 in QMenu::aboutToShow (this=0xd493778) at .moc/release-shared/moc_qmenu.cpp:143 #13 0xb688e0f6 in QMenu::popup (this=0xd493778, p=@0xbfdfdbc8, atAction=0x0) at widgets/qmenu.cpp:1735 #14 0xb688f0e5 in QMenu::internalDelayedPopup (this=0xb1b5ae0) at widgets/qmenu.cpp:2855 #15 0xb6893c71 in QMenu::timerEvent (this=0xb1b5ae0, e=0xbfdfe1bc) at widgets/qmenu.cpp:2696 #16 0xb612e6af in QObject::event (this=0xb1b5ae0, e=0xbfdfe1bc) at kernel/qobject.cpp:1120 #17 0xb6514e64 in QWidget::event (this=0xb1b5ae0, event=0xbfdfe1bc) at kernel/qwidget.cpp:7551 #18 0xb6893f79 in QMenu::event (this=0xb1b5ae0, e=0xbfdfe1bc) at widgets/qmenu.cpp:2265 #19 0xb64bd79c in QApplicationPrivate::notify_helper (this=0x9836f80, receiver=0xb1b5ae0, e=0xbfdfe1bc) at kernel/qapplication.cpp:3803 #20 0xb64c56ea in QApplication::notify (this=0xbfdfe47c, receiver=0xb1b5ae0, e=0xbfdfe1bc) at kernel/qapplication.cpp:3768 #21 0xb71e807d in KApplication::notify (this=0xbfdfe47c, receiver=0xb1b5ae0, event=0xbfdfe1bc) at /tmp/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311 #22 0xb611f0d1 in QCoreApplication::notifyInternal (this=0xbfdfe47c, receiver=0xb1b5ae0, event=0xbfdfe1bc) at kernel/qcoreapplication.cpp:587 #23 0xb614d031 in QTimerInfoList::activateTimers (this=0x983a0c4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #24 0xb6149680 in timerSourceDispatch (source=0x983a090) at kernel/qeventdispatcher_glib.cpp:160 #25 0xb5242398 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0xb5245a33 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x09838d10 in ?? () #28 0x00000000 in ?? () #0 0xb7fe4424 in __kernel_vsyscall ()