Summary: | Digikam crashes, related with the rename of several photographs | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Thomas Vergnaud <thomas.vergnaud> |
Component: | AdvancedRename-engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andi.clemens, auvielee, caulier.gilles |
Priority: | NOR | ||
Version: | 1.4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.2.0 | |
Sentry Crash Report: |
Description
Thomas Vergnaud
2010-11-27 09:34:20 UTC
Andi, Another entry about the famous crash in Advance Rename tool I'm so suprized to see bugzilla proposal around entries which are not relally relevant of digiKam... What's the common point to link these entries ? Gilles Caulier Thomas, Can you test with digiKam 1.6.0 out recently ? Thanks in advance Gilles Caulier I just installed Digikam 1.6.0 from the tarball, and I get exactly the same crash. It seems to be x64 and Ubuntu / OpenSUSE related, all reports had either this architecture or this distribution. I can not fix this because I have no crash, regardless of what I'm doing here. I guess these distributions ship a broken Qt installation. By looking at the source code I can not find any suspicious code, the lines mentioned in the backtraces have not been changed in months and worked before for everyone. I really guess it is Qt's fault, I can not debug this. Andi I just renamed 30.000 images in my test-collection (it took a while :-)), no crash. Dear all, I get the crash only since I updated Ubuntu to Maverick. When I was using Lucid 64 bits (which shipped digikam 1.2.0), everything was fine. I just made a test with a 32 bits Kubuntu Maverick running in a virtual box (so, same configuration as mine, but 32 bits). There is no crash. Andi, as you say, the problem seems to be related to the 64 bit implementation of something in Maverick. I think we should redirect Thomas (and the rest) to report a bug against their distro with Qt component as there's nothing we can do about it. *** This bug has been marked as a duplicate of bug 237642 *** *** Bug 260594 has been marked as a duplicate of this bug. *** Fixed with #237642 |