https://bugs.kde.org/show_bug.cgi?id=382013
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||7.5.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=382013
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #11 from caulier.gil...@gmail.com ---
Rjvb,
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 bug
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #10 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=382013
--- Comment #9 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.
Thanks in advance
Gilles
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #8 from caulier.gil...@gmail.com ---
Hi,
Can you check if this problem still exist with last weekly bundle build of
digiKam 7.0.0 available here:
https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #7 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just
released ?
https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #6 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle
available here :
https://files.kde.org/digikam/
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=382013
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|setup |Setup-Collections
--
You are
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #5 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:
https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
Problem still reproducible ?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=382013
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|general |setup
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #4 from RJVB ---
Not that it's the issue at hand (the backtrace comes from Linux) but I don't do
anything to disable dbus in my `port:kf5-digikam` and I have yet to run into
issues. Mind you, I have never tried to use
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #3 from caulier.gil...@gmail.com ---
No. under OSX, this never work properly. Under Windows, it just the hell.
This is why for non Linux, DBUS must be disabled with digiKam. This is what i
do for Windows + OSX bundle.
Gilles Caulier
--
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #2 from RJVB ---
Yes, I reported this mostly for reference. It actually crashes in libc as far
as I can tell. I don't think it's a bug in digiKam but the a crash like this
could also be due to improper usage in Qt.
https://bugs.kde.org/show_bug.cgi?id=382013
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
15 matches
Mail list logo