ok, i tried with the following setup:
- client: nVidia Geforce 7800 GTX (with `nouveau` drivers) - server: Intel HD 4000 (with `i915` driver)
i then run the following:
~~~~~bash client$ ssh -X server server$ cd .../Gem server$ pd -path abstractions:. -> [create :0( -> [gemglxwindow] ~~~~~
this opens a window on the server, and (most of the times) immediately *crashes* with the following writte to the console:
~~~~~ libGL error: failed to authenticate magic 49 libGL error: failed to load driver: nouveau GLEW version 1.10.0 error: Xwin: GLXBadContext
error: Xwin: GLXBadContext
error: Xwin: 0
error: Xwin: GLXBadContext
[xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pd: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Pd: signal 6 ~~~~~
i get the same crash with `[gemwin]`.
all works fine when using Gem-0.93, so it's indeed a regression,
---
** [bugs:#235] gemwin: cant render on remote monitor**
**Status:** open **OS:** linux **Release:** unknown **Labels:** gemglxwindow **Created:** Sat Sep 13, 2014 10:30 AM UTC by kubriel **Last Updated:** Sun Sep 14, 2014 07:26 AM UTC **Owner:** nobody
usually i was using xforwarding to display patch on my laptop, but running pd and gem rendering on big machine. i used [create :0( for this. looks like [gemglxwindow] does not take name of the screen..
"[gemglxwindow]: unable to switch to current window (do you have one?), cannot render!"
yes, i have one.
---
Sent from sourceforge.net because gem-dev@lists.iem.at is subscribed to https://sourceforge.net/p/pd-gem/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.