| Summary: | 5.6.0-pre pkg does not detect filesystem changes | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jens <jens-bugs.kde.org> |
| Component: | Bundle-MacOS | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 5.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | 6.1.0 | |
| Sentry Crash Report: | |||
|
Description
Jens
2017-06-01 17:41:11 UTC
I cannot reproduce the dysfunction on my Macbook pro 2012 with last Sierra 10.12.5 Did you already seen this dysfunction with older digiKam versions ? In last 5.6.0 PKG, nothing has changed. Same Qt version is used (5.7.1) and we use Qt to handle file changes notifications. The PKG has KF5 update, Exiv2, and QtAV. It will help to see want DK print as debug statements in the console at run time while disk changes. To run it from a console, look the "Freezes and Other Issues" section here : https://www.digikam.org/contribute/ Gilles Caulier I am still using 10.11, not Sierra. Haven't had a compelling reason to upgrade yet. Do you think that makes a difference? Well, i don't know. Apple is not very verbose about the fixes done in core MacOS. But certainly something have been fixed... Gilles Caulier A new fresh 5.8.0 pre-release PKG installer for MacOS was just rebuild for testing and is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please confirm if the problem remains with this version. Thanks in advance Gilles Caulier Jens, Can you reproduce the dysfunction with my last 6.0.0-beta1 bundle that i just rebuild today : https://files.kde.org/digikam/digiKam-6.0.0-beta1-20180821T182536-MacOS-x86-64.pkg.mirrorlist Thanks in advance Gilles Caulier This seems to work now. I tested a few things (adding files, removing files, adding, renaming, removing directories) and the changes were detected whenever Digikam came into focus again - or even a few seconds after the modification. Thanks! 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/ |