Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in uninstalling via homebrew #1067

Open
Nintnedo opened this issue Nov 9, 2020 · 22 comments
Open

Error in uninstalling via homebrew #1067

Nintnedo opened this issue Nov 9, 2020 · 22 comments
Labels

Comments

@Nintnedo
Copy link

Nintnedo commented Nov 9, 2020

I Used this app. I didnt like it. Deleted app. still effects my windows

@ianyh
Copy link
Owner

ianyh commented Nov 9, 2020

Have you quit the app as well?

@maclarel
Copy link

maclarel commented Apr 20, 2021

Having this same challenge. Uninstalled via brew but Amethyst is still hijacking all of my windows. As far as I can tell, there's no actual process running that's doing this, nor does Amethyst have any permissions in Accessibility.

Have you quit the app as well?

Not to be a meme, but how?

Edit: Ok, installing the application and stopping/starting it there cleared this up. There's something weird with the version available through homebrew...

@ianyh ianyh changed the title UnInstall App Error in uninstalling via homebrew Jul 3, 2021
@ianyh ianyh added the bug label Jul 3, 2021
@piersolenski
Copy link

Also having this 🫠

@piersolenski
Copy link

@maclarel how exactly did you resolve it in the end? I've tried reinstalling the application, both via homebrew and the website, tried "disabling", uninstalling via both methods, trashing all the preferences, and yet the maximum amount of windows allowed to display at one time feature persists.

At this point considering wiping my machine 🫠

@ianyh any ideas?

@ianyh
Copy link
Owner

ianyh commented Mar 11, 2024

Can you check to see if there's some process still running somewhere?

ps aux | grep -i amethyst

@ianyh
Copy link
Owner

ianyh commented Mar 11, 2024

You can also see if there's something in launchd that's causing it to just keep getting restarted or something.

launchctl list | grep -i amethyst

@piersolenski
Copy link

It looks like it is for both:

ps aux | grep -i amethyst
piers            80828   0.0  0.1 409801312  24000   ??  S     2:39pm   0:04.50 /private/var/folders/93/_ppw8bls1zq
37l52d1mbrdmh0000gn/T/AppTranslocation/D84F9C10-2F4D-4D18-ADCC-8F413C911DE5/d/Amethyst.app/Contents/MacOS/Amethyst
piers            17507   0.0  0.0 408628368   1680 s010  S+    5:50pm   0:00.00 grep -i amethyst
launchctl list | grep -i amethyst
80828   0       application.com.amethyst.Amethyst.4333004.4333014

Whats the best step forward?

@ianyh
Copy link
Owner

ianyh commented Mar 11, 2024

Try

launchctl remove application.com.amethyst.Amethyst.4333004.4333014

and then see if the process is still there.

@piersolenski
Copy link

I've quit Amethyst and now the launch agent has gone, but the process is still there. The PID keeps changing so I can't use kill.

@ianyh
Copy link
Owner

ianyh commented Mar 12, 2024

Could possibly be a launch daemon somehow? You can run the launchctl with sudo to see. Otherwise, you could grep for the current pid instead of an amethyst name to see if it's a different agent somehow.

@ianyh
Copy link
Owner

ianyh commented Mar 12, 2024

Also, this issue may be of help. Homebrew/homebrew-cask#51646

@piersolenski
Copy link

Which particular part of the homebrew issue are you referring to?

I don't know where I'd point xattr -r -d com.apple.quarantine ... because the application supposedly no longer exists 🤔

launchctl list | grep -i amethyst is no longer returning anything, with or without sudo.

The pid seems to be constantly changing so I'm finding it hard to kill it or grep for it.

@ianyh
Copy link
Owner

ianyh commented Mar 14, 2024

You may need to reinstall it first. My impression is that the application was put in a quarantined state as a result of the homebrew installation, and it's stuck there now. I've made occasional changes to the brew formula over the years, but it's mostly just updated by other people so I'm not as familiar with it.

I'll try to see if I can reproduce this tomorrow, and fiddle with xattr to see if I can reverse the quarantine for you. This is really frustrating, and I'm considering removing the cask installation suggestion from the readme.

@piersolenski
Copy link

Reinstalling and running xattr -r -d com.apple.quarantine /Applications/Amethyst.app then uninstalling didn't seem to solve the problem 🫠

Sorry, I love this app and have used in on and off over the years, but right now it seems stuck particularly on the maximum windows setting and it's driving me mad haha.

I've installed in via Homebrew in the past with no issues, so it's weird...

@ianyh
Copy link
Owner

ianyh commented Mar 14, 2024

You can try putting a dot file in that disables the window count limitation and only uses the floating layout. That would functionally disable it for the most part.

@ianyh
Copy link
Owner

ianyh commented Mar 14, 2024

Sorry, I haven't had access to a machine I can test this on yet today.

@piersolenski
Copy link

piersolenski commented Mar 14, 2024

No worries, where would I place the dot file?

@ianyh
Copy link
Owner

ianyh commented Mar 14, 2024

@ianyh
Copy link
Owner

ianyh commented Mar 15, 2024

Okay, I can't reproduce this, but I've read up more on app translocation. One thing you can try is reinstalling via homebrew, but then manually move the application bundle around via Finder. So, like, from Applications to Desktop and back to Applications.

@ianyh
Copy link
Owner

ianyh commented Mar 15, 2024

Also, here is specifically what the ~/.amethyst.yml would look like:

layouts:
  - floating

window-max-count: 0

@piersolenski
Copy link

piersolenski commented Mar 18, 2024

Sadly this doesn't seem to have made a difference 🫠

@ianyh
Copy link
Owner

ianyh commented Mar 19, 2024

Okay. How about installing directly? The newest beta would be the one to try. https://github.com/ianyh/Amethyst/releases/tag/v0.21.0b

If that doesn't change anything, then I can try giving you a version of that build with a different hardened runtime configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants