Open mfalt opened 8 years ago
I'm pretty sure this is a problem far out of the control of either Immerse or PyPlot. It's what happens when you have multiple monolithic gui frameworks messing with program memory. Just out of curiosity... What backend is PyPlot using? (PyPlot.backend) Immerse is using Gtk.
On Mar 9, 2016, at 7:58 AM, Mattias Fält notifications@github.com wrote:
Julia crashes when using PyPlot with Immerse, PyPlot however seems to work fine with for example Gadfly. I'm running Julia v0.4.2. Minimum example:
import PyPlot import Immerse Immerse.plot(y=1:10) The same problem occurs with using. I get the following trace
/work/mattiasf/julia/julia: symbol lookup error: /lib64/libpangoft2-1.0.so.0: undefined symbol: FcWeightFromOpenType I have also experience the following error
GLib:ERROR:gmain.c:3078:g_main_dispatch: assertion failed: (source)
signal (6): Aborted gsignal at /lib64/libc.so.6 (unknown line) abort at /lib64/libc.so.6 (unknown line) g_assertion_message at /lib64/libglib-2.0.so.0 (unknown line) g_assertion_message_expr at /lib64/libglib-2.0.so.0 (unknown line) g_main_context_dispatch at /lib64/libglib-2.0.so.0 (unknown line) unknown function (ip: 0x7f6aae542e20) g_main_loop_run at /lib64/libglib-2.0.so.0 (unknown line) gtk_main at /lib64/libgtk-3.so (unknown line) anonymous at /local/home/mattiasf/.julia/v0.4/Gtk/src/events.jl:2 g_sigatom at /local/home/mattiasf/.julia/v0.4/Gtk/src/GLib/signals.jl:168 gtk_main at /local/home/mattiasf/.julia/v0.4/Gtk/src/events.jl:1 jlcall_gtk_main_22812 at (unknown line) jl_apply_generic at /work/mattiasf/julia/usr/bin/../lib/libjulia.so (unknown line) unknown function (ip: 0x7f6cdca7c944) unknown function (ip: (nil)) Aborted (core dumped) — Reply to this email directly or view it on GitHub.
It says
julia> PyPlot.backend
"qt4agg"
the Immerse README clearly states support for Gadfly, and has no mention of PyPlot.
Julia crashes when using PyPlot with Immerse, PyPlot however seems to work fine with for example Gadfly. I'm running Julia v0.4.2. (I updated julia to 0.4.4 and all the packages, and problem persists). Minimum example:
The same problem occurs with
using
. I get the following traceI have also experience the following error