| Summary: | Digikam 5.0 beta 7 crashes while showing the splash image. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Hans-Peter <hans-ph> |
| Component: | ProgressManager-Splashscreen | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, philip.johnsson |
| Priority: | NOR | ||
| Version: | 5.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
|
Description
Hans-Peter
2016-07-04 18:45:24 UTC
It's not clear why it crash, probably when it try to load a plugin for image editor. It's not reproducible here. I suspect a binary compatibility issue. Also 5.0.0 final will be released in few day. I recommend to test with this final version. Gilles Caulier Thats also what i suspect. I hoped a version build on my system would do better. And an older version (b6) did run. So either some Ubuntu update destroyed things or some cutting-edge lib from the digikam ppa. And i probably also messed up my system when trying to resolve this by deinstalling or reinstalling things. Oh hell, what happened to good old static binaries? Sorry, not the developers fault, but i really love digikam and really would like to have a stable environment. Does digikam.exe run under wine? (joking, partially) HP I never tried windows version under Wine. why not to recompile yourseft the code under Linux ? Gilles Caulier As i wrote in previous messages, i did compile it on my Linux box, no difference to the pre-packed binaries. HP Ok If code is compiled, i recommend to re-install the system from scratch. You can also use a VM to test. I'm 99% sure that core system libraries are broken or something like that. Gilles Caulier Official 5.0.0 is out please update and try again. Gilles Caulier I tried normal update. No success, digikam5 crashes as described initially. I then deinstalled everything from Phillips ppa and most libs with *kf5* or marble. Reinstalled, no difference. I installed old 4.14 again, still works (puuh!). So i give up on trying digikam5 for now and stay with 4.14 (which works mostly nice). Maybe i try again in a month or so. However, if You have ideas for producing more meaningful debug logs, pls. tell me. I think what happens is called the "dependency hell" of libraries. Is this better on FreeBSD? HP Hans-Peter I'm also interested in this bug and crash as if it's a package or build problem with my PPA I want to see if I can fix it. If it's not my packages then the developers sure is interested too. I haven't heard of any users of my PPA that have your problem so my thoughts are that either some package on my PPA have binary incomparability with some external package you have installed on your system or some package on my PPA that is needed is held back from being updated and that give you this crash. Or it's a crash because of code in digikam that need to be fixed. Make a full backtrace from when you start digikam 5 and post it here so we can have a look at it. How to make backtrace can be found here: https://www.digikam.org/contrib /Philip Philip, i also think its a problem with package dependencies. DK 5. beta 6 from your repo did run, happily together with 14.04. Then suddenly it stopped working, and from then on none of the 5.x did work, not even a self compiled version. So my guess is that some Ubuntu library update messed up things. Probably something with exiv2 or with marble. Can it be that some Ubuntu libs meanwhile have newer versions like yours? Regarding backtrace: first bug report has a back trace, but without full debug info. Would full debug packages produce richer output?If so, give me some time, this is a hell of installation. Debug packages seem to be depended on almost everything and are huge. HP Surprise, surprise. I vaguely remembered that someone had problems with the digikamrc file. So i tried again, removed .config/digikamrc (from older beta 6) before. And now digikam5 from Philips ppa starts fine and i can start real testing or even go and make new images :) I think there should be an error message. Happy again. Thanks Philip and Gilles for the patience and support. HP |