Re: Quicksilver will not start up

[Jon Stovell]

Try these steps to see if they can resolve the problem for you.

http://qsapp.com/wiki/FAQ#How_to_Quickly_Reset_Quicksilver_Settings

On Wednesday, September 12, 2012 5:10:12 PM UTC-4, Jack Miller 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.

Help, please. I'm in withdrawal.

[Jack Miller]

No joy.  Same error message.  Is there a way to uninstall and start over again?

[NightStalker]

Same problem here, just after QS updated itself

Helpppp - methinks we need a new install package to overwrite the problem, as QS won't be running to update itself.

[Patrick Robertson]

Hi there both,

Can you please find the Quicksilver.app file in Finder and use 'Get Info' (right click) to see which version you are running. This should help us pinpoint the problem.

Also, if you can tell us

a) If you have any reports on Quicksilver in Console.app (find it in /Applications/Utilities)

b) Which interface you use for Quicksilver (Primer, Bezel, Mini interface etc.)?

Thanks

--
You received this message because you are subscribed to the Google Groups "Quicksilver" group.
To post to this group, send email to blacktree-...@googlegroups.com.
To unsubscribe from this group, send email to blacktree-quicks...@googlegroups.com.
Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
 
 

[Rob McBroom]

On Sep 12, 2012, at 5:10 PM, Jack Miller <jmill...@gmail.com> 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?

--
Rob McBroom
<http://www.skurfer.com/>

[Israel Chauca F.]

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

[Keith Kastorff]

On my machine the issue is definitely the new Automator plugin. The plugin shows up on the plugin downloads page as "Automator Plugin" version 1.2 dated 2012-9-12. The plugin inside Quicksilver still shows up under the old name as "Automator Module" version version 1.1.0 date 2012-3-27. Version 1.2 does not show as an update, even when manually checking for updates within Quicksilver. From within QS I removed the old plugin, and then downloaded and installed the new plugin by double clicking on it in the Finder. As soon as QS relaunched, it no longer responded to my activation hot key.

Console displays this message with the new plugin installed: 9/13/12 12:00:53.353 PM Quicksilver[29001]: *** setObjectForKey: object cannot be nil (key: QSCommandInterfaceControllers)

If I uninstall the new plugin and restart QS, it works fine.

Keith

On Wednesday, September 12, 2012 4:10:12 PM UTC-5, Jack Miller 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.

[Rob McBroom]

On Sep 13, 2012, at 11:35 AM, Israel Chauca F. <israel...@fastmail.fm> wrote:

> 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 didn’t have it installed, but if I install it fresh, I can reproduce the problem. We’ll look into it. Thanks.

[Rob McBroom]

OK, a new version of the Automator plug-in is available and should fix this.

To install it, I suggest

* Delete any copies you have in `~/Library/Application Support/Quicksilver/PlugIns`
* Launch Quicksilver
* Go into the Plugins preferences and click refresh at the bottom of the window
* Make sure Automator shows version 1.2.1. If so, install it.

[NightStalker]

Wow...!!  What fantastic support.  Problem fixed :))

Thank you x1000

[Keith Kastorff]

Probably should tell folks that the update requires a newer build than B69 (3932). Version 1.2.1 doesn't show up in my plugins list.

[Jack Miller]