From: Stefan Dirsch <sndirsch@suse.de>
To: dri-devel@lists.freedesktop.org
Subject: Weird behaviour (GLX extension missing) in X11 forwarding since xorg-server 1.20 ...
Date: Wed, 21 Aug 2019 16:26:32 +0200 [thread overview]
Message-ID: <20190821142632.GA3351@suse.de> (raw)
Hi
I'm wondering, whether this happens to everybody using xorg-server 1.20
(1.20.3 in my case).
When using X11 forwarding via ssh
ssh -X <remotemachine>
(DISPLAY=localhost:10.0)
the list of available extensions when running xdpyinfo is limited to
[...]
number of extensions: 2
BIG-REQUESTS
XC-MISC
default screen number: 0
When running xdpyinfo local (DISPLAY=:0) it's complete:
[...]
number of extensions: 29
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
XVideo-MotionCompensation
default screen number: 0
[...]
This happens even if you ssh to the same local machine. Can anybody reproduce
this? Is this a known issue. Since now GLX extension is missing I can't run
any GL application any longer via ssh ...
This still works with xorg-server 1.19 for me.
Thanks,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
----------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
----------------------------------------------------------------
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2019-08-21 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190821142632.GA3351@suse.de \
--to=sndirsch@suse.de \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.