On Jul 31, 2012, at 11:10 AM, Christopher Harwood <[email protected]> wrote:
> I had time to test one plugin active at a time, but won't be able to test > combinations of plugins for awhile. No one plugin seems to cause the error > on its own when QS launches. When all my plugins are active, the batch of > errors appears on launch and then intermittently afterward (including any > time that I run the script I was working on). Thanks. The only one you had that I didn’t was RTM, so it was easy enough to install that one. I still don’t get the log messages though. On the GitHub issue, one user tracked it down to the Services Menu plug-in. In any case, anything that happens on launch and periodically after makes me thing it’s related to catalog scanning. That code does a lot of autorelease related stuff, and it just so happens that it was updated slightly to prevent a crash. It will most likely be in the next release and will hopefully take care of this. It might help us to know now, so if you’re willing to run a test build, I can get you one. > Incidentally, the Services Menu plugin seems to trigger errors with FUSE on > QS launch. I've attached a log. This batch of errors also occurred > periodically throughout the tests (including when the Services Menu plugin > was not active) so I think the plug in is just triggering a bug in FUSE > itself. Not sure about this one. Do you have any catalog entries that might be scanning things stored on FUSE filesystems? > Spotlight Plugin (forgot what this is for, too.) Well, unlike the past, it has documentation to explain that now. :-) You can get to it from the plug-in’s info panel in the prefs. -- Rob McBroom <http://www.skurfer.com/> -- You received this message because you are subscribed to the Google Groups Quicksilver group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/blacktree-quicksilver?hl=en
