[ opennx-Bugs-3536396 ] All tools hang/crash on Lion

[SourceForge.net <no...@so...>]

Bugs item #3536396, was opened at 2012-06-19 12:02
Message generated for change (Comment added) made by felfert
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=910152&aid=3536396&group_id=184662

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: All tools hang/crash on Lion

Initial Comment:
Trying to use the /Applications icons just results in a bouncing icon, nothing happens (doesn't even start up X11).

Starting X11 manually and launching the tools from /Library/OpenNx/bin starts the programs but when they try to save or just when the session is about to resume, they all show the same error (this from opennx):

2012-06-19 08:53:59.020 opennx[5908:3f03] CFURLCreateWithString was passed this invalid URL string: '/System/Library/CoreServices/CommonCocoaPanels.bundle' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.

I have a Lion Server box where this does not happen. I can't say what the difference would be. Both running the latest and greatest from apple (10.7.4).

----------------------------------------------------------------------

>Comment By: Fritz Elfert (felfert)
Date: 2012-06-29 13:57

Message:
Most likely there's some shared lib which is broken or missing.

The warning about CFURLCreateWithString has nothing to with it (it is
generated by wxWidgets) and it does not have any impact on functionality.

To figure out, which libraries are used by opennx on a particular system,
you can use the following command:

otool -L /Library/OpenNX/bin/opennx

Run this on both machines and you probably will find the culprit or at
least some differences which should give you a hint.

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2012-06-21 12:35

Message:
That error is not the crashing one. If you want me to capture a stack trace
from a core dump, just give me some instructions for doing so on osx.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=910152&aid=3536396&group_id=184662