Bug 306821 - When finishing digiKam, program crashes
Summary: When finishing digiKam, program crashes
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 2.8.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-15 08:26 UTC by Axel Krebs
Modified: 2017-08-06 07:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2012-09-15 08:26:30 UTC
when ending digiKam, the program crashes

Reproducible: Always

Steps to Reproduce:
1. every time? I woiuld say, "most of the time"
2.
3.
Actual Results:  
just do and experience!
Comment 1 caulier.gilles 2012-09-15 08:30:45 UTC
We need a GDB backtrace please...

Gilles Caulier
Comment 2 Axel Krebs 2012-09-15 10:48:41 UTC
sorry, was meaningless: "zero star"


Axel

Am 15.09.2012 10:30, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=306821
> 
> Gilles Caulier <caulier.gilles@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>                  CC|                            |caulier.gilles@gmail.com
>          Resolution|---                         |BACKTRACE
> 
> --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> ---
> We need a GDB backtrace please...
> 
> Gilles Caulier
>
Comment 3 caulier.gilles 2015-07-01 06:03:40 UTC
New digiKam 4.11.0 is available :

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

Can you reproduce the problem with this release ?
Comment 4 caulier.gilles 2015-08-21 07:04:53 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.
Comment 5 caulier.gilles 2016-07-14 09:18:01 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