I too encountered this. It appeared after I was trying out the "Show Source in Catalog" builtin action where it takes you to the catalog source for whatever item you have in pane one. >From there I navigated "up" (up-arrow) into Quicksilver itself, then interested in what Quicksilver itself would offer as it should have loads of virtual resources I soon found myself trapped in a vicious circle where one step ended up being the last of the next so that I was navigating in circles.
I also remember almost all entries had "Catalog" somehwhere in them. After restarting QS it showed exactly the symptoms described. It would seem that something in my behaviour caused the Catalog indexing to get corrupted... André On 15 Sep., 03:25, Eris <[email protected]> wrote: > I've encountered this as well, but I'm not sure if there is a solution > yet. Before I finished reading your entry, I was going to suggest > precisely the solution you discovered. The good news is that for me it > has been a rare occurrence. If it happens again, let us know what > plugins you have installed and I'll compare them with mine. > > On Sep 14, 11:06 am, qff <[email protected]> wrote: > > > > > I'm sitting with a clean Snow Leopard install and Quicksilver B56a7 > > (3825). I'm new to OSX/Mac and thereby also new to Quicksilver. At > > first Quicksilver worked fine and I was happily opening applications > > and doing simple tasks via Quicksilver. But yesterday after a reboot > > there was no longer any "real" entries in the Quicksilver catalog - > > all I had was a long list of entries (some of them application names - > > though without their proper icon) appended by "(Catalog)"; entries > > which could not be run. I tried to disable and re-enable scanning of > > the Applications folder and rescan the catalogs - nothing helped. > > Today I cleared the ~Library/Caches/Quicksilver/Entries folder and > > everything is back to normal - the applications, their icons and the > > run command are back. > > > Just wanted to let you know of this (to me) strange behavior. And > > furthermore I would like to avoid this in the future - what could have > > caused it? > > > Malthe :)
