QS Misfire

[anatomatic]

Since updating to some of the new 64bit plug-ins, QS doesn't "fire" an action:

I.e. On:

github.com --> open url [Return]
Bezel disappears but nothing happens.

Restoring Plugins folder + .plist from Time Machine back-up clears it up.

I imagine 64bit QS will fix this issue, but filing for anyone else seeing this issue in the meantime.

[pjrobertson]

Can you please check the console for any messages related to Quicksilver?

I believe this is an issue related to ß68 and not any newer plugins.
Restarting Quicksilver will fix the problem.

The 64 bit build does indeed have a fix for this issue. See #910

On 9 June 2012 20:33, anatomatic <
reply@reply.github.com

wrote:

Since updating to some of the new 64bit plug-ins, QS doesn't "fire" an
action:

I.e. On:

github.com --> open url [Return]
Bezel disappears but nothing happens.

Restoring Plugins folder + .plist from Time Machine back-up clears it up.

I imagine 64bit QS will fix this issue, but filing for anyone else seeing
this issue in the meantime.

---

Reply to this email directly or view it on GitHub:
#928

[anatomatic]

Here is console log, looks identical to #910:

Relaunched a couple of times, eventually crept back in.

http://dl.dropbox.com/u/425408/QS-console_20120609.txt

[pjrobertson]

Yep, that's the same, which will be fixed in the next release.

Thanks for reporting though, restarting is the best/easiest bet. Unfortunately it'll keep creeping back until the next release.

Bear with us.

[anatomatic]

No prob. Following equation still applies:

Time saved using QS > Time used for occasional QS relaunch