メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Plugin initialization failed

コメント

3件のコメント

  • Permanently deleted user

    Hi Ken,

    This type of issue has been encountered by some users, mostly those running Windows, but it happened to me, too, that the plug-in was disabled when launching Capture One (20.0.4 under Mojave).

    An update will be available from tomorrow, if I understand the message I received today, and maybe you could wait until then before opening a ticket at the Capture One staff.

    Robert

    0
  • Ken Bates

    Thanks for the info, Robert. If the message you're referring to is the same one I got today, I have the same issue with what that message refers to (is that a roundabout reference, or what?). Hopefully it's something that can be fixed.

     - Ken

    0
  • Ken Bates

    The problem turned out to be the way I had my system configured. For various reasons (performance and reliability), my home folder is on a separate drive from the system disk. Although this worked well in the past, Catalina considers this disk to be a removable one (even though it's an internal SSD), and when doing installations, requires me to 'allow removable drive access' for applications.

    I did this for C1, but apparently the plugin is considered an application by Catalina, so when it tried to load, it failed since it didn't ask for permission to access the removable drive and eventually timed out.

    The solution was to completely remove C1, then log in to the admin account, which was on the system disk. Installing C1 from that account worked, so when I switched over to my account, everything was set up and worked fine. The error apparently occurred during the installation phase, working fine on the admin account but not requesting the appropriate permission when installed from a home directory other than the system disk, even though the eventual destination was the same (/Applications).

    Not sure if this is a C1 bug (probable) or a Catalina issue (also probable), but since I now know the workaround and things work, I'm happy. Hopefully I won;'t have to go through this for upgrades, but if so, at least I now know how to do it.

     - Ken

    1

投稿コメントは受け付けていません。