https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #18 from caulier.gil...@gmail.com ---
@Andrea,
digiKam 8.3.0 stable version is released and available at usual place :
https://www.digikam.org/download/
Can you reproduce the dysfunction on your computer ?
Thanks in advance
Gilles
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #17 from caulier.gil...@gmail.com ---
@Andrea,
digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110
frameworks. Installer is available at usual place :
https://files.kde.org/digikam/
Can reproduce the problem with
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #16 from caulier.gil...@gmail.com ---
@Andrea
digiKam 8.0.0 is out. Problem still reproducible ?
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #15 from caulier.gil...@gmail.com ---
Andrea,
Stable digiKam 7.4.0 is published. Please check if problem is reproducible.
https://www.digikam.org/download/
Thanks in advance
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #14 from caulier.gil...@gmail.com ---
digiKam 7.2.0 official release is published with more than 360 files closed
from bugzilla:
https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/
Can you reproduce the dysfunction with
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #13 from caulier.gil...@gmail.com ---
https://bugs.kde.org/show_bug.cgi?id=426938
--- Comment #4 from caulier.gil...@gmail.com ---
Hi,
digiKam 7.2.0-beta2 pre-release PKG installer now support BigSur and is
compiled with last stable Qt
https://bugs.kde.org/show_bug.cgi?id=367853
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #12 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:
https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
We need a fresh feedback on this file using this version.
Best Regards
Gilles
https://bugs.kde.org/show_bug.cgi?id=367853
simon...@gmail.com changed:
What|Removed |Added
CC||simon...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #10 from caulier.gil...@gmail.com ---
Andrea,
Can you reproduce the dysfunction using 6.1.0 pre-release package for MacOSX
available here :
https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #9 from caulier.gil...@gmail.com ---
What's about this file using 5.8.0 pre-release buncle :
https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #8 from caulier.gil...@gmail.com ---
digiKam 5.4.0 pre-release is available in this repository :
https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
Can you test with this version please ?
Gilles Caulier
--
You are
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #7 from Lars Van Casteren ---
I got it up & running with some major trickery using MariaDB 10.1.14 (lots of
manual config stuff & creating mysql. innoDB tables etc before DK would
continue) but in the end I get
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #6 from caulier.gil...@gmail.com ---
2016-08-27 13:50 GMT+02:00 Lars Van Casteren via KDE Bugzilla <
bugzilla_nore...@kde.org>:
> https://bugs.kde.org/show_bug.cgi?id=367853
>
> --- Comment #5 from Lars Van Casteren
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #5 from Lars Van Casteren ---
I think the scanning actually went ok when seeing the console msg output.
The problem seems to appear after the folder scan, or during consequent startup
if you killed it.
This is
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #4 from Andrea ---
Gilles,
thank you very much for the new pre installer. I tried it. Unfortunately, the
problem remains. For the time being a hint like you proposed in the
releasenotes.html, a readme and the FAQ
https://bugs.kde.org/show_bug.cgi?id=367853
Lars Van Casteren changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #2 from caulier.gil...@gmail.com ---
With current implementation we fix some lock with database on special
conditions discovered under Windows. I think this problem can also appears with
MacOS.
So i just build a new pre 5.2.0 installer for
https://bugs.kde.org/show_bug.cgi?id=367853
--- Comment #1 from caulier.gil...@gmail.com ---
Looking on my macbook pro how Apple iPhoto or Photos applications store the
data (image and metadata), it's look like a big mess, with a lots of redondant
subdirectories relies on image, preview,
https://bugs.kde.org/show_bug.cgi?id=367853
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|Digikam hangs on 'Reading |Digikam hangs on 'Reading
20 matches
Mail list logo