Same problem, started today for me.

On Feb 10, 11:51 pm, Lvood <[email protected]> wrote:
> Hi,
>
> I'm using QS b5 (3841) on Mac OS 10.6.5.
>
> Quicksilver ist quite unstable at the moment, it did crash very often
> and suddenly.
> I removed the File Tags plugin and installed the Open Meta pluing
> instead,
> it seemed to be better.
>
> Now I accidently hit Cmd-Q when QS was open, so the dialog window went
> open which tells me that I have to press Cmd-Q longer to quit QS.
> This window did not disappear any more (even when QS was in the
> background), which became annoying, so I quit QS.
>
> Trying to launch it again was not possible, it always crashes directly
> after launching (I see the rotating QS logo and the shel window opens
> and then it quits and leaves me with a crash report. :-(
>
> I've trashed the content of the Caches directory (folder "Indexes") -
> no change.
> I've trashed the Shelf and Clipboard plist - no change.
>
> ---------------
>
> Process:         Quicksilver [36242]
> Path:            /Applications/_Software/Tools/Quicksilver.app/
> Contents/MacOS/Quicksilver
> Identifier:      com.blacktree.Quicksilver
> Version:         ß58 (3841)
> Code Type:       X86 (Native)
> Parent Process:  launchd [320]
>
> Date/Time:       2011-02-11 06:45:22.623 +0100
> OS Version:      Mac OS X 10.6.5 (10H574)
> Report Version:  6
>
> Exception Type:  EXC_BREAKPOINT (SIGTRAP)
> Exception Codes: 0x0000000000000002, 0x0000000000000000
> Crashed Thread:  3
>
> Application Specific Information:
> *** Terminating app due to uncaught exception
> 'NSInvalidArgumentException', reason: '-[QSApp frame]: unrecognized
> selector sent to instance 0x22b7c0'
> *** Call stack at first throw:
> (
>         0   CoreFoundation                      0x9895a6ba __raiseError + 410
>         1   libobjc.A.dylib                     0x90dc7509
> objc_exception_throw + 56
>         2   CoreFoundation                      0x989a790b -
> [NSObject(NSObject) doesNotRecognizeSelector:] + 187
>         3   CoreFoundation                      0x98900c36 ___forwarding___ +
> 950
>         4   CoreFoundation                      0x989a6cc2
> __forwarding_prep_1___ + 50
>         5   Quicksilver                         0x00010ab7 0x0 + 68279
>         6   CoreFoundation                      0x988e1793
> __CFXNotificationPost + 947
>         7   CoreFoundation                      0x988e119a
> _CFXNotificationPostNotification + 186
>         8   Foundation                          0x954a5384 -
> [NSNotificationCenter postNotificationName:object:userInfo:] + 128
>         9   Foundation                          0x954b2789 -
> [NSNotificationCenter postNotificationName:object:] + 56
>         10  QSCore                              0x000d0ffb -[QSTaskController
> updateTask:status:progress:] + 155
>         11  Foundation                          0x954b0bf0 -[NSThread main] +
> 45
>         12  Foundation                          0x954b0ba0 __NSThread__main__
> + 1499
>         13  libSystem.B.dylib                   0x9003185d _pthread_start +
> 345
>         14  libSystem.B.dylib                   0x900316e2 thread_start + 34
> )
>
> -------------
>
> Then, additionally I removed all the plugins from the PlugIns folder
> in Application Support/Quicksilver and could launch QS again.
> So it seems to be something with the plugins...
>
> Can anybody interpret the crash log and tell me what's the reason for
> that?
> According to the Crash Logs the problems started to days ago, so I
> tried to figure out what was changed with my notes and the Time
> Machine Backups, but I was not able to find out up to now...
>
> Concerning the plugins:
> Is it correct, that not necessarily all plugins which are in the
> PlugIns folder are really active? How can I find out which plugins
> were active at a certain time? With the plugins.plist?
>
> I fear I'll have to remove all preferences and start fresh again...
> but in those few hours without a working Quicksilver I learned how
> much my productivity depends on it!!
>
> Kind regards
>
> Martin

Reply via email to