Hello,

with QRecall version 1.2.0(55) beta (1.2.0.55), I see the Console log filling with messages of the form

29.12.11 15:45:26 QRecallScheduler[19600] *** Assertion failure in -[QuantumScheduler reiterateLoginState], /Users/james/Development/Projects/Quantum Recall/Scheduler/Source/QuantumScheduler.m:2401
29.12.11 15:45:26 com.apple.launchd.peruser.503[80] (com.qrecall.scheduler) Throttling respawn: Will start in 9 seconds
29.12.11 15:45:36 QRecallScheduler[19602] *** Assertion failure in -[QuantumScheduler reiterateLoginState], /Users/james/Development/Projects/Quantum Recall/Scheduler/Source/QuantumScheduler.m:2401
29.12.11 15:45:36 com.apple.launchd.peruser.503[80] (com.qrecall.scheduler) Throttling respawn: Will start in 9 seconds
29.12.11 15:45:46 QRecallScheduler[19608] *** Assertion failure in -[QuantumScheduler reiterateLoginState], /Users/james/Development/Projects/Quantum Recall/Scheduler/Source/QuantumScheduler.m:2401
29.12.11 15:45:46 com.apple.launchd.peruser.503[80] (com.qrecall.scheduler) Throttling respawn: Will start in 9 seconds

In QRecall's own log, I find the following (don't know if that's related):

Schedule 2011-12-29 15:49:46 Failure Unexpected problem; scheduler stopping immediately
Schedule 2011-12-29 15:49:46 sKnownLoginState not kLoginConditionLoggedIn or kLoginConditionLoggedOut
Schedule 2011-12-29 15:49:46 (debug) NSInternalInconsistencyException exception
Schedule 2011-12-29 15:49:46 (debug) backtrace
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff85a80766: 0x00007fff85a806d0 __exceptionPreprocess (/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation@0x00007fff859cf000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff8216df03: 0x00007fff8216ded6 objc_exception_throw (/usr/lib/libobjc.A.dylib@0x00007fff82164000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff85a805a7: 0x00007fff85a80540 +[NSException raise:format:arguments:] (/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation@0x00007fff859cf000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff8842d97a: 0x00007fff8842d8b4 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] (/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation@0x00007fff8835f000)
Schedule 2011-12-29 15:49:46 (debug) 0x00000001000084b7: 0x0000000000000000 unknown (/Library/Application Support/QRecall/QRecallScheduler@0x0000000100000000)
Schedule 2011-12-29 15:49:46 (debug) 0x00000001000054a0: 0x0000000000000000 unknown (/Library/Application Support/QRecall/QRecallScheduler@0x0000000100000000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff8838724c: 0x00007fff883870b8 __NSFireDelayedPerform (/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation@0x00007fff8835f000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff85a1cbb8: 0x00007fff85a1b260 __CFRunLoopRun (/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation@0x00007fff859cf000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff85a1ad8f: 0x00007fff85a1ab50 CFRunLoopRunSpecific (/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation@0x00007fff859cf000)
Schedule 2011-12-29 15:49:46 (debug) 0x00007fff883aab74: 0x00007fff883aaa66 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] (/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation@0x00007fff8835f000)
Schedule 2011-12-29 15:49:46 (debug) 0x00000001000020c0: 0x0000000000000000 unknown (/Library/Application Support/QRecall/QRecallScheduler@0x0000000100000000)
Schedule 2011-12-29 15:49:46 (debug) 0x0000000100001689: 0x0000000000000000 unknown (/Library/Application Support/QRecall/QRecallScheduler@0x0000000100000000)
Schedule 2011-12-29 15:49:46 (debug) 0x0000000100001534: 0x0000000000000000 unknown (/Library/Application Support/QRecall/QRecallScheduler@0x0000000100000000)
Schedule 2011-12-29 15:49:46 (debug) 0x0000000000000001: (unknown image)

I am running on OS X 10.6.8 Build 10K549.

What could be the issue here? Is this intended during beta phase, or is there something wrong with my install?

- Christian

Christian Roth wrote:What could be the issue here?

Something has mangled the preferences saved by the scheduler that it uses to restore its state when restarting. This is the second report I've had of this, but I still don't know what's going on. The saving and reading of preference values is handled by the operating system, and is usually quite reliable.

First, send me a diagnostic report (Help > Send report...). This will let me look at your preference setting files in hopes of understanding what's happening to them.

Next, open up a Terminal window, paste in the following command, and press Return.

defaults delete com.qrecall.scheduler QRSavedUserLogInState

That should delete the offending value, the scheduler will revert to using a default value, and everything should be running again. If it doesn't restart on its own, quit and relaunch QRecall. If there's still no joy, restart your system. If you encounter a new problem, send another diagnostic report.

Is this intended during beta phase

This assertion is only in the beta version of QRecall (the release version would have just shrugged it off and gone on). The beta versions of QRecall are far less tolerant of these kinds of inconsistencies.

Thanks James, just sent the Diagnostic Report your way and deleted the offending pref value. As soon as I had done that, the scheduler resumed operation of the pending actions.

If the issue shows up again, I hope I will be able to timely spot it so that maybe we can track everything that happened between now (the pref reset) and it happening again.

- Christian