Termination Reason: Namespace SIGNAL, Code 0xb Termination Signal: Segmentation fault: 11 Path: /Applications/MAXON/*/CINEMA 4D.app/Contents/MacOS/CINEMA 4DĪnonymous UUID: 3CF71565-91DE-6993-29A1-C0C50954128CĬrashed Thread: 0 Dispatch queue: -threadĮxception Codes: KERN_PROTECTION_FAILURE at 0x00007ffeed821f38 …So this is how I managed to bungle it up today. I recommend you make a copy of the Mesa folder before you delete it, just in case.Īnyway, hope some of this may help you out! Good luck! ** I found this recommendation online somewhere, though I can’t remember where. * If you don’t know how to do this, I’ll be glad to post instructions. In my first post I noted them as not having worked for me, but maybe they’ll work for you. Delete the Mesa folder located in Applications/MAXON/Cinema 4D R19/resources/libs/osx/ **.Launch in Recovery Mode and run First Aid on your drives.Reset the System Management Controller *.Deleting the contents of your Cache, Launch Agents, Saved Application State, Launch Daemons, etc., folders.If you haven’t already, maybe the following are worth a try: What do you get just before the the startup process exits? The fact that you’re not getting this, that swapping the framework file hasn’t worked for you, and that your issue started after you updated elsewhere makes me think that perhaps your issue isn’t related to the amework.ĭo you get any warnings at all in the Console? Look for the word “error”. (file:///Applications/MAXON/Cinema 4D R19/corelibs/c4dplugin.xlib) In /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice. Referenced from: /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice Error code: dlopen(/Applications/MAXON/Cinema 4D R19/corelibs/c4dplugin.xlib, 6): Symbol not found: _xpc_file_transfer_create_with_path I’m sorry to hear you’re having this issue as sorry as I am to hear this issue is still a thing and that all Maxon are doing to solve it is linking back to this post… I too wondered why they would rely on a private framework, let alone one that has to do with mobile device support.Īnyway, as for your first question: Indeed, I got the error in Console, at the very end of the startup attempt:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |