Summary: | digiKam crashed while moving pictures | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Max <MaximilianDuffner> |
Component: | Albums-IconView | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | axel.krebs, caulier.gilles, cfeck, raul.malea |
Priority: | NOR | ||
Version: | 1.8.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.0.0 | |
Sentry Crash Report: |
Description
Max
2011-03-05 10:26:53 UTC
We need feedback using a recent version. 2.0.0 RC is out, please test... Thanks in advance Gilles Caulier This crash is caused by Qt not always being able to handle a nested event loop inside a dropEvent handler. To workaround this problem, you need to invoke a deferred method (either using QMetaObject::invokeMethod with Qt::QueuedConnection, or using a singleShot timer call), where the drop KMenu is shown. This also refers to bug 226816 and bug 229900. Is this officially a Qt bug with any chance to get fixed? Or is this somewhere documented as "down open an event loop in drop handler"? Because I dont feel like very much working around platform bugs, with significant and unelegant changes needed here. *** Bug 281322 has been marked as a duplicate of this bug. *** Am 04.09.2011 17:03, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=267686
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |axel.krebs@t-online.de
>
>
>
>
> --- Comment #4 from Gilles Caulier <caulier gilles gmail com> 2011-09-04 15:03:54 ---
> *** Bug 281322 has been marked as a duplicate of this bug. ***
>
I checked this bug, not finding enough fit...
Anyway, thank you for proving!
Coment:
I assume DK has reached some limits from data-organsation: I change the
choosen directories, and DK seems to keep the total database. OK I read
that DK erases dead entries. But how can work with several
databases/directories, next startup with _other_ directories and so on??
I suggest strongly to reduce database extent to metadata per pic. Under
this pre-condition, it could change the choosen directiories anytime
without any limitations.
Besides I had no thumbnail-databate with more than 7 GB(!!) slowing down
each work progress.
Last argument to do pic-based date-management: this would increase the
data-safety enormously: in worst case, there would be "risk" of single
pictures, not on a comlete database.
I beg developers, tho thinks about this suggestion. It is a matter of
data-safety, speeding up, and flexibility.
Maybe you have a best-practise tutoral for similar needs as me?
Last question: where can I get the recommended version 2.1 ("git") from?
It is not in my launchpad-repositories...
Thank you,
Axel
digiKam 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier Max, This file still valid with digiKam 2.4 ? Gilles Caulier Gilles,
For the sake of ease of installation (repository-orgies) I run digikam
2.1 from KUBUNTU-distribution.
Unfortunately, I can you therefore, if this issue applies in DK 2.4 :-(
Thinking about how to contribute better and more efficiently to DK project.
Axel
---
Am 14.12.2011 10:15, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=267686
>
>
>
>
>
> --- Comment #7 from Gilles Caulier <caulier gilles gmail com> 2011-12-14 09:15:02 ---
> Max,
>
> This file still valid with digiKam 2.4 ?
>
> Gilles Caulier
>
Official digiKam 2.6.0 release is out since few days now : http://www.digikam.org/drupal/node/656 Please, check if this entry still valid, or update report accordingly. Thanks in advance. Gilles Caulier digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier We need feedback here using digiKam 3.5.0... Gilles Caulier (In reply to comment #11) > We need feedback here using digiKam 3.5.0... > > Gilles Caulier sorry, I am bound to digiKam v3.4 within 13.10 Is there an easy and reliable way to updat to 3.50? Axel Problem still here with 3.4.0 ? Gilles Caulier New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. With digiKam 5.0.0, this problem is not reproducible. I close this file now. Re-open it if necessary. Gilles Caulier *** Bug 321541 has been marked as a duplicate of this bug. *** |