-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to use GUIs (xterm, xclock, IBM Installation Manager) #106
Comments
Hello @ajleonar, While the base VM does not have the X11 packages installed by default, this guidance shows how to install them. # dependencies for X server access
yum install -y libXtst libSM libXrender
# dependencies for GUI installation
yum install -y gtk2 gtk3 libXtst xorg-x11-fonts-Type1 mesa-libGL |
Hi @edburns Thanks for your help. I forwarded your response to the customer and they have some additional questions: "At https://learn.microsoft.com/en-us/azure/developer/java/migration/migrate-websphere-to-azure-vm-manually?tabs=in-bash%2Cwas-nd-v9#create-a-windows-vm-and-set-up-an-x-server, it creates a Windows VM as a jump box to run X11. It makes me feel the jump box is mandatory to X11 Linux in Azure. Could you reach to the IBM image and ask if they know any client using X11 by any chance? Is the jump box solution is a must?" |
Hi @edburns, I installed all the packages and still have the same error. Any further help? Thanks, |
Hello @felixxie99 I am Haixia from Ed's team. Could you please answer the following question to help me learn more about the problem.
I would suggest you try VcXsrv Windows X Server, I double confirmed it worked with RHEL 9 and RHEL 8. Make sure the following dependencies are installed.
Thank you. |
I am able to use X11 forwarding by defining the It didn't work with Public IP. So please make sure your Windows machine is in the same VNET with RHEL. Otherwise, use a jump box following the guidance. You can find the address from Xming log (Right click Xming icon, select View log). The following example is XdmcpRegisterConnection: newAddress 10.1.0.4.
|
xterm / xclock failing with the below errors:
[ ~]$ xclock
Error: Can't open display: localhost:10.0
[ ~]$ xterm
xterm: Xt error: Can't open display: localhost:10.0
Is X11 supported on this image?
The text was updated successfully, but these errors were encountered: