search

nomic-ai / gpt4all

GPT4All: Run Local LLMs on Any Device. Open-source and available for commercial use.
https://nomic.ai/gpt4all
MIT License
69.11k stars 7.59k forks source link

how to uninstall gpt4all on Macbook (M) #2839

Open Jack-613 opened 1 month ago

Jack-613 commented 1 month ago

Documentation

Hello Support,

can you please help me and tell me how I can uninstall gpt4all which I have installed on my Macbook (M) ?

Thanks for short instructions!

Best regards

manyoso commented 1 month ago

If you look in your applications folder you should see 'gpt4all' go into that folder and open the 'maintenance tool' exe and select the uninstall. You might also need to delete the shortcut labled 'GPT4All' in your applications folder too.

Jack-613 commented 1 month ago

Thank you for your quick feedback.

But my question relates to the installation in the Mac OS. There is no directory with exe files.

Can you give me a deInstallation recommendation for Mac OS ?

thx

manyoso commented 1 month ago

What I described above is how I'd do it on macOS

Jack-613 commented 1 month ago

found it !

Thx :-)

cosmic-snow commented 1 month ago

Added a page on the wiki: Uninstalling the GPT4All Chat Application. Although it's still in an initial stage.

There's also this older issue, not sure if there are others:

aeonoea commented 1 month ago

The maintenancetool application on my mac installation would just crash anytime it opens.

This means when manually opening it or when gpt4all detects an update, displays a popup and then as soon as I click on 'Update', crashes in this moment.

maintenancetool-crash-log.txt

cosmic-snow commented 4 weeks ago

The maintenancetool application on my mac installation would just crash anytime it opens.

This means when manually opening it or when gpt4all detects an update, displays a popup and then as soon as I click on 'Update', crashes in this moment.

maintenancetool-crash-log.txt

I've seen that log but can't really look into it since I don't have a Mac. Is this from an older installation? New installers should be signed now, but I'm unsure if that's also the case for the maintenancetool.

By the way, you might have to open a separate issue as this sounds more like a bug than a case for additional documentation.

aeonoea commented 4 weeks ago

@cosmic-snow It's from the most recent gpt4all installation. Not sure if it's a signage problem, I suspect more it's a problem with OS compatibility. In the logs you can see I am running the most recent MacOS 15.0 which is currently in late public beta and will be released soon as stable. Probably best to address compatibility issues before that... let me know if I can help test.

cosmic-snow commented 4 weeks ago

Sorry, but as I said I can't look into this. I hope someone else can pick it up from here.

manyoso commented 4 weeks ago 
Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 1 Taskgated Invalid Signature

@aeonoea I'm guessing that you're using a maintenance tool before our updated code signing for macos? What is the file date on that maintenance tool binary?

aeonoea commented 4 weeks ago

@manyoso As far as I know I have never encountered a maintenancetool binary before gpt4all. When the error occurred the first time it was with gpt4all v3.1.1, which is not on my system anymore (uninstalled manually and replaced with 3.2.0). The file now dates Aug 13. Which version was the code signing updated?

manyoso commented 4 weeks ago

That should have the newly signed version. Adding @johnwparent who has written our code signing for macOS in the CI.

johnwparent commented 4 weeks ago

Thanks for the context all, investigating now.

johnwparent commented 3 weeks ago

@aeonoea if you run codesign -dv --verbose=4 <path to maintenancetool> what are the results? I've tried a few different versions of gpt4all and the maintenance tool and have been unable to replicate the behavior (all of mine are signed and run w/o issue). At this point I'm wondering if you have a local configurating requesting extra entitlements from the maintenancetool.

aeonoea commented 3 weeks ago

@johnwparent if I run the code I get these results:

% codesign -dv --verbose=4 /Applications/gpt4all/maintenancetool.app Executable=/Applications/gpt4all/maintenancetool.app/Contents/MacOS/maintenancetool Identifier=com.yourcompany.installerbase Format=app bundle with Mach-O thin (x86_64) CodeDirectory v=20500 size=286473 flags=0x10000(runtime) hashes=8945+3 location=embedded VersionPlatform=1 VersionMin=720896 VersionSDK=852224 Hash type=sha256 size=32 CandidateCDHash sha256=bbd75cde314e624e6d4bd919c19f73078b6970ba CandidateCDHashFull sha256=bbd75cde314e624e6d4bd919c19f73078b6970bab6e1a1ee9968c71aca08f14b Hash choices=sha256 CMSDigest=bbd75cde314e624e6d4bd919c19f73078b6970bab6e1a1ee9968c71aca08f14b CMSDigestType=2 Executable Segment base=0 Executable Segment limit=28246016 Executable Segment flags=0x1 Page size=4096 CDHash=bbd75cde314e624e6d4bd919c19f73078b6970ba Signature size=8980 Authority=Developer ID Application: Nomic, Inc (PA) (6P9A8WD2QJ) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=12 Aug 2024 at 21:53:46 Info.plist=not bound TeamIdentifier=6P9A8WD2QJ Runtime Version=13.1.0 Sealed Resources=none Internal requirements count=1 size=192

johnwparent commented 3 weeks ago

@aeonoea Thanks, that all looks correct, the maintenancetool is definitely signed according to the sign tool. This might be an issue of the kernel's signature validation. Can you provide a bit more context about your system?

aeonoea commented 3 weeks ago

@johnwparent For sure! I pasted the hardware info section. Let me know if you need more info.

Model Name: Mac mini Model Identifier: Mac14,3 Model Number: MMFJ3SM/A Chip: Apple M2 Total Number of Cores: 8 (4 performance and 4 efficiency) Memory: 8 GB System Firmware Version: 11881.1.1 OS Loader Version: 11881.1.1 Activation Lock Status: Enabled