[Bug]: Mac Notes.app crashes on QS launch

PeterJ1947 commented 2 years ago

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

[X] Searched the issue is not already listed in the Issue List (I've searched it)
[X] Searched in the Quicksilver Users' Group for questions relating to tech support.
[X] Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.

Bug description

Mac mini M1, OS 12.3.1, 16GB, QS 2.1.0 (4032). Have been using QS for several years. With latest update any launch of Notes.app from QS causes Notes to crash on launch. Notes will launch successfully when double-clicked from Finder. This is only app I have found this on, all other apps that I use routinely (Mail, Safari, Pages, BusyCal, PDFPro, Messages, etc) launch fine from QS. Crash report in attached file Notes Crash Report.pdf .

Steps to reproduce

Press cmd-space to launch QS 2.Press "N" to select NOtes.app 3.Press to launch Notes.app 4.Mac beeps and returns crash report indicating Notes has crashed.
Multiple attempts return same effect, including after computer restarts

Expected behavior

Notes.app should launch successfully 100% of the time, just like other apps.

MacOS Version

macOS 12

Quicksilver Version

2.1.0

Relevant Plugins

None that I know of are relevant -- however Maestral (Dropbox clone), Hazel, Backblaze, Default Folder X and Time Machine are all running.

Crash Logs or Spindump

Attached above.

Screenshots

No response

Additional info

No response

n8henrie commented 2 years ago

Launches Notes.app without trouble here (m1 mbp).

A few odd things:

EXC_CRASH (SIGKILL (Code Signature Invalid))

That seems odd -- how did you install quicksilver?

"procPath" : "\/Volumes\/VOLUME\/*\/Notes.app\/Contents\/MacOS\/Notes",

That doesn't look like the right path. Can you send me a screenshot of what QS looks like after step 2 but before step 3? Could you have something else mounted in /Volumes that is launching the wrong Notes.app?

For example:

This shouldn't be right either, both Notes and QS should be running natively as arm64.

"cpuType" : "X86-64",

PeterJ1947 commented 2 years ago

Nathan your note put me on the right path to solve this.

Here’s the screenshot you asked for:

This is pointing to the wrong volume and copy of Notes — this is a copy stored on a mounted backup disk which archived the contents of my wife’s old iMac and some legacy financial reports that we need to keep for tax purposes.

I can fix this! I navigate to the right copy of Notes (not the one built for an Intel CPU) and make that default…

Sorry for the trouble … next time I’ll check the path!

Peter

On May 9, 2022, at 16:12, Nathan Henrie @.***> wrote:

Launches Notes.app without trouble here (m1 mbp).

A few odd things:

EXC_CRASH (SIGKILL (Code Signature Invalid)) That seems odd -- how did you install quicksilver?

"procPath" : "\/Volumes\/VOLUME\/*\/Notes.app\/Contents\/MacOS\/Notes", That doesn't look like the right path. Can you send me a screenshot of what QS looks like after step 2 but before step 3? Could you have something else mounted in /Volumes that is launching the wrong Notes.app?

For example:

https://user-images.githubusercontent.com/1234956/167489585-18b0f773-cbf5-4aa5-beae-fbc30c054f55.png This shouldn't be right either, both Notes and QS should be running natively as arm64.

"cpuType" : "X86-64", — Reply to this email directly, view it on GitHub https://github.com/quicksilver/Quicksilver/issues/2867#issuecomment-1121530474, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZCASH3HKURZ5YE5ANWYNULVJFWUTANCNFSM5VKUMT6Q. You are receiving this because you authored the thread.

n8henrie commented 2 years ago

No trouble at all, glad to get it sorted out.

BTW, your screenshot didn't come through (maybe due to sending via email). However your full name and phone number did -- I updated your response to remove them and deleted the revision that had them. Just FYI!

PeterJ1947 commented 2 years ago

Thank you sir — both for the help and the courtesy!

On May 9, 2022, at 17:01, Nathan Henrie @.***> wrote:

No trouble at all, glad to get it sorted out.

BTW, your screenshot didn't come through (maybe due to sending via email). However your full name and phone number did -- I updated your response to remove them and deleted the revision that had them. Just FYI!

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

quicksilver / Quicksilver