-
Notifications
You must be signed in to change notification settings - Fork 44
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
Kiva doesn't work on Ubuntu 12.10 #74
Comments
This looks like a fun one... ;) Here's what I think might be happening. Emphasis on might. Kiva's agg statically links to freetype2 (specifically, v 2.3.12). During initialization, it calls module_init on what it thinks is one of its own internal modules, but instead calls into the system libfreetype. At that point, any number of crazy things could happen depending on how out of sync the two versions of freetype are. In this case, you got a segfault. Now, I'm not quite sure yet how to avoid calling into the system freetype. The freetype sources are a bit twisty. There are lots of symbols that get prefixed with Any takers? |
On weekdays I've tried to connect to my work machine via |
I have found solution, but don't know what exactly of this helps :
|
It is true that at times, deleting enable's build folder is required before On Mon, Oct 22, 2012 at 5:13 AM, Rustam Safin notifications@github.comwrote:
|
Today I've tried to upgrade my home laptop from 12.04 to 12.10. Kiva doesn't want to work with libfreetype6 v2.4.10 |
Bump! kiva/tests/dummy.py I have to admit, I did not investigate the relation to this bug further. |
@bunrpanck I think what you are seeing is related to #97 |
@jwiggins Thanks for pointing out that other issue. My symptoms surely look related, though a quick try using Ubuntu 12.10's gcc 4.6 did not solve the issues. Particularly, when running kiva/tests/dummy.py, I still get the following glibc complaint:
After this, python stops with SIGABRT, with the following backtrace:
Any ideas? |
@burnpanck That's definitely the freetype problem. |
@rahulporuri We good to close this issue? (I found this while looking for issues mentioning ubuntu while reviewing #889). |
This is technically still unresolved, but #553 is a more specific description (AFAICT). Although I'm pretty sure the interest in Ubuntu 12 is considerable less than when this issue was created. |
Ah I see, that makes sense
Yeah this is sort of what I had been thinking. Nonetheless, if it is unresolved keeping the issue open is reasonable |
Hello I've recently updated my ubuntu to 12.10 version. Applications that use Enable doesn't work.
Here is valgrind output of running some enable's example : http://pastebin.com/M3ZPeqpQ
The text was updated successfully, but these errors were encountered: