FFS for Mac v6.14 - FFS app opening randomly after succesful call by RTS

[htismaqe]

I installed 6.14 a couple of days ago and got everything setup and working. For some unknown reason, about 1 in 5 times RTS successfully calls FFS and FFS completes, it opens the actual FFS application and brings it to the forefront instead of silently terminating.

For example, in 5 hours this morning, RTS has called FFS 6 times. It has completed without errors 5 times. One time it completed successfully - no errors - and then FFS opened on my desktop.

[Zenju]

All that RTS does is to execute the command line, so maybe there is something about the command line in your scenario that is having these effects?

[htismaqe]

Is there a way to check? What's mystifying is that it happens so randomly. It happened only once yesterday, despite RTS calling FFS to run over 20 times.

[Zenju]

What is the command line you entered in RTS?

[htismaqe]

"/Applications/FreeFileSync.app/Contents/MacOS/FreeFileSync" "/Users/XXX/Library/Scripts/BatchRun.ffs_batch"


[Zenju]

"/Applications/FreeFileSync.app/Contents/MacOS/FreeFileSync" "/Users/XXX/Library/Scripts/BatchRun.ffs_batch"


Looks fine. All I can tell from FFS's side is that whatever started FFS in GUI mode, it was not this command line. Even if the ffs_batch file were temporarily unavailable or there was a failure when loading the file, FFS would show an error message rather than ignore the issue and start anyway. The next step would be to find some way to log the process executions on OS X and see what started this stray FFS GUI process.

[htismaqe]

I'll have to wait for it to happen again. I can get some info on processes from Console but without having a reference point, it's like finding a needle in a haystack.

[htismaqe]

I was ripping a CD this morning which causes the sync process to run several times (once as each track file is written to my music folder). The CD had 14 tracks and after 13, FFS opened. Unfortunately, the log output is not real helpful I'm afraid.

This is what the log entry looks like:

3/2/15 9:39:37.162 AM FreeFileSync[2460]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.10.2. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 0   CarbonCore                          0x00007fff8e723d9b ___Gestalt_SystemVersion_block_invoke + 113
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 1   libdispatch.dylib                   0x00007fff8ca43c13 _dispatch_client_callout + 8
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 2   libdispatch.dylib                   0x00007fff8ca43b26 dispatch_once_f + 117
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 3   CarbonCore                          0x00007fff8e6cc3ca _Gestalt_SystemVersion + 987
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 4   CarbonCore                          0x00007fff8e6cbfb7 Gestalt + 144
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 5   FreeFileSync                        0x000000010b1c65ff _Z19UMAGetSystemVersionv + 31
3/2/15 9:39:37.163 AM FreeFileSync[2460]: 6   FreeFileSync                        0x000000010afa0d1f _Z14wxDisplayDepthv + 15
3/2/15 9:39:38.331 AM FreeFileSync[2460]: setting security information: Operation not permitted


I do notice an abundance of those "Operation not permitted" errors around the same time as it occurred.