| Summary: | Digikam Crashes When Trying to Start | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Clifton Hodges <cliftonhodges> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bruno.kiste, caulier.gilles, eb3682, gatschhupfer, kay.muras, ralphdewitt |
| Priority: | NOR | ||
| Version: | 3.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Clifton Hodges
2013-06-19 19:17:02 UTC
*** Bug 322556 has been marked as a duplicate of this bug. *** *** Bug 324183 has been marked as a duplicate of this bug. *** *** Bug 324350 has been marked as a duplicate of this bug. *** The seg fault that I have experienced in bug 324350 was on a fresh NetrunnerOS version 13.06 install (hard drive totally reformatted and data only recovered from backup, no .kde files were restored) my digikam database was verified uncorrupt using sqlite version 3. My digikam database is at version 4. The installed version of Digikam is 3.3.0, KDE is version 4.11.1 all installed from official repositories. Digikam 3.3.0 is at database version 6. My photo's go back to the 1960's and the tagging is unrecoverable due to poor memory. I desperately need a upgrade solution to my problem. Created attachment 82515 [details]
New crash information added by DrKonqi
digikam (3.2.0) on KDE Platform 4.10.5 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:I launched digikam, no other application was running
-- Backtrace (Reduced):
#5 0x00007f2e33e17109 in QReadWriteLock::lockForWrite() () from /usr/lib64/libQtCore.so.4
#6 0x00007f2e35b9f154 in Digikam::CollectionScanner::scanFileNormal(QFileInfo const&, Digikam::ItemScanInfo const&) () from /usr/lib64/libdigikamdatabase.so.3
#7 0x00007f2e35ba1b29 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) () from /usr/lib64/libdigikamdatabase.so.3
#8 0x00007f2e35ba1a22 in Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) () from /usr/lib64/libdigikamdatabase.so.3
#9 0x00007f2e35ba253b in Digikam::CollectionScanner::scanAlbumRoot(Digikam::CollectionLocation const&) () from /usr/lib64/libdigikamdatabase.so.3
digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier Hello Gilles,
it seems that version 3.5.0 does work, at least it did not mcrash and
the tags of saved in digikam3.db were converted to digikam4.db correctly
as far as I could see.
Thank you,
Matthias
Am Donnerstag, den 31.10.2013, 07:52 +0000 schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=321403
>
> --- Comment #6 from Gilles Caulier <caulier.gilles@gmail.com> ---
> digiKam 3.5.0 is out.
>
> Can you give a fresh feedback about your report ? Crash still reproducible ?
>
> Thanks in advance
>
> Gilles Caulier
>
*** Bug 334337 has been marked as a duplicate of this bug. *** |