> Maybe next v. can check plugin compatibility on launch? It's crossed my mind. But like most things - I haven't had time to mention it. Can you post an issue at https://github.com/quicksilver/Quicksilver/issuesso everyone can see it? :)
On 19 April 2011 22:16, jweinstein <[email protected]> wrote: > It was a old Twitter plugin causing the crash on open. I cleared out > the plugins folder ad it worked. Maybe next v. can check plugin > compatibility on launch? > > On Apr 19, 2:37 am, Patrick Robertson <[email protected]> > wrote: > > It's most likely BezelHUD and UI Elements. > > > > If you're going to install any plugins, best to get them fromhttp:// > qsapp.com/plugins. It's not the same list as in QS. We'll be fixing > > this soon. > > > > ...very soon in fact. I have some good news to share :) > > > > On 19 April 2011 16:28, gord moore <[email protected]> wrote:> I > deleted all the plugins in that directory and the program started. I > > > installed the "recommended" plugins and it still started. I won't play > > > around with them at this time, but it is great to have it working > again! > > > > > frere > > > > > On Tue, Apr 19, 2011 at 12:14 AM, Patrick Robertson < > > > [email protected]> wrote: > > > > >> A few things that have been problematic with the new version are some > > >> plugins such as: > > > > >> BezelHUD, > > >> UI Elements, > > > > >> If you use either of these. Try deleting them from > ~/Library/Application > > >> Support/Quicksilver/Plugins and then restarting. > > >> Just make sure you have all the latest versions from > > >>http://qsapp.com/plugins > > > > >> You might like to check the few things in the FAQ: > > > > >>http://qsapp.com/wiki/FAQ > > > > >> On 19 April 2011 15:22, frere <[email protected]> wrote: > > > > >>> Yes, same problem. I see the "flash screen" as it starts, but then it > > >>> quits and is gone. I don't see the icon in the menu bar either. > > >>> Very puzzling! > > > > >>> frere > > > > >>> On Apr 18, 9:08 pm, jweinstein <[email protected]> wrote: > > >>> > Anyone else running into this issue? Tried to downgrade but didn't > > >>> > work either. So excited to see new development! >
