gemwin: cant render on remote monitor
Brought to you by:
zmoelnig
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.
Anonymous
hmm, cannot reproduce in the following simplistic setup:
i will try with a real remote host next week.
I confirmed this bug here between 2 Ubuntu 14.04 64bit.
Last edit: IOhannes m zmölnig 2014-09-18
ok, i tried with the following setup:
nouveau
drivers)i915
driver)i then run the following:
this opens a window on the server, and (most of the times) immediately crashes with the following writte to the console:
i get the same crash with
[gemwin]
.all works fine when using Gem-0.93, so it's indeed a regression,
forgot to add that running e.g.
glxgears
with X-forwarding (thus displayed on the client) also gives similar errors:im running glxgears this way without any errors
with command trough ssh 'DISPLAY=:0 glxgears'
client: Quadro NVS 320M
server: GeForce GTX 660 Ti
booth of them is update arch linux with propietary nvidia drivers
and sometimes i can create a window on the server but nothing is rendered to it, and i get the following error for each frame:
the
libGL error
gave me the idea, that this problem might be related to context-sharing:libGL
errors)possible solution: do not try to create/use a shareable context when the display is set.
do you still have this error with a recent version of Gem (post [83419d] / 19.09.2014)
Related
Commit: [83419d]
i tested it fastly today in the morning with fresh git source, and it
was running fine, without any problems.
i was also able to open more render windows with the same content.
should i try to test it with version [83419d]
http://sourceforge.net/p/pd-gem/gem/ci/83419d017f3adb64ce52c384f3c1deb0ae2d602c
/ 19.09.2014 ??
k
On 22.09.2014 14:11, "IOhannes m zmölnig" wrote:
--
http://kubriel.servus.at
Related
Commit: [83419d]
setting this to "pending" as i'm sure this is not fully fixed yet
context-sharing has been disabled to prevent crashes on intel cards while it seems to work fine with nouveau.
Last edit: IOhannes m zmölnig 2014-09-23