#137 tuxpaint won't run on MacOS X 10.6 (snow leopard)

v0.9.21
open
None
5
2012-10-03
2009-10-26
No

Just installed tuxpaint on my macbook, runing snow leopard. I installed the stamps too, and installed them into the application.

It crashed. The problem report dialog (attached) says:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000008a514900
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Discussion

  • secretlondon

    secretlondon - 2009-10-26

    crash report

     
  • secretlondon

    secretlondon - 2009-10-26

    This does it every time as well. Cannot get the program to start.

     
  • secretlondon

    secretlondon - 2009-10-27

    I've restarted my machine and I've deleted and installed without the stamps. Same thing - won't start.

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x000000008a514900
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

     
  • secretlondon

    secretlondon - 2009-10-27

    Presuming this is one for Martin.

     
  • William Kendrick

    Discussion ongoing on tuxpaint-devel. Seems to be related to the fontconfig issue (currently listed on the Known Issues page: http://www.tuxpaint.org/docs/known_issues/ ). Removing the ".fontconfig" file helps, although running other apps that require fontconfig (e.g., Inkscape) reintroduces the crash in Tux Paint.

     
  • William Kendrick

    Note: Assuming this crash does NOT occur on a system that doesn't have any other apps that utilize fontconfig (or simply that the user running Tux Paint has not run them). In other words, if Tux Paint crashes out-of-the-box on a new OS X install (without having run Inkscape, Gimp, etc. first), please let us know! (I'll bump the priority of this bug way up, in that case!) Thanks.

     
  • William Kendrick

    Please see #3143137 and let me know if the 'disable system fonts' solution there helps. Thanks!

     
  • William Kendrick

    Just received a report from a 10.6-using friend. They made sure "load system fonts" was disabled (per suggestion in #3143137), but the crash still occurs: "com.newbreedsoftware.tuxpaint 0x000d8910 FcStrListCreate + 51 (fcstr.c:1139)" (That's part of fontconfig.)

    I asked them to move their "~/.fontconfig/" folder out of the way (rename it), and try again, and this time Tux Paint launched. However, mouse position seemed offset compared to the pointer. (Investigating, may post another bug if it persists.)

    I asked them to move "~/.fontconfig/" back, and try the "tuxpaint-0.9.21-fctest.dmg" test version that Martin made available in late 2009. They said they'll try later today.

     
  • William Kendrick

    secretlondon: Can you confirm whether the 'system fonts' option helps? If so, I'd like to close this bug (though we should then investigate what other fonts should be blacklisted; see "int blacklisted = ..." in src/dirwalk.c)

     
  • wxl

    wxl - 2011-06-11

    Same situation here (after having Gimp installed-- also doesn't MPlayer OSX Extended use fontconfig too?), but removal of ~/.fontconfig/ fixed it all up.

     
  • William Kendrick

    I'm getting confused between all these OS X crash bugs that are related to fonts, but it sounds like diff. versions of fontconfig with incompatible cache formats. We mention deleting fontconfig's cache as a workaround here: http://www.tuxpaint.org/docs/known_issues/ ... but it also sounds like Martin put together a test version that may solve the problem.

    Where are we with that? Is there a code- or packaging-related solution we can include (or have already in CVS), and we can close this bug as "Fixed in 0.9.22"? Or will this forever be a "use this workaround" kind of bug?

    Thanks folks!

     
  • William Kendrick

    Any response? Does Martin's work-around help?

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks