| Summary: | digikam crashes on startup | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Hans-Werner Gerke <hans-werner> |
| Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | critical | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.6.0 | |
| Sentry Crash Report: | |||
It crash on OpenCV shared lib, not digiKam. Gilles Caulier Thank you, Mr. Caulier; but what can I do now? Am 19.08.2012 18:01, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=305420 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > CC| |caulier.gilles@gmail.com > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> --- > It crash on OpenCV shared lib, not digiKam. > > Gilles Caulier > Report this problem to your distro packager... Gilles Caulier |
digikam 2.8.0 crashes allways on startup leaving message: "illegal Instruction" Reproducible: Always Steps to Reproduce: 1.open bash 2.type "digikam" 3. Actual Results: message "Ungültiger Maschinenbefehl" Expected Results: start of "digikam" Here the backtrace: #0 0xb46bac3a in cvGetTickFrequency () at /usr/src/debug/OpenCV-2.4.2/modules/core/src/system.cpp:638 #1 0xb42294b2 in __static_initialization_and_destruction_0 (__priority=65535, __initialize_p=1) at /usr/src/debug/OpenCV-2.4.2/modules/legacy/src/blobtrackingauto.cpp:55 #2 _GLOBAL__sub_I_blobtrackingauto.cpp(void) () at /usr/src/debug/OpenCV-2.4.2/modules/legacy/src/blobtrackingauto.cpp:480 #3 0xb430481d in __do_global_ctors_aux () from /usr/lib/libopencv_legacy.so.2.4 #4 0xb42248b1 in _init () from /usr/lib/libopencv_legacy.so.2.4 #5 0xbfffef44 in ?? ()