Re: Constant crashing on changing triggers

Be sure you're running 3815 (get it from www.blacktree.com)

tiennou's builds (posted to the google code site) have this behavior  
if there are mouse triggers defined. I think it will be fixed (at  
least somewhat) in his next build. I use 3815 on 10.5.4 so that my  
mouse triggers work.

Your ~/Library/Application Support/Quicksilver/Triggers.plist file is  
probably corrupt. Quit Quicksilver, (re)move this file, and restart  
Quicksilver. Any custom triggers will be gone but you can recreate them.

Note, when you delete a .app on the mac your settings are not removed.  
They are stored in your ~/Library/ folder (usually under Preferences/  
and Application Support/). For this reason, just uninstalling and  
reinstalling often doesn't help a problem, but cleaning out the  
settings and merely restarting usually does.

Howard

On Jul 18, 2008, at 5:17 AM, Rob G wrote:

> Hi,
>
> I'm new to Mac and to Quicksilver. I love the application, but am
> running into problems and have had to uninstall it. I was running b54
> (latest version downloaded and installed for the first time
> yesterday). I'm running OS X 10.5.4.
>
> Everything was working fine yesterday. I then created a customer
> trigger to paste some text on pressing a certain hotkey combination.
> This worked fine. When I restarted the machine this morning, the
> hotkey combination was no longer working - I checked in QS and sure
> enough, it was no longer listed under custom triggers. So I created it
> again. However, after that, whenever I reopened QS preferences and
> clicked on Triggers, I got a kind of spinning wheel in the top left of
> the preferences window, and the Triggers pane never appeared. One of
> these times, the application froze and there was nothing I could do to
> exit it (it didn't even appear in the Force Quit list).
>
> I've tried uninstalling and reinstalling it without any modules, but
> the problem is still there. In fact, it's even worse now - I can't get
> into the Triggers pane at all without getting the spinning wheel, not
> even the first time I try to access it.
>
> I've read through various posts about this kind of issue, suggesting
> various approaches which may or may not work, involving unofficial
> builds, terminal commands etc. I don't really want to get into
> something complicated like that. I just want to know if there is a
> straightforward fix for this issue so that I can become a happy QS
> user.
>
> Thanks in davance,
>
> Rob