| Summary: | digikam editor crash | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Knut Hansen <knut.tr> |
| Component: | Plugin-Editor-Balance | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.7.0 | |
| Sentry Crash Report: | |||
| Attachments: | attachment-19163-0.html | ||
|
Description
Knut Hansen
2017-03-12 11:36:36 UTC
No idea why it crash here. It can be a broken binary compatibility with OpenSuse RPM. The backtrace said about SSE3 assembly instructions located in libC. So i recommend to test with 5.5.0 pre release AppImage which work very well here. https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM AppImage do not install something in your computer and can be run in parallel with OpenSuse version. Download file, make it as executable and run it as well. All necessary dependencies to run digiKam are bundle in file. Gilles Caulier new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier digiKam 5.6.0 is now released and available as bundle for Linux, MacOS and Windows. https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier New digiKam 5.7.0 are built with current implementation as pre-release bundles: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Problem still reproducible ? Created attachment 107006 [details] attachment-19163-0.html I apologize for being late in answering this. My original problem was related to handling large files (250 MB+). I installed more memory, originally I had 8 GB, increased to 32 GB. And I have not encountered the problem again. Of course I can not be absolutely sure that this was related to running out of memory, but if it was, maybe digikam should be able to handle that situation more gracefully. Anyways, I am not able to reproduce the problem. Knut 2017-07-23 20:27 GMT+02:00 <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=377517 > > --- Comment #4 from caulier.gilles@gmail.com --- > New digiKam 5.7.0 are built with current implementation as pre-release > bundles: > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Problem still reproducible ? > > -- > You are receiving this mail because: > You reported the bug. |