![]() ![]() This is inherently protected against remote attacks and allows several local-only X11 protocol extensions which in turn allow for much more efficient graphics rendering. Instead, when you specify DISPLAY=:0.0 without any hostname, a UNIX socket is used to communicate with a local X server: specifically, the socket for display 0 is expected to be at /tmp/.X11-unix/X0. Modern Linux X servers don't generally listen on TCP ports unless you specifically enable that old-style, horribly insecure remote X11 access. So if you specify DISPLAY=localhost:0.0 and there is no X server listening on local TCP port 6000, it isn't going to work. If there is a hostname before the colon character, this connection is established as a TCP connection into a port number that is calculated as (display number + 6000). Paraview - or any other X11 GUI application for that matter - will attempt to connect to the X server as specified by the DISPLAY variable. X11 GUI system needs to write a few tiny files when starting up the X server and a few more when starting a user session, and if it cannot do that, it will usually behave very badly. ![]() If there is nothing in there, make sure your filesystem has some free space left. In your other question you said there is nothing in the logs - really? The main log file in X11 GUI matters would be /var/log/Xorg.0.log. With a VM, it might be easiest to establish basic networking, so that you can have a SSH connection to your VM in another window while trying to get the console X11 graphics working. ![]() The problem of Control-Alt-F1 not working might be as simple as Windows stealing all keystrokes that include Alt as menu shortcuts, so your keystroke might not even reach the VirtualBox intact, let alone the VM. ![]() If you use plain xinit, you must at least bring the mouse cursor on a window to focus it: if you can't do that, the situation might appear like all input is ignored. If you don't have your X11 mouse driver in order, the mouse cursor might be stuck in its default location. I think this is handled by xorg-x11-drv-evdev RPM package. A regular mouse cannot "jump" like that, but a tablet device can. VirtualBox throws a bit of a curve ball here, as it might be representing the mouse to the VM as a drawing tablet device, to better handle situations like when you move the mouse cursor out of the left side of the VM console window, move it around the window and then back in the right side. The problem of "no input" might be as simple as not having the correct drivers for mouse installed. I will now have to restart the machine.Īttempting to reinstall n the kernel build reveals "ERROR: Kernel configuration is invalid." There is a new behaviour, a GUI window with only xterm visible. I have run yum install xterm on an attempt to run xinit. Virtual machine manager: Oracle VM VirtualBox Manager 5.2.18.Machine operating system: Windows 7 Professional.What I would like to know is effectively what are the ways in which the system could be broken, what exactly to look for in the stack of technologies as evidence of faults, where any settings are stored, and what things may well be the key to getting this working. With Paraview or xhost or anything else on the command line no matter what I export the DISPLAY variable as, the result is: xhost: unable to open display "localhost:0.0" Not even Ctrl+Alt+F2 etc will switch to other terminals. However in the virtual machine, the GUI ignores all input and effectively all I can do is kill and restart the VM. Startx starts bringing up the gnome interface, with the 'first time install' window. I am not trying to use any remote tunneling, SSH etc, it is all local. I am attempting to run OpenFOAM 2.3.1 on an installation of CentOS 7, running inside a virtual machine hosted by Oracle VM VirtualBox on a Windows 7 machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |