Quicksilver is Buggy on MacOS 14 (Sonoma) about quicksilver

[winstonford]

Running QS 2.4.2 smoothly on (4041) Sonoma 14.2.1

Thanks a ton for the work and update. Before the update I had problems with launcher begin off center and top right of screen. No more. Working as expected.

[jtharp-ict]

Thank you for working on this, I was not able to even get through the setup on a new machine. The Terminal command above helped quite a lot.

[sararielle]

Glad to see this isn't a sign I broke something. (I'm having the "detached pane" issue.) I'm so grateful for the team/community's continued work on this project. I'm a longtime user and I look forward to the continued improvement (and resolution of these issues).

[kattkieru]

Thank you for looking into this. I just bought a new Mac and the installation process for QS was difficult.

For anyone else: if you can't click with the laptop trackpad, try an external mouse. It's what got me to a usable state. The trackpad makes the window jump away like crazy.

[cgarre]

Thank you for this. I struggled a lot to get through the first screen itself, it was not just buggy, it is practically unusable. Thanks for the workaround, I had uninstalled it, now got it back.

[cgarre]

Thank you for looking into this. I just bought a new Mac and the installation process for QS was difficult.

For anyone else: if you can't click with the laptop trackpad, try an external mouse. It's what got me to a usable state. The trackpad makes the window jump away like crazy.

unfortunately nothing worked for me. Most windows use to show up and by the time I try to go to the window, it vanishes. It was a mess, with trackpad and with mouse. I thought I will use stage manager still similar issues. Somehow i figured if i put my mouse at right place i can click through the agreement, and that helped me get past 1 screen - but this is a persistent pain.

[n8henrie]

@winstonford that's great news, thanks for the report!

[wwmiller3]

Still seeing frequent crashes with 2.4.2 on Sonoma 14.2.1. Crash log indicates SIGSEGV:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

[acovrig]

2.3.2 is more stable for me on Ventura, I did get a crash this morning, is there a good/better place to post crash reports to help rather than become noise?

Crashed Thread:        5  Dispatch queue: quicksilver.qslibrarian.scanning
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

I'm hoping to use my Sonoma machine more today, so may have more insight.

I presume it's a separate issue, but my biggest issue in Ventura is typing ~/doc/gi/test to complete to ~/Documents/git/test and it ends up getting ~, then the / for doc gets to the / root path - as-if a path searcher returns too late and it falls back to / (using the → key instead of / works (~→doc→gi→tes), but is less convenient)

[n8henrie]

Sorry for late response.

is there a good/better place to post crash reports to help rather than become noise?

Here on GitHub is great. Submitting the crash reports will hopefully be eventually helpful, but the backlog of issues is long.

my biggest issue in Ventura is typing ~/doc/gi/test to complete to ~/Documents/git/test and it ends up getting ~, then the / for doc gets to the / root path

Perhaps open a separate issue, but this seems odd. ~/git/fauxmo selects the expected directory for me. In settings -> command, what is your Reset search after settings? Mine is 1.5s.