quicksilver / Quicksilver

Quicksilver Project Source
http://qsapp.com
Apache License 2.0
2.74k stars 286 forks source link

[Bug]: Sonoma/Intel QS doesn't fully load at start up #3004

Open dcnicholls opened 9 months ago

dcnicholls commented 9 months ago

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

Bug description

If I set load a login, QS starts up without the menu bar icon (blank menu bar icon, reported elsewhere) and the triggers don't work properly - some work, others do odd things depending on the open app. Work around: Don't set load at start up, run QS from the dock icon, things appear to work as they should. Intel Mac (2018), Sonoma 14.2.1 QS 2.4.2

Steps to reproduce

  1. Set load at login
  2. Log in

Expected behavior

Expect load at login to show menu bar icon and for triggers to work

MacOS Version

macOS 10.14

Quicksilver Version

2.4.2

Relevant Plugins

n/a

Crash Logs or Spindump

doesn't crash or hang, just doesn't work properly

Screenshots

No response

Additional info

Updated from Ventura to Sonoma (bad idea) and then had to remove old version of QS (flakey, then installed the latest version. Problems as described above with Sonoma and new QS

dcnicholls commented 9 months ago

I should mention that six other non-MacOS items load into the menu bar at log in, but none experience problems. QS problem only happened after update to Sonoma.

n8henrie commented 9 months ago

I'm not sure about the menu bar issue -- I just enabled it and then tested twice, and the menu bar icon is present on bootup as expected.

The triggers issue I can replicate.

dcnicholls commented 9 months ago

My impression is that QS is not loading fully, before the menu bar icon and the triggers have loaded, perhaps due to the other things I am loading on boot up. Used to load properly on Ventura, but not now. The bug is pretty consistent. I have to run QS manually from the Dock after boot up and then it works properly.

warrenlain commented 6 months ago

I'm experiencing the same issue, subscribing to hear more.

n8henrie commented 5 months ago

@warrenlain can you be more specific about which issue you're also seeing?

@dcnicholls I'm trying to think of how to get more information, since I'm not seeing this issue. One option, if you're willing, is to see if you can provide me some logs from a debug build.

You could try:

  1. Quick QS
  2. Download a debug build from e.g. https://github.com/quicksilver/Quicksilver/releases/download/v2.4.2/Quicksilver-debug.zip
  3. Unzip
  4. You can run normally by right / two-finger clicking and selecting "run" and probably ignoring a few warnings about it not being signed. However, instead...
  5. Open up Terminal.app and run something like the below to run with extra verbosity for the startup sequence, capturing the output to qs-debug-startup.log but also displaying to your screen
QSDebugStartup=1 ~/Downloads/Quicksilver.app/Contents/MacOS/Quicksilver 2>&1 | tee ~/Downloads/qs-debug-startup.log

If you're able to do that, take a look through ~/Downloads/qs-debug-startup.log and if you don't see anything too private, please post it (otherwise we can talk about other ways to look through).