x11 was working until I updated to the latest version of RDM (2019.1.3.0 64-bit).
I haven't changed any settings on our servers, nor on my local XMing server.
Here are my current settings:
Enable X11 Forwarding -> True
X display location -> localhost:0.0
Protocol -> MIT-Magic-Cookie-1
X authority file for local display ->
Using the plain putty client with the same settings it works (xclock runs, no errors).
Currently RDM throws a "/usr/bin/xauth: (stdin):2: bad "add" command line" when connecting to the same server.
Hi,
Could you send me the logs with verbose on? The "Verbose" check box is in the "Advanced" tab. You'll also need to check "Enable logging" and specify a "Log path" and set "Log mode" to "Event". Connect and attempt to launch an X11 Application and post the resulting logs.
Regards
Denis Vincent
I should specify that I'm using RDM free, and I don't see any logging options.
Can you clarify where I should see the logging options at?
The logging options are in the "Advanced" tab also, 4th option below "Verbose".
Denis Vincent
Thanks.
See attached.
x11forwarding.log
Hi,
I have located the problem. It might take me a while to fix the bug, I hope to have it fixed by the end of next week.
Regards
Denis Vincent
I appreciate it. In the mean-time I've switched over to using the legacy terminal.
Hello,
The issue you reported has been resolved by our engineering department. The fix will be available in the next release of RDM.
Please consult our release notes to learn more about the latest improvements and bugs fixes in RDM - https://remotedesktopmanager.com/release-notes
Best regards,
David Grandolfo
Hi,
I got the same problem using RDM 2021.2.21.0 using ssh shell with xlaunch got this error:
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-b07)
OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)
Exception in thread "main" java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)
at java.awt.Window.<init>(Window.java:536)
at java.awt.Frame.<init>(Frame.java:420)
at java.awt.Frame.<init>(Frame.java:385)
at javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1763)
at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1838)
at javax.swing.JWindow.<init>(JWindow.java:187)
at javax.swing.JWindow.<init>(JWindow.java:139)
at com.steeleye.LifeKeeper.client.C_MainFrame$18.<init>(C_MainFrame.java:1048)
at com.steeleye.LifeKeeper.client.C_MainFrame.showSplash(C_MainFrame.java:1048)
at com.steeleye.LifeKeeper.client.C_MainFrame.main(C_MainFrame.java:1008)
working corretly using putty.
any idea?
Regards
Hello,
After having a discussion on that matter with our Engineering Department, they have confirmed that this issue has been fixed internally and that this will be corrected in RDM 2021.2.24.0.
Best regards,
James Lafleur
Nice Thanks!