I am using Mobaxterm(free version) on a windows 7 desktop to connect to a SUSE 11 Enterprise server on AWS. I am trying to display the xclock program on my xtrem client but I get an error saying 'Error: Can't open display:'. I have used the following syntax to set the display on the server:
export DISPLAY=<IP_addr>:0.0
SUSE 11 does not come with xclock by default so I had to download it and install it.
The hosts file on my PC has the localhost entry commented out, I am not sure if that would make a difference. Any ideas on how to debug this? Thanks.
Fixed!
Earlier I was just looking at xclock program's error msg. But when I scanned Mobaxterms client terminal's output, I found the following msg:
X11 forwarding request failed on channel 0
After some google hunting, found that one of the reasons this happens is when xauth package is not installed on the remote server. So, I checked and found that to be the case. This is the command I ran:
zypper in -name xorg*
This command tells you if the package is installed and if any dependencies exist. The package comes bundled with the xclock program. So zypper uninstalled the other xclock I had installed from another source and replaced it with the right version.
Link to package info:
https://www.suse.com/LinuxPackages/packageRouter.jsp?product=server&version=11&service_pack=&architecture=i386&package_name=xorg-x11-xauth
I also modified a file called /etc/ssh/sshd_config as root. The following lines need to be uncommented:
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
And X11UseLocalhost was changed to 'no'. I also changed my security group on AWS to let inbound traffic on port 6000. I am not sure if that matters.
After this mobaxterm automatically set my display parameter to localhost and I was able to run xclock on the remote server and see it on my local PC desktop.
Related
I'm trying to setup Pycharm professional edition on Fedora 25 x64.
After downloading the files and extracting them, I'm trying to run the script ./pycharm.sh in the bin directory.
This is the error I get:
Startup Error: Unable to detect graphics environment
I have checked my Java version
[root#localhost bin]# java -version
openjdk version "1.8.0_144"
OpenJDK Runtime Environment (build 1.8.0_144-b01)
OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)
I tried as well to set the DISPLAY variable:
export DISPLAY=:0
And this is what I get:
[root#localhost bin]# ./pycharm.sh
No protocol specified
Start Failed: Failed to initialize graphics environment
java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.
Any suggestions please ?
I had the same error installing in a clean Ubuntu 17.10, with Gnome on Wayland. At #mattdm's suggestion in your comments, I just opened a new terminal (as myself, not root) and it ran fine. I was running as root (after unpacking everything to /opt/) when I got the error.
mike#feynman:~$ /opt/pycharm/bin/pycharm.sh
Once you register/activate, just click the "* Configure v" pulldown from the welcome window, and select "Create Desktop Entry" to make it available from your OS menus. I'm assuming JetBrains made this work for whichever linux flavor you prefer.
Your X environment is not properly set (manually setting DISPLAY doesn't always work). Possibly because you're attempting this as root and root is not the owner of the graphics session. There could be other reasons, too.
You won't be able to run xclock or any other X app either in this situation - this is the clue that it's not a pycharm-related problem. For example if you ssh to localhost as root, not as the user currently logged in into the graphical session:
laptop:~ # ssh localhost
Password:
Last login: Thu Nov 23 22:19:06 2017 from localhost
Have a lot of fun...
laptop:~ # export DISPLAY=:0
laptop:~ # xclock
No protocol specified
Error: Can't open display: :0
laptop:~ # konsole
No protocol specified
Segmentation fault
laptop:~ # pycharm
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
No protocol specified
Start Failed: Failed to initialize graphics environment
You'd also see the same behaviour if you attempt the same in a text-mode console.
To address this issue open a new terminal from the graphics environment - if it is properly installed you should be able to run any of the X apps, including pycharm (or at least it shouldn't fail with that error).
In fedora
I have installed pycharm using fedy. This is worked.
Or change to a another user and try except root.
Phpstrom, Webstrom, PyCharm
Above three of them worked same like that.
In my case I am runing pycharm through docker, which is different host, run command xhost + , this would disable access control and client would be able to connect from any host.
Try running the program from another user instead of root. It worked for me.
I used OpenJDK instead of Oracle Java, because PyCharm hangs on Raspberry Pi.
In the file /etc/java-8-openjdk/accessibility.properties, disabling the entry assistive_technologies (simply comment out with a #) solved the issue.
This is what resolved my issue:
export DISPLAY='localhost:11'
I am struggling to set a desktop environment on a Centos 7.2 Server. I connect to the server in following way:-
Though putty ssh onto a jump box with my user Then from the jump box
ssh onto the Centos 7.2 server using my id
I have installed and tried below desktops:
Gnome Desktop --> Couldn't make it work (finally did a sudo yum groupremove of it)
Cinnamon --> still struggling
Have installed following packages:-
sudo yum --enablerepo=epel -y install cinnamon*
sudo yum install xorg*
I keep getting below error on startx:-
xauth: file /home/ma357577/.serverauth.4007 does not exist
(EE)
Fatal server error:
(EE) PAM authentication failed, cannot start X server.
Perhaps you do not have console ownership?
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console
I have tried to
rename /etc/pam.d/xserver (but in absence of this it falls back to /etc/pam.d/other hence is completely restricted)
and change the xserver file as below:-
\#%PAM-1.0
auth sufficient pam_rootok.so
\#auth required pam_console.so
auth sufficient pam_console.so nullok
account required pam_permit.so nullok
session optional pam_keyinit.so force revoke
none of the changes seem to work. Searched a lot on google but still stuck.
Eagerly seeking help on this! Thanks in advance.
Regards
Rohan
Check out this instruction Configuring VNC Server
You want to use xined service.
I'm trying to connect to a vagrant with a command vagrant ssh as instructed in the official vagrant documentation. Earlier I used older ubuntu as a virtual machine: config.vm.box = "hashicorp/precise32". During that time, issuing a command vagrant ssh did let me connect to the machine with just a username and password.
Now I changed the vagrant box to a newer one because I wanted newer nodejs. Currently, the box is: config.vm.box = "ubuntu/vivid32". Now with this box, if I run the vagrant, and try to connect to the machine with vagrant ssh, it does not let me, but instead it will prompt no kex alg. I read somewhere it has to do with authentication using keys. How could I connect to the new ubuntu with vagrant ssh? One option could be to just regularly connect to the box.
I just had this same issue for a couple days a finally found a way to fix this. I know its a old topic but just incase other people will experiance the same issue. this is how you can solve it:
edit your sshd_config and add:
KexAlgorithms diffie-hellman-group1-sha1
this is what fixed it for me (obviously restart ssh after that)
I guess something was done wrong in the box - when you look the history https://vagrantcloud.com/ubuntu/boxes/vivid32 there has been a few boxes released in short time. I just downloaded the box today and it is working as expected.
I suggest you update the box and you will get the latest version
vagrant box update --box ubuntu/vivid32
Checking for updates to 'ubuntu/vivid32'
Box 'ubuntu/vivid32' (v20151001.0.0) is the latest version
you should go to your vagrant using putty or anything
after that
sudo nano /etc/ssh/sshd_config
go to bottom line and put
KexAlgorithms diffie-hellman-group1-sha1
after that ctrl+o and enter and ctrl+x
go back to your windows and reload vagrant
then try
ssh vagrant#127.0.0.1 -p 2222
Hope this help you
my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.
I have a raspberry pi running arch linux connected to the TV and want to run commands on that screen by SSH'ing from my Ubuntu machine elsewhere.
I have tried running the command SSH -Y root# and starting xclock as a test. However I get the following error:
No protocol specified
Error: Can't open display: :0
I then tried running "export DISPLAY=:0" on the arch machine, but this doesn't solve the issue.
I have X running fine and can see it on the TV and I have edited the file /etc/ssh/ssh_config to allow X11 forwarding.
Anyone know what I am doing wrong?
Many thanks
The ArchLinux wiki has some good instructions on setting things up. I struggled for a while until I found them, but for me the key was to set up SSH forwarding within sshd_config (most distros seem to enable this by default, but Arch doesn't).
Once you've enabled X forwarding in SSHD, I also found it helpful to install the dummy video driver for Xorg ("pacman -S xf86-video-dummy"), which gets rid of irritating errors about missing the RANDR extension. This might not be necessary if you already have it running a real X server locally on the Pi - personally, I'm running mine completely headless.
I've found that I don't have to worry about setting up the DISPLAY variable, or xhost, when running with 'ssh -X' from an iMac. I'd expect Ubuntu to behave the same.
looks like an authentication problem. The answer used to be
xhost +
on the console of the X display. Might help.
You probably want to set
export DISPLAY=[IP_ADDRESS_OF_ARCH_BOX]:0
on your Ubuntu box, then when you run xclock from your Ubuntu box, it'll forward the screen to the Arch box.