Triggers become null in Snow Leopard about quicksilver

[tilltheis]

I can not even change the Launch-Quicksilver-Trigger. Setting it to anything else than Ctrl-Space (e.g. Cmd-Space) yields a "(null) does not respond to (null)" message in Console.app.

[jackbrannen]

Me too! Same problem.

[starrynight]

Same issue, here. I created a trigger to run an AppleScript. It works fine until QuickSilver retstarts. The trigger remains however it doesn't remember which script to run and simply displays "Run: (Null)". My Quicksilver version is B58(3841) and OS is Snow Leopard 10.6.5

[starrynight]

It appears that I should add the scripts folder into the category to make it work.
Now the issue seems to be resolved.

In my experience, they start working after you make QS realize that all the objects in the trigger are in it's catalog, i.e. if you have a trigger for searching Google which doesn't work on startup and has "(null)" in the description in the Triggers preference pane, you have to open QS and type 'goo' to make it see the Google item in the catalog. Then the trigger works normally, and appears correctly in the preferences.

Obviously this isn't a real solution, but it gives me some ideas about where to start looking for the bug that's making this happen.

[lmartins]

I can confirm that searching for the catalog items does make QS aware of the triggers. Like neurolepsy said, not ideally but for now i eases the pain.

[dacode-zz]

I have the same problem. Why would the version before B59 not have this issue and has there been progress resolving it?

This seems like a pretty basic function of QS.

[pjrobertson]

This will be fixed in an up and coming version of Quicksilver.

For those who'd like to build and test, then checkout this branch: https://github.com/pjrobertson/Quicksilver/commits/triggerNull

[pjrobertson]

Fixed in the latest HEAD