Summary: | digiKam crashes on first run | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Ian Moir <ian> |
Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, cfeck, ian |
Priority: | NOR | Keywords: | drkonqi |
Version: | 3.4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.4.0 | |
Attachments: | New crash information added by DrKonqi |
Description
Ian Moir
2014-01-11 00:03:45 UTC
*** This bug has been marked as a duplicate of bug 310798 *** Created attachment 84580 [details]
New crash information added by DrKonqi
digikam (3.4.0) on KDE Platform 4.11.3 using Qt 4.8.4
- What I was doing when the application crashed:
After experiencing this problem with digiKam 3.2, I installed digiKam 3.4 and discovered the same problem. DigiKam is unuseable since, on opening up, it checks for new items very rapidly to a level of 75%, then proceeds slowly to 84% whereupon it crashes. There appears to be a common factor with most of these crash reports ie: "floating endpoint error" - is this the main problem?
-- Backtrace (Reduced):
#6 0x00007fa498f6c9af in read_dib_body (s=..., bi=..., offset=138, startpos=0, image=...) at image/qbmphandler.cpp:322
#7 0x00007fa498f6d5b1 in QBmpHandler::read (this=0x7fa45c54a0e0, image=0x7fa471f26930) at image/qbmphandler.cpp:770
#8 0x00007fa498f465f4 in QImageReader::read (this=this@entry=0x7fa471f26990, image=image@entry=0x7fa471f26930) at image/qimagereader.cpp:1205
#9 0x00007fa498f46b44 in QImageReader::read (this=this@entry=0x7fa471f26990) at image/qimagereader.cpp:1155
#10 0x00007fa498f3ae4e in QImage::load (this=this@entry=0x7fa471f26ae0, fileName=..., format=format@entry=0x0) at image/qimage.cpp:5094
Ian, did you actually read comment #1 and the link mentioned in it? Fixed with #310798 |