Summary: | Digikam crashes at launch | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | mike_fowler |
Component: | Setup-Templates | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, hojendiz, mike_fowler |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.3.0 | |
Sentry Crash Report: |
Description
mike_fowler
2010-08-04 02:48:52 UTC
Probably a binary incompatibility. Please try to complete reinstall digikam. *** This bug has been marked as a duplicate of bug 243107 *** Did that: "System is a relatively fresh and clean install; Digikam failed from the get-go, so removed and re-installed Digikam and related packages with no change." Also, 246666 is not a duplicate, thanks. This bug (243107) refers to a crash when opening preferences. 246666 refers to a crash when launching Digikam...not sure how that makes it a duplicate. The backtraces look very similar in the end. But if reinstalling doesn't help we need to further investigate. It's a duplicate. The problem is in Qt4 library : #9 setValidator (p=<value optimized out>, this=<value optimized out>) at ../../src/gui/widgets/qlinecontrol_p.h:641 #10 QLineEdit::setValidator (p=<value optimized out>, this=<value optimized out>) at widgets/qlineedit.cpp:589 #11 0x0838eccb in Digikam::SubjectEdit::SubjectEdit (this=0x88085a0, parent=0x0) at /usr/src/debug/digikam-1.3.0/libs/template/subjectedit.cpp:80 #12 0x0838d763 in Digikam::TemplatePanel::TemplatePanel (this=0x865be00, parent=0x0) at /usr/src/debug/digikam-1.3.0/libs/template/templatepanel.cpp:419 #13 0x080f80a8 in Digikam::SetupTemplate::SetupTemplate (this=0x8640f20, parent=0x0) at I remember a lots of memory corruption with QLineEdit using Valgrind with and older release. Now after and update all disappear Gilles Caulier *** This bug has been marked as a duplicate of bug 243107 *** *** Bug 251403 has been marked as a duplicate of this bug. *** YAY!!!! zypper dup fixed it! Thanks to radlpix@goldmail.de, I tried this after reading about it at bug 243107. Fixed with bug #243107 |