On Sep 13, 2012, at 11:02 AM, Rob McBroom <[email protected]> wrote:
> On Sep 12, 2012, at 5:10 PM, Jack Miller <[email protected]> wrote: > >> All of a sudden our beloved QS will not start up for me. I get an >> >> Interface Changed >> Interface could not be load... >> >> Error. > > Is it possible that it’s running, but it just won’t do anything? > > This error appears when your chosen interface couldn’t be loaded. It should > fall back to the default (Bezel), but perhaps it can’t load that one either. > Seems unlikely, but if Quicksilver is still running, you should be able to > access the preferences. What happens if you try to pick an interface there > (under Appearance)? > > If you can’t get into the preferences, run this command in Terminal and let > me know what it says. > > defaults read com.blacktree.Quicksilver QSCommandInterfaceControllers > > For those of you that updated: To which version? Are you using the B70 > pre-release or B69? I had the problem after updating the Automator plugin. After I removed all extra interfaces QS would appear in Activity Monitor, but it'd be unresponsive. Since I got QS working, I haven't really pinned the issue to the Automator plugin, but I found 2 Automator plugins in ~/Library/QuickSilver/plugins after the update. I could try breaking QS again if needed. Israel -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
