Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Damage application graphs not working on OSX 10.8.5 #234

Closed
Insurgencygame opened this issue Dec 24, 2014 · 5 comments
Closed

Damage application graphs not working on OSX 10.8.5 #234

Insurgencygame opened this issue Dec 24, 2014 · 5 comments

Comments

@Insurgencygame
Copy link

This has been an ongoing issue for the last several releases.

It did work in v 120

I when you click on graphs from the menu there is no response

@blitzmann
Copy link
Collaborator

Are you running pyfa from source or from the release package?

From my testing on my OS X VM, I can open graphs when running from release (which includes python interpreter and all modules needed). If you are running from source, you should make sure you have proper modules installed. Take a look here and see if this helps at all: #40

@Insurgencygame
Copy link
Author

Hi I am running it from the release package.

I have not tried v1.9 yet

On Wed, Feb 4, 2015 at 2:46 AM, Ryan Holmes [email protected]
wrote:

Are you running pyfa from source or from the release package?

From my testing on my OS X VM, I can open graphs when running from release
(which includes python interpreter and all modules needed). If you are
running from source, you should make sure you have proper modules
installed. Take a look here and see if this helps at all: #40
#40


Reply to this email directly or view it on GitHub
#234 (comment).

@glguy
Copy link

glguy commented Jul 8, 2015

I had a problem like this on OS X after I moved the application bundle. Running pyfa with stderr visible showed that some font (iirc) paths had absolute paths registered for the original location where I'd executed pyfa.app and they were no longer working once I'd moved it into /Applications. In my case I fixed it by deleting the cache files associated with whatever library it was related to at the time.

(Just throwing this out there as a possibility)

@blitzmann
Copy link
Collaborator

Finally got a hackintosh going. @glguy seems to be right, although I have not been able to get it to print out an error yet. It seems to be somewhat difficult to reproduce - running it from Downloads and graphs open fine. Then if I move the app to the Applications folder, graphs don't work. If I move it to the desktop, again graphs don't work. Move it back to the Downloads and it works.

And then I tried the desktop again and it worked. Very odd. @glguy, you probably know more about osx than me. how did you get it to print stderr/out from inside the package? I try to run it from source and even through my interpreter through the .app itself, and it always works.

EDIT: And I just tried running it from the Downloads location, and graphs didn't work. >.<

@blitzmann
Copy link
Collaborator

Well, I got something: http://pastebin.com/fUECwM6A

Seems to suggest something about the fonts like @glguy reported. This leads to interesting questions such as why the hell does this only affect the graphing. Where are the cache files that need to be downloaded? And what exactly can be done to prevent this. Looking into it =)

edit: while googling around, I found this pyfa bug report from over two years ago: https://forums.eveonline.com/default.aspx?g=posts&m=3347476#post3347476 lol

edit 2: found it. matplotlib stores it's own cache of stuff. Simply deleting ~/.matplotlib/fontList.cache should resolve it. I'll look to see if we can disable the caching at the application level. If not, I'll put something about it on the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants