Quicksilver not launching with keyboard or from .app, please help!

[Vincentvw]

Dear all,

System-specs:
iBook g4
Leopard 10.5.5
Quicksilver-b56a2 (but also happens with the b54 version)

I've been having some Quicksilver problems since this morning. It
started when I installed Cog, the open-source music player. It froze,
but refused to be removed from the dock. Other apps started doing the
same and I force-restarted my mac.

Afterwards, Quicksilver would just crash on startup. I posted the bug
here: http://code.google.com/p/blacktree-quicksilver/issues/detail?id=152&q=safaristand

Then I tried removing all quicksilver files by searching the finder
and when that happens Quicksilver starts up as a new install, asks a
few questions, then seems to run.

However, I cannot seem to launch it by pressing the keyboard shortcut,
I assigned to it: option-space. Double-clicking Quicksilver.app also
doesn't do anything. The screen actually flashes when I do either,
because I set that in the OS X preferences. The process runs on my Mac
with minimal CPU-usage, but just seems to sit there.

I've run a permission-repair and the full suite of Onyx, restarted,
but no effect. I'm at a loss at what to do now. Is there somewhere I
reset the whole thing, or did I forget to delete a file somewhere?

Please help!

[jarhead]

I'm having the same problem this morning.

Leopard 10.5.5 on a MacBook.

iTunes and Safari were updated yesterday. Not sure if that might have
something to do with it.

On Dec 4, 3:16 pm, Vincentvw <el.Vin...@gmail.com> wrote:
> Dear all,
>
> System-specs:
> iBook g4
> Leopard 10.5.5
> Quicksilver-b56a2 (but also happens with the b54 version)
>
> I've been having some Quicksilver problems since this morning. It
> started when I installed Cog, the open-source music player. It froze,
> but refused to be removed from the dock. Other apps started doing the
> same and I force-restarted my mac.
>
> Afterwards, Quicksilver would just crash on startup. I posted the bug

> here:http://code.google.com/p/blacktree-quicksilver/issues/detail?id=152&q...

[Howard Melman]

The first FAQ item has the list of all the things to remove (or
rename) to reset QS completely.
http://groups.google.com/group/blacktree-quicksilver/web/faq

I'm using QS B54 fine on a MacBook Pro running 10.5.5, Safari 3.2.1
and iTunes 8.0.2

I find the B54 to be the most stable version, and be sure to uninstall
plugins you don't use. Some of them are unstable on leopard. Don't
run the Services Menu plug-in.

Howard

[Vincentvw]

I'm sad to say that deleting those files hasn't helped.

When I do so, Quicksilver starts up, asks me to set a few preferences,
then it disappears, the screen flashes (that's a system alert on my
Mac) and Quicksilver disappears. Neither the trigger or clicking .app
have any effect, except to make the screen flash again.

When starting, with the option-key pressed, the console prints the
following:
12/5/08 10:22:19 AM Quicksilver[1567] Setting Verbose

That's it! What the hell is going on!!!??? I've tried both beta54 and
56.

Funny thing is that even though I deleted those files, run Onyx, and
reboot, it still remembers the custom-trigger I set for it. So is
there a hidden file somewhere that I forgot???

Vincent

On Dec 5, 11:43 pm, Howard Melman <hmel...@gmail.com> wrote:
> The first FAQ item has the list of all the things to remove (or  

> rename) to reset QS completely.http://groups.google.com/group/blacktree-quicksilver/web/faq

[Howard Melman]

I was worried until you got to your last paragraph. If a custom
trigger is still around then you're not deleting the right files.
Triggers are stored in

~/Library/Application Support/Quicksilver/Triggers.plist

Note the ~ at the start of that means your home folder. Be sure the
path you're changing isn't some other account on the machine or the
system library folder which would be:

/Library/Application Support/Quicksilver/Triggers.plist

Howard

[Vincentvw]

I'm sorry, but those were the files I deleted. I only have one user on
my machine, me, and I also searched the system-folder, to no avail.
This is very odd.

[Vincentvw]

OMG, after trying countless of things (incl. downgrading), getting
desperate, and downgrading again, it now works again. Thank the lord…
and everyone who responded!