You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #643: Synergy "Starts" then "Stops" immediately

Kind bug
Product Synergy
When Created , updated
Status closed
Reporter Nathan Rowlett
Tags no tags

Description

I was using 3.5a2 fine and upgraded to a4. When I click the button to start synergy, it starts for a second and then stops with no explanation. The application does not report an error.

The console reports the following:

1/13/08 4:52:29 PM Synergy[1994] Error loading /Library/QuickTime/LiveType.component/Contents/MacOS/LiveType: dlopen(/Library/QuickTime/LiveType.component/Contents/MacOS/LiveType, 262): Library not loaded: /System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType 

 Referenced from: /Library/QuickTime/LiveType.component/Contents/MacOS/LiveType
 Reason: no suitable image found.  Did find:
/System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType: GC capability mismatch

1/13/08 4:52:32 PM com.apple.launchd[110] ([0x0-0xe40e4].org.wincent.Synergy[1994]) Exited abnormally: Bus error

I have Final Cut Pro Studio 5.1.4 (which is compatible with Leopard) installed. This includes LiveType. I may not have had this installed when I was using Synergy a2. Unfortunately I can go back to a2 to see if the bug is present there.

Comments

  1. Greg Hurrell

    The LiveType messages are unrelated to the crashes. You see those because LiveType doesn't support Garbage Collection, it tries to inject itself into every running process, and when it tries with Synergy (which is 100% Garbage Collected) it fails to inject itself.

    So those warnings are basically harmless and you'll see many such warnings, for many different applications, during these "early days" in the Leopard cycle. Eventually everything will be Garbage Collected but that it still some distance away.

    The crashes you're seeing are caused by NSAppleScript. See this bug report for more details:

    https://wincent.dev/a/support/bugs/show_bug.cgi?id=640

    Basically, a4 is much more stable than a2, but that one issue remains. If you try starting it a few times you'll see that it more or less runs indefinitely (at least it does in my experience). The NSAppleScript issue is the last one that I need to solve, I think, before getting back to full stability.

    Keep your eye on the nightly builds too:

    https://wincent.dev/s/nightlies/

    Basically, every time I fix a bug which has some kind of user-visible impact I generally upload a new nightly. If you browse the bug database you'll see some of the latest issues that have been fixed (yes, I know the bug database UI sucks; I have concrete plans to replace it as soon as I can).

Add a comment

Comments are now closed for this issue.

Menu