jay gamel wrote:Not a single one in a single place indicated. Why, then does the problem persist?
Well, there must be one somewhere, or at least there was one somewhere.
First, let me remind you to restart. The message that you're getting is from launchd, the primary launch services daemon that controls the running and maintenance of most background processes in Mac OS X. launchd is configured entirely by the presence of .plist documents installed in /Library/LaunchDaemons, /Library/LaunchAgents, and/or ~/Library/LaunchAgents (at least for user installable processes, there are more of these folders in /System).
Removing the .plist for a service isn't sufficient to stop it. After removing the .plist document, launchd either needs to be restarted (which basically means you need to restart your OS), or you can use a command like this in the Terminal:
launchctl stop com.qrecall.monitor
If neither the stop command or restarting your computer solves the problem, then you haven't eliminated all of the QRecall related .plist documents. launchd runs on these configuration documents, and it doesn't start services that don't have a .plist configuration document somewhere. You'll probably find the errant file in the ~/Library/LaunchAgents folder of some other user. If you find them in another user account, trash them and restart.