[digiKam-users] Known problems under macOS 11?
mbs at mbsnet.de
Tue Nov 17 15:59:10 GMT 2020
Hi Gilles and Peter,
thanks for the quick response. Don’t know, why my googling didn’t find this bug report.
Unfortunately my MacBook is nearly as old as Gilles' and the system disk is rather crowded. No space anymore for installing Xcode. Therefore I'll probably do a roll back or wait for 7.2, hoping the MacPorts issues are fixed till then.
BTW: Many thanks for all your efforts put into development of digiKam during all the many years I am using it. It is a really great piece of open source software.
> Am 17.11.2020 um 16:34 schrieb Gilles Caulier <caulier.gilles at gmail.com>:
> See also the bugzilla entry here :
> Gilles Caulier
> Le mar. 17 nov. 2020 à 10:16, Peter Teuben <teuben at gmail.com> a écrit :
>> there was a lot of discussion in the media (e.g. slashdot) about macOS11
>> needing to certify the app, and long delays with that. I don't know how
>> apple is going to solve this if you are in an airplane with no network.
>> But what about the certification. If I have my own code, compile it, can
>> i just run it? Or do I need to be registered as a valid developer with
>> some app key? So far i've been able to compile my own stuff, you usually
>> get some warning to click on the OK button if you allow this app to run.
>> Your particular problem seems different, as there is just a black screen
>> followed by a crash. If you move the databases to a backup directory,
>> and so to say start from scratch, is there the same behavior? No splash
>> screen either?
>> On 11/17/20 10:00 AM, Manuel Bock wrote:
>>> Hi digiKam users and developers,
>>> I am having problems with starting digiKam on my Mac after upgrading to macOS Big Sur. Since searches do not show any reports of this problem so far, I wonder, if this is a known issue or if I have to look for problems specific to my machine or setup, rather not related to this upgrade?
>>> Background info:
>>> - macOS 11.0.1
>>> - digiKam 7.1
>>> No visible activity on screen after starting the app. In the activity monitor of macOS there is one digikam process running on one core with close to 100% cpu time, the error counter ist staidly increasing, the open files show just libraries and the database, but no open image files, and after a rather looooong period, the macOS error message occurs, digiKam was terminated unexpectedly.
>>> A reinstall does not change anything at all.
>>> Is anybody out there having the same issues after upgrading to Big Sur? Or are there any hints on were to start digging for specific issues on my machine?
More information about the Digikam-users