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

QS always shows at top left corner of the screen on first use after computer startup.[Bug]: #2984

Closed
3 tasks done
LuisVxd opened this issue Oct 31, 2023 · 4 comments
Closed
3 tasks done

Comments

@LuisVxd
Copy link

LuisVxd commented Oct 31, 2023

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

Bug description

After install Sonoma (14.0) QS shows at top left corner of the screen. Difficult to move to other position as QS window does not follow the cursor, it lags behind.
It always go back to top left corner of the screen at computers startup.

Steps to reproduce

  1. Start the computer
  2. Trigger QS

Expected behavior

I am QS user since 2008. QS always kept window position where it was last closed even after computer restart.

MacOS Version

Other

Quicksilver Version

2.4.1 (4040)

Relevant Plugins

No plugins installed

Crash Logs or Spindump

No response

Screenshots

No response

Additional info

I have a 2019 Macbook Pro (Intel) with no extra displays and a resolution 1680x1050 (default).
This odd behavior started after install Sonoma. Previously all was ok.

@LuisVxd LuisVxd changed the title QS always shows at top left corner of the screen on first use after computer stratup.[Bug]: QS always shows at top left corner of the screen on first use after computer startup.[Bug]: Oct 31, 2023
@randomobject
Copy link

Same here. I'm using latest M1 MacBook. Also happened after upgrade to Sonoma. Previously all good.

@n8henrie
Copy link
Member

Thanks for your report! This is already being tracked at #2962

@n8henrie
Copy link
Member

(I realize that this is about the QS interface and the former is about the results list, but I'm pretty sure it's the same underlying problem and fixing one should lead to a fix for the other. Unfortunately I'm having a hard time sorting out the root cause -- but I'm trying.)

@LuisVxd
Copy link
Author

LuisVxd commented Nov 1, 2023

Yes, I got similar behavior with results list as former. It should be the same issue.

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

No branches or pull requests

3 participants