If I close Quicksilver and restart the application it then works as it
should.
Thanks,
Dave.
Sounds a lot like https://github.com/quicksilver/Quicksilver/issues/580
I’m stumped at the moment.
--
Rob McBroom
<http://www.skurfer.com/>
DN
Shame, because I have used QS forever and don't want to let it go...
1. Turn off the Start at login option in QS's preferences.
2. Paste the text below into a new plain text file in TextEdit. Remove
the annoying line breaks that Google groups introduces into long lines
of text. (In particular, <!DOCTYPE plist ... PropertyList-1.0.dtd"> is
all one line, as is the line listing the path to the executable inside
Quicksilver.app under the ProgramArguments key.)
3. Save the file in ~/Library/LaunchAgents with a name like
"QuicksilverStartAtLogin.plist"
4. Open Terminal and enter this command: launchctl load ~/Library/
LaunchAgents/QuicksilverStartAtLogin.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://
www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>QuicksilverStartAtLogin</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Quicksilver.app/Contents/MacOS/Quicksilver</
string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
Optionally, you can replace <key>RunAtLoad</key> with <key>KeepAlive</
key> if you want QS to restart automatically if it ever crashes.
Excellent.
DN
On Dec 2, 9:48 pm, Jon Stovell <jonstov...@gmail.com> wrote:
I was able to reproduce this finally in a test account, but it no longer happens with B64 (which was made available as a pre-release this morning). Could you try it out and see if it fixes this problem?
(Go to the Extras section of the preferences to tell Quicksilver which type of release to look for. Make sure it’s on “Prerelease Candidates”, then go to the Application section of the prefs and click “Now” to check for the update.)
defaults read com.blacktree.Quicksilver "Last Update Check"
Thanks.
But be aware that I don't consistently get the faded Splash Icon on startup (only sometimes), what I do get consistently is that Quicksilver consistently hangs up on Startup (process is there, but I can't activate it; If I start it manually again a dialog appears that gives me the option to clear caches; from thereon it works fine)
2011-11-17 10:06:06 -0500
Howard
QS B64 (3915) 10.6.8. MacBookPro4,1 Intel Core 2 Due 2.4GHz, 4 GB RAM
> I'm on snow leapard and it says:
>
> 2011-11-17 10:06:06 -0500
And you’re having the problem where, on login, the “QS” stays on screen and typing in the interface appears to do nothing? And a manual restart after login fixes it?
> I get this:
>
> usma-m022-ccm:/ jeffvautin$ defaults read com.blacktree.Quicksilver "Last Update Check"
> 2012-03-01 12:16:40.756 defaults[3347:707]
> The domain/default pair of (/Users/jeffvautin/Library/Preferences/com.blacktree.Quicksilver.plist, Last Update Check) does not exist
>
> Not sure what why it's reporting that? I do definitely get the start on login problem.
That’s what I was hoping to see. I think I’ve fixed it for the next release. Until then, if you manually check for updates, it should set something for that value and fix your problem. You don’t have to install any updates if you don’t want to, just check for them.
> On Mar 1, 2012, at 9:50 AM, Howard Melman wrote:
>
>> I'm on snow leapard and it says:
>>
>> 2011-11-17 10:06:06 -0500
>
> And you’re having the problem where, on login, the “QS” stays on screen and typing in the interface appears to do nothing? And a manual restart after login fixes it?
No, I'm not having any such problems.
Howard
DN