27 Comments

Summary:

From what I’ve been reading on support forums, some users of Quicksilver saw no affect from upgrading their machines to Snow Leopard. I however, was not one of those people. And although I am warming more and more to Google Quick Search Box, I still supplement […]

Quicksilver logo

From what I’ve been reading on support forums, some users of Quicksilver saw no affect from upgrading their machines to Snow Leopard. I however, was not one of those people. And although I am warming more and more to Google Quick Search Box, I still supplement my usage of QSB with Quicksilver where the former is lacking in features. So I tinkered around until I was able to resuscitate and use Quicksilver again under Snow Leopard.

Been having similar problems? Let me walk you through the process.

First, make sure you’ve upgraded to the most current version of Quicksilver. B56a7 is the most up to date version, that is built for Snow Leopard. Download it here if you haven’t already done so. Once that’s done, go ahead and try running Quicksilver. If you’re lucky, that’s all that is needed. If you’re not, don’t fret, because we’ll figure it out in short order.

What I found to be the issue with getting my installation of Quicksilver working, was the huge collection of plug-ins that I’ve installed over the years. Plug-ins (in my opinion) are what have made Quicksilver what it is to so many of us today. They extend it into nearly every nook and cranny of your Mac, allowing you to control everything. The downside, is that some of those plug-ins are broken in OS 10.6’s new underlying architecture.

So let’s fix that.

  • Navigate (using Finder) to ~/Library/Application Support/Quicksilver
  • Open the ‘PlugIns’ folder
  • Select all of the plug-in files, and drag them someplace else (I suggest the Desktop, for easy access, as we’ll be using them again)

Now, let’s make sure Quicksilver opens before we go any further. If at this point the answer is no, I’d recommend posting the question to the Blacktree Quicksilver group on Google. (I’m happy to help too of course, but I’m not that bright, and if I can’t duplicate your setup, there’s a slim chance I’ll be useful on the subject.) If on the other hand, Quicksilver is starting up, let’s continue.

  • Quit Quicksilver
  • Drag the first plug-in (that you moved somewhere, like your Desktop) back into that ~/Library/Application Support/Quicksilver/PlugIns folder
  • Launch Quicksilver

Did Quicksilver remain open? Or did is crash after a few moments? If Quicksilver is still running, then that plug-in was not the culprit, and you may return to the ‘Quit Quicksilver’ step, and repeat with the next plug-in file. If Quicksilver bombed after launch, continue on below. (Does this feel like a choose your own adventure to anyone else?)

  • In the ~/Library/Application Support/Quicksilver/PlugIns folder, delete the plug-in that you just placed there

Unfortunately, that plug-in was no longer valid under the new Snow Leopard architecture. At this point, you should rinse and repeat (so to speak), moving the next plug-in file from your Desktop, into the Quicksilver PlugIns folder, and then seeing if Quicksilver crashes or not. Do this until you’ve deleted the bad plug-ins, and have the rest installed, with Quicksilver running happily again.

As a point of reference, the plug-ins that appear to cause me trouble were:
– Airport Module
– Services Menu
– Text Manipulations (not 100 percent certain about this one)
– Image Manipulations (not 100 percent certain about this one)
– Any interface modules seem to be causing issues as well

The downside is, you may lose some level of functionality (if you were even using that particular plug-in) from Quicksilver. The upside is that you’ll still be able to run Quicksilver, if somewhat pared-down in capability. In my case, I didn’t lose anything I’d been using regularly. In the event that you have actually lost something of use to you, you can either downgrade back to OS 10.5.8 (probably not realistic), or wait on Google QSB to get up to speed, as I have seen some great strides on that application in a short period of time.

  1. Thanks for your advice, I think there should be a list of incompatible plugins for snow leopard at the projects site… but looks like you started doing it here. Add this one to the list: File Tagging Module. I’m gonna miss it, although I didn’t use it too much it used to let me tag several files at a time with the same words, something the Finder, incredibly, doesn’t allow to do.

    Share
  2. Thanks for the post. I followed your tips, but even after moving the plug-ins, QS crashes on startup. Perhaps strangely, the old version (B54) had been working absolutely fine on my new SL running machine. So I went back. But now, when I try to launch QS preferences, there is an empty window and the QS icon sits determinedly in the dock.

    Anyone have any experience or advice on this? Thanks in advance.

    Share
  3. One of my favorite interface plugins HUD no longer worked with Quicksilver B567a7 (the Snow Leopard build). I found over on minimal mac a link to a working version of that plugin.

    The Article:
    http://minimalmac.com/post/182982309/one-of-the-things-that-resulted-from-my-upgrade

    The **New** Bezel HUD Theme:
    http://code.bencochran.com/bezelhud/

    QS is still slow and less responsive after upgrading to Snow Leopard. It’s somewhat stable for me when trying to find new items that were dropped into my Applications folder and occasionally mine crashes on me. I am only using one plugin at the moment and that’s Bezel HUD.

    Share
  4. Don’t you mean “jibe”?

    Share
  5. jibe
    verb [ intrans. ] informal
    be in accord; agree : the verdict does not jibe with the evidence.

    jive
    noun
    a form of slang associated with black American jazz musicians.

    Share
  6. Don’t make it so hard. When you move all the plugins out, don’t move them back just one at a time. That takes too long. Do it in binary: drag half back in. Crashes? Drag half of those back out again. Doesn’t crash, drag half of what’s left back in. Rinse and repeat. For N plugins, it will take on the order of log2 N steps instead of N steps (e.g. 5 instead of 32).

    Share
  7. I found that after upgrading to Snow Leopard my 17″ MacBook Pro was not any faster and in fact started to get annoyingly slow. Even though QuickSilver was working, my preference pane no longer worked. I downloaded the latest version of QuickSilver and now the preference pane appears. On top of that, my computer is much, much faster. I don’t know if it was QuickSilver or something else, but that was quite a coincidence.

    Share
  8. Thanks a lot. At me it was the airport plugin. I tried so long to get QS fixed.
    Thanks again
    Florian

    Share
  9. I was devout Quicksilver power-user for years. Until I upgraded to Snow Leopard. I had the occasional crash, but it wasn’t frequent enough to drive me away to Launchbar – no, it was the speed. It was the horrible horrible speed. I grabbed the newest open source version; it did not help matters. I did a fresh install of Snow Leopard, with the open source to help eliminate cruft, it still did not help matters.
    This day was a long time coming, ever since Alcor gave up active development, QS has never been the same. QSB was my runner up, but is still too under-powered for me to officially adopt. Butler was a little… “weird”. I’m still not 100% satisfied with LaunchBar, but it’ll do for now.

    Share
  10. Hi,

    Copy/paste from Dictionary: “Affect and effect are both verbs and nouns, but only effect is common as a noun, usually meaning ‘a result, consequence, impression, etc.': : my father’s warnings had no effect on my adventurousness.”

    I think you want to use the word “effect” in the first paragraph of you post.

    Share

Comments have been disabled for this post