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

Quicksilver's suggestion pane is detached, unstretchable, and has a totally garbled search...can I uninstall then reinstall without losing my 40 keyboard command triggers #2989

Closed
3 tasks done
sambovermont opened this issue Nov 11, 2023 · 8 comments

Comments

@sambovermont
Copy link

Before submitting your bug report, please confirm you have completed the following steps

Bug description

Quicksilver's suggestion pane is detached, unstretchable, and has a totally garbled search...can I uninstall then reinstall without losing my 40 keyboard command triggers

Steps to reproduce

  1. Just basic use of the app....previous keyboard prompts yielded perfect results....seriously worked now

Expected behavior

To work like before....

MacOS Version

Other

Quicksilver Version

Current, just checked for update

Relevant Plugins

No response

Crash Logs or Spindump

No response

Screenshots

No response

Additional info

No response

@jdortiz
Copy link

jdortiz commented Nov 14, 2023

I have the same problem. It also has some problems with the preferences windows, that disappear from screen.

@pjrobertson
Copy link
Member

To be able to help out you need to provide at least:

  1. the Quicksilver version you are using
  2. The version of macOS you are using
  3. A screenshot of the issue.

@sambovermont
Copy link
Author

sambovermont commented Dec 1, 2023 via email

@n8henrie
Copy link
Member

n8henrie commented Dec 4, 2023

@sambovermont

Quicksilver has several serious bugs on MacOS 14 (Sonoma). Please try the steps here to see if they help, and please report back: #2994 . Thank you!

@sc8tty
Copy link

sc8tty commented Dec 6, 2023

Disabling "superfluous visual effects" (linked in the previous post #2994) worked for me. I missed the note about it requiring a restart of QS so make sure you do that.

@sambovermont
Copy link
Author

sambovermont commented Dec 6, 2023 via email

@jonathanalevi
Copy link

Wasted an hour on this freaking problem before coming here. SO ANNOYED.

@n8henrie
Copy link
Member

Looks like the recommendations worked around the issue for the OP and the newest release forces this behavior at launch-time so will close for now. (In the upcoming version I hope to remove the use of the private APIs which should more fully prevent the issue from cropping up again in the future.)

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

No branches or pull requests

6 participants