Sounds like one of the plugins you installed was the AirPort Module. The version available from within QS is broken and causes QS to crash. To fix this, go to ~/Library/Application Support/Quicksilver/PlugIns and remove the plugin (I think it should be called AirPort Modul.qsplugin). Then try to start QS again.
If you still want to use the AirPort Module, go to http://qsapp.com/plugins/ and download the new version from there and install it manually (by double-clicking once it's downloaded). On Wed, Oct 5, 2011 at 4:21 PM, Eric Weir <[email protected]> wrote: > I'm a real QS novice, having barely scratched the surface of its > capabilities. I have, however, become pretty reliant on it to launch > most of my applications and to shut them down. > > A few minutes ago I was browsing the interface and added a few > plugins. The last one I tried to add the interface disappeared, and > now QS will not run. The QS logo appears briefly then disappears. I > opened the package and clicked on the binary, same thing happened, but > I also got the following report from the terminal: > > /Applications/Utilities/Quicksilver.app/Contents/MacOS/Quicksilver ; > exit; > MacBookWeir:~ ericweir$ /Applications/Utilities/Quicksilver.app/ > Contents/MacOS/Quicksilver ; exit; > 2011-10-05 10:08:35.543 Quicksilver[1314:903] Prevented load of > unidentified action from bundle Keychain Module.qsplugin because the > action's featureLevel (set from its Info.plist) is higher than NSApp's > current featureLevel. This is not neccessarily an error. Sometimes > this mechanism is used to prevent unstable actions from loading. > WirelessAttach: IOServiceOpen error: e00002c7 > Error: WirelessAttach: -2013261827 > logout > > Does this explain what has happened? Whether it does or not, what do I > need to do to get QS running again? > > I know this is not much information to go on, but I don't know what to > provide. > > Thanks, > > Eric Weir > >
