Bug 339319 - digikam crashes at startup
Summary: digikam crashes at startup
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 4.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-23 07:55 UTC by yves bodson
Modified: 2016-07-14 09:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yves bodson 2014-09-23 07:55:18 UTC
After a system update, digikam crashes at startup.  
Application: digikam (4.3.0)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-36-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>
I tried to run digikam but after showing the splash screen it did open the main screen and did crash by itself.

I had reloaded and just tried to run digikam.  No other apps were running other than the systme's.

The crash can be reproduced every time. yes 


-- Backtrace:
A useful backtrace could not be generated
I have tried to install many times the backtrace code but it never  went through..?

Report to https://bugs.kde.org/

Reproducible: Always

Steps to Reproduce:
1.boot
2.login
3.run digikam >> crash
everything else works normally


Expected Results:  
accessing my collections of albums and photos

I think it is because the system update..  maybe wrong
Comment 1 caulier.gilles 2014-09-23 08:01:50 UTC
Run digiKam in gdb to get a backtrace, as explained here :

https://www.digikam.org/contrib

Gilles Caulier
Comment 2 caulier.gilles 2015-06-25 08:56:08 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 3 caulier.gilles 2015-08-17 11:27:36 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier
Comment 4 caulier.gilles 2016-07-14 09:16:27 UTC
With 5.0.0 stable release, this problem is not reproducible.
I close this file now. Don't hesitate to reopen if necessary.
Gilles Caulier