---
** [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:** Sat Sep 13, 2014 10:30 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.
hmm, cannot reproduce in the following simplistic setup:
$ xhost + $ ssh -X localhost localhost$ pd -lib Gem
-> [create :0.0, 1( -> [gemglxwindow]
i will try with a *real* remote host next week.
---
** [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:** Sat Sep 13, 2014 10:30 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.
I confirmed this bug here between 2 Ubuntu 14.04 64bit.
-- do it yourself http://antoine.villeret.free.fr
2014-09-14 9:26 GMT+02:00 "IOhannes m zmölnig" zmoelnig@users.sf.net:
hmm, cannot reproduce in the following simplistic setup:
$ xhost + $ ssh -X localhost localhost$ pd -lib Gem
-> [create :0.0, 1( -> [gemglxwindow]i will try with a *real* remote host next week.
- [bugs:#235] http://sourceforge.net/p/pd-gem/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:* Sat Sep 13, 2014 10:30 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.
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
I confirmed this bug here between 2 Ubuntu 14.04 64bit.
-- do it yourself http://antoine.villeret.free.fr
2014-09-14 9:26 GMT+02:00 "IOhannes m zmölnig" zmoelnig@users.sf.net:
hmm, cannot reproduce in the following simplistic setup:
$ xhost + $ ssh -X localhost localhost$ pd -lib Gem
-> [create :0.0, 1( -> [gemglxwindow]i will try with a *real* remote host next week.
- [bugs:#235] http://sourceforge.net/p/pd-gem/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:* Sat Sep 13, 2014 10:30 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.
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
---
** [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 http://sourceforge.net/p/pd-gem/bugs/
To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
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.
forgot to add that running e.g. `glxgears` with X-forwarding (thus displayed on the client) also gives similar errors:
$ glxgears libGL error: failed to authenticate magic 55 libGL error: failed to load driver: nouveau ^C $ DISPLAY=:0 glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. ^C
---
** [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:** Thu Sep 18, 2014 03:38 PM 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.
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
---
** [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:** Thu Sep 18, 2014 11:00 PM 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.
On 09/19/2014 12:09 PM, kubriel wrote:
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
could update Gem (>=83419d0) and see whether it is fixed?
gfdsamr IOhannes
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:
Xwin: BadMatch (invalid parameter attributes)
Xwin: GLXBadContext
Xwin: 0
---
** [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:** Thu Sep 18, 2014 03:42 PM 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.
the `libGL error` gave me the idea, that this problem might be related to context-sharing:
- Gem creates a *local* shareable context (producing the `libGL` errors) - and then tries to share this with the remote context (producing the rendering problems)
possible solution: do not try to create/use a shareable context when the display is set.
---
** [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:** Thu Sep 18, 2014 03:43 PM 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.
do you still have this error with a recent version of Gem (post [83419d] / 19.09.2014)
---
** [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:** Thu Sep 18, 2014 11:00 PM 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.
- **labels**: gemglxwindow --> gemglxwindow, remote - **status**: open --> pending-fixed - **assigned_to**: IOhannes m zmölnig - **Release**: unknown --> 0.94 - **Comment**:
setting this to "pending" as i'm sure this is not fully fixed yet; esp. context-sharing has been disabled to prevent crashes on intel cards while itseems to work with nouveau)
---
** [bugs:#235] gemwin: cant render on remote monitor**
**Status:** pending-fixed **OS:** linux **Release:** 0.94 **Labels:** gemglxwindow remote **Created:** Sat Sep 13, 2014 10:30 AM UTC by kubriel **Last Updated:** Mon Sep 22, 2014 12:10 PM UTC **Owner:** IOhannes m zmölnig
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.
-
"IOhannes m zmölnig" -
Antoine Villeret -
Antoine Villeret -
IOhannes m zmölnig -
kubriel