Not really, no. As for the error message you got in Terminal, that usually just means that the launch agent is already loaded.
On Jan 3, 9:56 am, brian_t <[email protected]> wrote: > Hi Jon, > > thx for your input. I have read all your suggestions for fixing this > issue and I placed the new plist file in my home Library/ > LauncherAgents folder <user>/Library/... yet Quicksilver continues to > hang on my mba startup as had been described here. > > Any additional suggestions you may have? > > If it is useful hint, when I ran the Terminal command, I got the > message that there is nothing to load. > > thank you > > On Dec 2 2011, 9:54 pm, Jon Stovell <[email protected]> wrote: > > > > > > > > > Actually, you don't need to bother running the Terminal command. For > > the job this particular launch agent does, you don't need to. It > > should just run the next time you log in. > > > On Dec 2, 9:48 pm, Jon Stovell <[email protected]> wrote: > > > > As a workaround, try this method. It also has the added benefit of > > > making sure that QS is one of the very first things to load when you > > > log in, rather than one of the last. > > > > 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. > > > > On Dec 2, 8:03 am, mmcglynn <[email protected]> wrote: > > > > > I Have the same issue. Lion 10.7.2, 2.7 Ghz. > > > > > Shame, because I have used QS forever and don't want to let it go... > > > > > On Dec 1, 9:06 am, dw235 <[email protected]> wrote: > > > > > > Mac OS 10.7.2 - in preferences I've set Quicksilver to launch at > > > > > login. The initialization only seems to go so far. The large QS > > > > > freezes at approximately 25% opacity on fade out. The result is a > > > > > Quicksilver app that will open the QS interface when I hit the hotkey > > > > > but then won't take keyboard entry. It just stays blank. > > > > > > If I close Quicksilver and restart the application it then works as it > > > > > should. > > > > > > Thanks, > > > > > Dave.
