albertzl / artisan

Automatically exported from code.google.com/p/artisan
GNU General Public License v3.0
0 stars 0 forks source link

Version 0.7.4 won't open after install with osx 10.9.1 - Error In Console #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Follow installation instructions
2. Double click to open Artisan

What is the expected output? What do you see instead?

- The program doesn't open and you get window in the attached image.

What version of the product are you using? On what operating system?

- Trying to install version 0.7.4 on OSX 10.9.1

Please provide any additional information below.

- Here is the error when I go to console:

com.apple.launchd.peruser.501[184]: (com.google.code.p.Artisan.118304[454]) 
Exited with code: 255

- Here is another error when trying to open it again:

Artisan[484]: 
GetDYLDEntryPointWithImage(/System/Library/Frameworks/AppKit.framework/Versions/
Current/AppKit,_NSCreateAppKitServicesMenu) failed.

Thanks.

Original issue reported on code.google.com by davejann...@gmail.com on 19 Feb 2014 at 4:31

Attachments:

GoogleCodeExporter commented 9 years ago
Artisan is known to run fine on OS X 10.9.1. I guess something is wrong on your 
system or the installation. Could you try to reinstall and ensure that the 
permissions in the enclosing folder are set correctly (you might use Disk 
Utilities repair permissions).

Original comment by luther.m...@gmail.com on 19 Feb 2014 at 7:06

GoogleCodeExporter commented 9 years ago
Thanks for the suggestions. I repaired permissions and did a fresh 
download/install but am getting a similar error message in Console:

Artisan Error
com.apple.launchd.peruser.501[199]: 
([0x0-0xf30f3].com.google.code.p.Artisan[2578]) Exited with code: 255

I did have version 0.5.5 previously installed and that was working. Is there 
something I need to do to upgrade? Some latent files that need to be deleted? 
Thanks - I really appreciate the help.

Original comment by davejann...@gmail.com on 19 Feb 2014 at 7:44

GoogleCodeExporter commented 9 years ago
It turned out, starting Artisan from the Terminal.app via

# cd <dir where Artisan is installed>
# cd Artisan.app/Contents/MacOS
# ./Artisan

that the underlying matplotlib had issues with some fonts installed in 
~/Library/Fonts on that machine. Error thrown looked like this

Traceback (most recent call last):
  File "/Applications/Artisan.app/Contents/Resources/__boot__.py", line 418, in <module>
    _run()
  File "/Applications/Artisan.app/Contents/Resources/__boot__.py", line 361, in _run
    exec(compile(source, path, 'exec'), globals(), globals())
  File "/Applications/Artisan.app/Contents/Resources/artisan.py", line 6, in <module>
    from artisanlib import main
  File "artisanlib/main.pyo", line 83, in <module>
  File "matplotlib/figure.pyo", line 34, in <module>
  File "matplotlib/colorbar.pyo", line 29, in <module>
  File "matplotlib/collections.pyo", line 23, in <module>
  File "matplotlib/backend_bases.pyo", line 50, in <module>
  File "matplotlib/textpath.pyo", line 11, in <module>
  File "matplotlib/font_manager.pyo", line 1356, in <module>
  File "matplotlib/font_manager.pyo", line 1341, in _rebuild
  File "matplotlib/font_manager.pyo", line 1004, in __init__
  File "matplotlib/font_manager.pyo", line 584, in createFontList
  File "matplotlib/font_manager.pyo", line 390, in ttfFontProperty
RuntimeError: No SFNT name table

Moving all fonts out of ~/Library/Fonts allowed Artisan to startup properly 
(creating the matplotlib font cache file). After this first successful startup, 
Artisan started up also after the fonts were moved back to ~/Library/Fonts.

Original comment by luther.m...@gmail.com on 19 Feb 2014 at 10:04

GoogleCodeExporter commented 9 years ago
FYI - I had same exact issue on mac 10.9.2.  When opening it just said "Artisan 
Error". Moved all fonts out of Library/Fonts temporarily and then Artisan 
opened.  Moved all fonts back into Library/Fonts and Artisan still opens.  
Thanks for the post!

Original comment by KimRodg...@gmail.com on 2 Nov 2014 at 9:30