SUMMARY On macOS Mojave 10.14.5 and 10.14.6 digikam opens the image editor without toolbar on the right side of the window and also the buttons above the image are shown wrongly. Way too big icons and the not full bar is shown. After uninstalling and reinstalling version 6.2.0 everthing works fine again. STEPS TO REPRODUCE 1. Install digikam 6.3.0 on macOS Mojave 10.14 2. open digikam 3. open and image in the image editor OBSERVED RESULT toolbar at the right side of the window missing completelly toolbar above the image not completelly shown and with too big icons. EXPECTED RESULT Imge editor shows toolbar and full toolbar in resonable size above the image SOFTWARE/OS VERSIONS macOS: Mojave 10.14.5 and 10.14.6 ADDITIONAL INFORMATION effect is the same on 15" MacBook pro 2016 as on 27" LG UltraFine 5K display.
*** This bug has been marked as a duplicate of bug 411902 ***
Here you will find the pre-release of digiKam-6.4.0 where the problem has been fixed: https://files.kde.org/digikam/ Maik
(In reply to Maik Qualmann from comment #2) > Here you will find the pre-release of digiKam-6.4.0 where the problem has > been fixed: > > https://files.kde.org/digikam/ > > Maik Maik 6.4.0 works so far, all mentioned issues are fixed as far as I can see up to now. However, within all these good news, there are also bad news. JPEG2000 files cannot be opened. It does not matter wether generated with version 6.4.0 or prior versions, the imaged editor opens and states "Cannot open file <path><filename>.jp2." 00pippo
This is strange, digiKam is compiled with libjasper support for JPEG2000. Perhaps something is broken about type-mime wrapping and image loader plugins. I will recompile digiKAm for MAcOS this evening with last code from git/master Gilles Caulier
Done. new 6.4.0 PKG installer is rebuilt and available here: https://files.kde.org/digikam/ Gilles Caulier
(In reply to caulier.gilles from comment #5) > Done. new 6.4.0 PKG installer is rebuilt and available here: > > https://files.kde.org/digikam/ > > Gilles Caulier Perfect! Now it works! Thank you!
Fixed with #411902