Hi Charlie, It seems as if there may be problems with some of your catalog entries. In particular - one you have called 'user accounts' or something similar. Sending your crash log this way may indeed be helpful, thanks. Otherwise, a temporary fix could be to disable this (using an older version of Quicksilver).
Let me know either way :) On 24 October 2011 15:06, Charlie <[email protected]> wrote: > Clearing the caches did not work for me. The logs I get for the crash are > as follows: > > 10/24/11 9:57:08.713 AM Quicksilver: Prevented load of unidentified action > from bundle Keychain Module.qsplugin because the action's featureLevel (set > from its Info.plist) is higher than NSApp's current featureLevel. This is > not neccessarily an error. Sometimes this mechanism is used to prevent > unstable actions from loading. > 10/24/11 9:57:08.994 AM Quicksilver: Prevented load of unidentified action > from bundle Text Manipulation Actions.qsplugin because the action's > featureLevel (set from its Info.plist) is higher than NSApp's current > featureLevel. This is not neccessarily an error. Sometimes this mechanism is > used to prevent unstable actions from loading. > 10/24/11 9:57:08.996 AM Quicksilver: Prevented load of unidentified action > from bundle Chat Support.qsplugin because the action's featureLevel (set > from its Info.plist) is higher than NSApp's current featureLevel. This is > not neccessarily an error. Sometimes this mechanism is used to prevent > unstable actions from loading. > 10/24/11 9:57:08.997 AM Quicksilver: Prevented load of unidentified action > from bundle Chat Support.qsplugin because the action's featureLevel (set > from its Info.plist) is higher than NSApp's current featureLevel. This is > not neccessarily an error. Sometimes this mechanism is used to prevent > unstable actions from loading. > 10/24/11 9:57:21.906 AM Quicksilver: An error ocurred while scanning "User > Accounts": launch path not accessible > 10/24/11 9:57:39.591 AM com.apple.launchd.peruser.501: > ([0x0-0x9fc9fc].com.blacktree.Quicksilver[95737]) Job appears to have > crashed: Bus error: 10 > 10/24/11 9:57:42.327 AM ReportCrash: Saved crash report for > Quicksilver[95737] version ß61 (3900) to > /Users/MasterChief/Library/Logs/DiagnosticReports/Quicksilver_2011-10-24-095742_Cortana.crash > 10/24/11 9:57:42.528 AM ReportCrash: Removing excessive log: > file://localhost/Users/MasterChief/Library/Logs/DiagnosticReports/Quicksilver_2011-10-23-210429_Cortana.crash > > This 'batch' of errors pop up each time in Console. If you would like I can > send you the actual .crash file. > Thanks, > Charlie > > On Monday, October 24, 2011 at 9:49 AM, Patrick Robertson wrote: > > Hi there, > > Sorry to hear you're having problems. If you say you've moved/deleted the > PlugIns folder in ~/Library/Application Support/Quicksilver (go to it by > typing it into the "Go to folder" dialogue in Finder), then it is unlikely a > plugin problem. > > Perhaps a further cause to the problem could be the caches. Try removing > ~/Library/Caches/Quicksilver and restarting. > > If this doesn't work, then please take a look in Console.app for any log > reports. Thanks! > > On 24 October 2011 14:22, Charlie <[email protected]> wrote: > > Hi everyone, > > I've been experiencing a problem with the new Quicksilver B61 on my > 10.7.2 Machine. I've tried deleting the main .plist file > (com.quicksilver or something like that), and the Catalog, PlugIns, > Actions, Mnemonics, and Triggers plist files. But every time I open > QS, it crashes 5-10 seconds after launch. I can access the menus and > preferences, but it still crashes afterwards. I have also moved the > away the BezelHUD plugin, as one person said on these forums it was > causing a problem. But it is still crashing. I also tried disabling > Lion's app-resume for Quicksilver with Lion Tweaks, but it didn't make > any difference. Are there any plugins that have been acting up for > anyone else, or do I need to remove and add plugins one at a time? > > Thanks, > Charlie > > > >
