Ticket 23190 - X11 forwarding not always working
Summary: X11 forwarding not always working
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Other (show other tickets)
Version: 25.05.1
Hardware: Linux Linux
: 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2025-07-09 07:56 MDT by Markus Köberl
Modified: 2025-07-09 08:02 MDT (History)
1 user (show)

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: Debian
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description Markus Köberl 2025-07-09 07:56:57 MDT
X11 forwarding is not working for relevant applications bat works for xclock

$ srun -w aim-gpu1 --x11 --pty xauth list
srun: job 257505 queued and waiting for resources
srun: job 257505 has been allocated resources
aim-gpu1/unix:60  MIT-MAGIC-COOKIE-1  578233d923f70762b6cb6f8db4ad7906

works:
$ srun -w aim-gpu1 --x11 --pty xclock
srun: job 257506 queued and waiting for resources
srun: job 257506 has been allocated resources

does not work:
$ srun -w aim-gpu1 --x11 --pty glxgears
srun: job 257507 queued and waiting for resources
srun: job 257507 has been allocated resources
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  151 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  28
  Current serial number in output stream:  29

works using ssh -X: 
$ ssh -X aim-gpu1 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
1364 frames in 5.0 seconds = 270.371 FPS


The same problem exists with Version 25.05.0

Probably related report on the mailing list:
https://groups.google.com/g/slurm-users/c/cD-hcSWKI04