Menu

#115 FlightGear 2.0 will not work on mac

WontFix
nobody
Mac (38)
2011-06-05
2010-04-01
Anonymous
No

Originally created by: simbab... (code.google.com)@gmail.com
Originally owned by: zakalawe@mac.com

What steps will reproduce the problem?
1. Open FlightGear on mac, atleast my mac
2. Click start flight
3. Then it crashes

What is the expected output? What do you see instead?
This is what the log said when it crashed each time:

Thu Apr  1 13:52:18 simons-macbook-pro-15.local fgfs[3482] <Error>:
kCGErrorIllegalArgument: CGSGetDisplayBounds (display 26c3a35e)
Thu Apr  1 13:52:18 simons-macbook-pro-15.local fgfs[3482] <Error>: kCGErrorFailure: Set a
breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Thu Apr  1 13:52:18 simons-macbook-pro-15.local fgfs[3482] <Error>:
kCGErrorIllegalArgument: CGSGetDisplayBounds (display 26c3a35e)

What version of the product are you using? On what operating system?
2.0, Mac osx Snow Leopard

Please provide any additional information below.

One of the pre released worked on my macbook pro but other than that the official release and
all other pre releases have not worked on my macbook pro or iMac.  The sim will literally not
start.  It will crash and Snow Leopard will tell me fgfs quit unexpectedly.  The gui launcher
remains up.

Cheers

Discussion

  • Anonymous

    Anonymous - 2010-04-14

    Originally posted by: simbab... (code.google.com)@gmail.com

    Anyone got an idea?

     
  • Anonymous

    Anonymous - 2010-11-24

    Originally posted by: zakalawe@mac.com

    Can you test a nightly build, or the Macflightgear.org developer release, and see if they behave any differently? Also, you should get a crash report window when fgfs crashes - if you could attach that log to this bug, that would be interesting. But try a new version first.

    Labels: Mac
    Cc: zakalawe

     
  • Anonymous

    Anonymous - 2010-12-12

    Originally posted by: zakalawe@mac.com

    I've had some feedback from simbabeat that he did eventually get 2.0 working on his Mac. I'd still like to trace down the underlying issue, but more data would be needed to do that. Closing for now.

    Status: WontFix

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Temp

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: WontFix

     

Log in to post a comment.

MongoDB Logo MongoDB