What is this about?
Docker has dozents of advantages and so is one of them to be able to use apps with a GUI isolated in a docker container. For example your Browser, TextEditor or something else.
Neatless to say that this will enable you to use linux / macOS software on your Windows host without messing with some hacks. Also this will prevent your maschine from having leftover dependencies when removing the app because it all stays wrapped up in a docker container.
Why would someone even try to do that?
I use Arch Linux on my private computer at home and Windows 10 at work. I wanted to be able to use the Evolution mail client and other handy linux apps on my Windows maschine.
So there are various tutorials on how to share an X11-Session from a linux host with a linux container. But:
Install VcXsrv and configure it
First of all, install VcXsrv Windows X Server. We could use Xming also, but the package for Windows hasn’t been updated since 2013. The easiest way would be to use Chocolatey which is by the way my favorite package manager for Windows!So fire up a powershell session and run:
Then run Xlaunch from the start menu and follow the initial configuration steps:Make sure to save to configuration file before you click finish!Save it to one of the following locations:
Create a Dockerfile
To use a simple example, create a new folder and place a Dockerfile with the following content in it:
FROM ubuntu:14.04 RUN apt-get update apt-get install.y firefox CMD /usr/bin/firefox
Build and run the container
For advanced docker users, here the quick commands:
docker build.t firefox. set-variable.name DISPLAY.value YOUR-IP:0.0 docker run.ti.-rm.e DISPLAY=DISPLAY firefox
With some explaination:
Now build the new container and label it firefox:
Because the container has its own localhost interface, we need to use the IP-address of our network adapter.Find out your IP address with
Find out your IP address in wsl(linux)
Set the environment variable (replace IP with yours):
set-variable.name DISPLAY.value 10.11.128.118:0.0
Set the environment variable (replace IP with yours – in WSL (linux))
export DISPLAY=192.168.0.102:0.0
Run the container: (in detached mode)
docker run.ti.-rm d.e DISPLAY=DISPLAY firefox
You should now see a firefox window:
This will work most other apps.
FROM debian:jessie RUN apt-get update \ apt-get install.y x11-apps ENV DISPLAY :0 CMD
run with input param with app name
docker run.d.-rm.e DISPLAY=DISPLAY xapps xeyes # will open xeyes docker run.d.-rm.e DISPLAY=DISPLAY xapps bitmap # will open bitmap app docker run.d.-rm.e DISPLAY=DISPLAY xapps oclock # will open clock app
FROM ubuntu:14.04 RUN apt-get.y update apt-get.y upgrade apt-get.y install nautilus apt-get.y install gedit VOLUME /home/sy VOLUME /root/.Xauthority:rw ENV env DISPLAY ENV net host ENTRYPOINT nautilus
docker build.t ubuntu-nautilus:0.0.1.
docker run.-rm.d.e DISPLAY=DISPLAY.v /home:/root/.Xauthority:rw ubuntu-nautilus:0.0.1
It is possible to run GUI applications in Linux containers on Windows host.Have a look at https://github.com/mviereck/x11docker 95.x11docker can run in MSYS2, Cygwin/X or WSL on Windows.Windows support is in master branch only and will be part of upcoming x11docker release 5.0.0.It needs X server VcXsrv 8 or Xwin in Cygwin/X.
have to validate the below steps too:
for me X0.hosts file is at “C:\Program Files\VcXsrv” directory.
Graphical displays not showing on WSL through VcXsrv
Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.
I use GAMA on WSL ( dcc3bf6a zip release (1.8.2), on Ubuntu 20.04.4 on Windows 11 ) and visualise it by exporting the display through VcXsrv, since Gama doesn’t work with WSLg. Everything works properly and simulations run, but the display parts are not “forwarded” properly :
Note that it works properly on the VM with a DE, so no issue with the build, but that the latency makes it unusable like that.
Lucas Grosjean
Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.
I tested GAMA on WSL ( c76d955d Linux deb with JDK release (1.8.2), on Ubuntu 20.04.3 on Windows 10 ), I’m exporting the display on Xming (https://sourceforge.net/projects/xming/).
Arthur S
Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.
It turns out that Gama somehow still uses WSLg, even when launched on a specific display relayed with VcXsrv/Xming. I have no clue of why it does, even when I durably export the display to specifically the one VcXsrv/Xming shows, with.bashrc. I thus shut down WSLg completely as a test, by editing the.wslconfig file, and it does work that way. So the problem indeed comes form WSLg (I’ve heard Wayland is known to cause issues).
The problem is that I use WSLg for a number of other programs, some of which don’t seem to work with an X server, and thus cannot durably have it off like that. Any way to durably have Gama display on a specific display? Otherwise a solution could be to write a Windows shell script that turns WSL off, edits the.wslconfig file, starts VcXsrv, turns wsl on again and then launches Gama, but what a hassle.
Arthur S
Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.
Let me add a clearer answer for who would need it. Note that the “load ui parts” as a note of my first email is no more, I think it was due to a conflict between WSLg and the export DISPLAY command in the Linux VM.
- Windows 11 with Ubuntu 20.04.4 on WSL2 (note that WSLg is embedded natively),
- Gama 1.8.2 dcc3bf6a zip release, with JDK or OpenJDK 17 (tested both with all scenarios, no differences),
- VcXsrv in scenario 2 (I did not test everything with XMing, but every time I did, I had the same behaviour than with VcXsrv),
- Windows’ Remote Desktop with xrdp in scenario 3 (setup like this, or something similar),
- Command to export display in Ubuntu (in.bashrc on scenario 2 and 3) : export DISPLAY=(cat /etc/resolv.conf | grep nameserver | awk ”):0 export LIBGL_ALWAYS_INDIRECT=true.
- A.wslconfig file lives in Windows user directory ( C:\Users\Me\ ), with the following : [wsl2] guiApplications=true / false.
guiApplications=true. VcXsrv not running and no DISPLAY forwarded by the VM. Gama launched from linux bash :./Gama.
- Gama launches, although not in a normal WSLg window.
- Java2D. runs, but displays nothing (first screenshot)
- OpenGL. crash
)
guiApplications=false. VcXsrv runs (options : multiple Windows, display 0 and.ac) and DISPLAY forwarded through the command mentioned above. Gama launched from linux bash :./Gama.
- Gama launches in an X window, but somehow the “Dark theme” option is greyed out.
- Java2D. works properly
- OpenGL. works properly (! @Lucas)
(The issue here being that I need to use WSLg for several other things, so this is not a durable solution)
xfce4 seen through xrdp and Remote Desktop. Gama launched by double clicking the binary file or with./Gama.
- Gama launches properly.
- Java2D. Runs
- OpenGL. Runs very slowly (note that this is a fresh Gama install, I did not mess with the settings and the INI)
I hope it is clearer. Now my hope would be to have WSLg working properly, since it is the handier. What could be the issue with these displays not showing?
Arthur S
Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.
Here’s the log for when it crashes with OpenGL (same as in case 1 in the previous mail, only with a fresh Debian install instead of Ubuntu and Gama with JDK, 1.8.2 RC 16152ad ). Again, Java2D runs but shows nothing and OpenGL crashes.
Vcxsrv Windows x server
The Windows Subsystem for Linux (WSL) was introduced by Microsoft in the Windows 10 Anniversary Update. It allows users to run a full Linux user space in Windows. It is a much nicer approach for most applications than Cygwin, or using a Linux VM. It is not an emulator either. Think of it as GNU/Linux/Windows (apologies to Richard Stallman). This guide starts off with Microsoft’s instructions for installing the WSL, and then goes a few steps further by describing how to run graphical Linux applications.
Prerequisites
Your PC must be running (at a minimum) a 64-bit version of Windows 10 with the Anniversary Update. The Creator’s Update is recommended.
To find your PC’s CPU architecture and Windows version/build number, open SettingsSystemAbout. Look for the System Type and Version fields respectively, as shown in the screenshot below.
If your build is below 14393, try checking for updates.
Enable the Windows Subsystem for Linux feature
You can enable the feature using a GUI or command-line interface.
GUI Method
- From the Start Menu, search for “Turn Windows features on or off” (type ‘turn’)
- Select Windows Subsystem for Linux
- Click OK
Command-line Method
Open a PowerShell prompt as administrator and run:
Enable-WindowsOptionalFeature.Online.FeatureName Microsoft-Windows-Subsystem-Linux
After enabling Windows Subsystem for Linux
Restart your computer when prompted.
It is important that you DO restart when prompted as some of the infrastructure which the Windows Subsystem for Linux requires can only be loaded during Windows’ boot-up sequence.
Install your Linux distribution of choice
Linux distributions can be installed using script, or by using the Microsoft Store links below:
After installation your Linux distribution will be located at: %localappdata%\lxss\ This directory is marked as a hidden system folder for a very good reason:
Avoid creating and/or modifying files in this location using Windows tools and apps! If you do, it is likely that your Linux files will be corrupted and data loss may occur. Please read this blog post for more information.
Create a UNIX user
The first time you launch a Linux distribution in Windows, you will be prompted to create a UNIX username and password.
This UNIX username and password has no relationship to your Windows username and password, and it can be different.
Use the same username that you use on remote Linux/UNIX systems, so you won’t need to specify it in individual configuration files, or every time you run commands like ssh. Read more.
Update the Linux distribution
After you have set up your user, update the OS.
To do this on Debian/Ubuntu based distributions, run:
sudo apt-get update sudo apt-get upgrade.y sudo apt-get upgrade.y sudo apt-get dist-upgrade.y sudo apt-get autoremove.y
Install common tools
The Debian distribution for WSL is minimal, so many packages that you might expect to be installed, such as ca-certificates, are not installed. To fix this, run:
sudo apt install.y ca-certificates findutils command-not-found vim nano curl openssh-client less screen apt-utils top htop whois git python3-pip
Accessing the Windows filesystem from WSL
Windows drives are mounted by their drive letters under /mnt. For example, your Windows C: drive is accessible via /mnt/c.
To make it easier to access your Windows user directory, consider adding a symbolic link, such as:
ln.s /mnt/c/Users/Sean/ ~/winhome
On Amazon WorkSpaces, this your Windows user directory is located in /mnt/d/Users.
That way, your Windows user directory is accessible from ~/winhome.
Graphical Applications
In order to run Linux GUI applications using WSL, you must:
Install VcXsrv
In order to run graphical Linux applications, you’ll need an X server.
VcXsrv is the only fully open source and up-do-date native X server for Windows. Download and run the latest installer, then locate the XLaunch shortcut in the Start Menu, and click it.
You will be greeted with a setup wizard. Accept the default options. On the last page of the wizard, click on the Save configuration button, and save the configuration file in %appdata%\Microsoft\Windows\Start Menu\Programs\Startup. so vcXsrv will launch at startup without asking about these options, then click on the Finish button.
You may receive a prompt to allow it through your firewall. Cancel/deny this request! Otherwise, other computers on your network could access the server.
A X icon will appear in your system tray.
Configure bash to use the local X server
- In bash run: Echo “export DISPLAY=localhost:0.0” ~/.bashrc
- To have the configuration changes take effect, restart bash, or run:. ~/.bashrc
Instructions for fish shell users
If you use fish instead of bash:
- Echo “set.x DISPLAY localhost:0.0” ~/.config/fish/config.fish
- To have the configuration changes take effect, restart fish, or run:. ~/.config/fish/config.fish
Test a graphical application
A new window will open, containing a pair of eyes that will follow your mouse movements.
Running remote GUI applications over SSH
To use a GUI application from a server, simply use the.X switch with the ssh command, for example:
ssh.X user@server.example.com
And run the GUI application from the shell prompt.
Using Visual Studio Code
Instead on installing the Linux version on Visual Studio Code on your WSL Linux distribution, install Visual Studio Code in Windows, and add the Remote Development extension pack.
After reloading Visual Studio Code, click on the green arrows at the bottom right corner of the window, and select Remote-WSL: New window action.
A new window will open with a Linux shell and editor. You will be able to edit files on the Linux file system.
Any Visual Studio Code extensions need to be installed in your Windows instance of Visual Studio Code first, and then on the WSL instance.
Recommended extensions for information security professionals include:
- AsciiDoc
- Autoit
- Beautify
- Bookmarks
- C/C
- C#
- Code Runner
- Code Spell Checker
- DotENV
- Edit CSV
- ESLint
- Excel Viewer
- Git History (Requires git)
- GitLens (Requires git)
- GnuPG-Tool (Requires GnuPG4Win on Windows, gpg on Mac or Linux)
- Haskell Syntax Highlighting
- Hexdump for VSCode
- HTML CSS Support
- ini for VSCode
- Markdown All in One
- markdownlint
- NDJSON Colorizer
- Output Colorizer
- Python
- Rainbow CSV
- REG
- REST Client
- reStructuredText
- tl;dr pages
- VBScript
- VSCode Ruby
- x86 and x86_64 Assembly
- XML Tools
- YAML
- YARA
References
This post was last modified on March 4, 2020 1:30 pm
Vcxsrv Windows x server
Xming is the leading X Window System Server for Microsoft Windows It is fully featured, lean, fast, simple to install and because it is standalone native Windows, easily made portable (not needing a machine-specific installation or access to the Windows registry).
Xming is totally secure when used with SSH and optionally includes an enhanced Plink SSH client and a portable PuTTY replacement package. Xming installers include executable code, and libraries, only built by me, Colin Harrison (Project Xming’s chief developer) this website is free of adverts, pop-ups and usage tracking of any kind, including cookies, and is hosted on machines only administered by me.
Mesa with GLX, or Microsoft WGL, provide interactive OpenGL 2D and 3D network transparent graphics rendering. High performance Windows AIGLX is available for graphics cards that support hardware-accelerated OpenGL.
PuTTY is Project Xming’s preferred and integrated X terminal emulator for Microsoft Windows: superseding any requirement for a cumbersome POSIX API compatibility layer and simulated directory mount points.
Xming is cross-compiled on Linux for Microsoft Windows, using MinGW-w64, mostly from canonical X.Org source code with my patches applied. It is kept current and secure with frequent updates from X.Org, XCB, XKB, FreeType, PThreads4W, Mesa, PuTTY and xorg group issues in freedesktop gitlab.
Windows Subsystem for Linux 1: Installing VcXrv X Server
Screenshots
| Xming -multiwindow mode on Windows 7 with five clients including a remote ParaView. | XDMCP on one X serverand an xlogo X client onanother. | XDMCP on one X server usedto access a remote Raspberry Piand a few clients on another. |
Releases
| XmingXming-x64 | 7.7.0.90 | Website Release | 2 May 2023 | MD5 signatures | 6.717.08 |
| Xming-portablePuTTYXming-portablePuTTY-x64 | 7.7.0.69 | Website Release | 2 Aug 2021 | MD5 signatures | 2.953.05 |
| See Donations for how to obtain a Donor Password. |
| Xming-fonts | 7.7.0.10 | Public Domain | 9 Aug 2016 | ed1a0ab53688615bfec88ab399ae5470 | 31.1 |
| XmingXming-mesa | 6.9.0.31 | Public Domain | 4 May 2007 | 4cd12b9bec0ae19b95584650bbaf534ae580debbf6110cfc4d8fcd20beb541c1 | 2.102.50 |
| Snapshot XmingSnapshot Xming-x64 | 7.7.0.91 | Work in progress | 27 May 2023 10:50 | Not yet released | 6.717.08 |
| See Donations for how to obtain a Donor Password. |
Windows installers
Xming installers make it child’s play to quickly install project components, interactively, with a few mouse clicks. They also install/uninstall, silently, using command line parameters.
Installers are for all Microsoft Windows editions no older than Windows 7 sp1 or Windows Server 2008 R2 sp1, but not ARM-based machines. Safety note: make sure you put an installer in an empty directory (or in one containing only other Project Xming installer files) before running it to avoid the possibility of a rogue file ‘hijack’. It is also wise to check the MD5 signatures of installers (I list a range of better checksums, than md5sum, for the installers in the download directory).
Xming
Optional extras are the Plink for Xming SSH client, XLaunch wizard, Tools and clients and GLX test clients. At least 24.8MB of free disk space is required. The x64 version is specific for 64-bit Windows x64. Note: use 32-bit Xming on Itanium/ia64.
Don’t install anywhere other than the default directory unless you really know what you are doing and install using right-click ‘Run as administrator’ if necessary.
OpenGL support is now provided by all Xming installers (Xming used to have separate builds and installers; with and without Mesa).
Install Desktop GUI for WSL | WSL Enable Desktop Guide
If you intend to use PuTTY: make sure you pick the correct Plink SSH client for use with Xming-portablePuTTY or original PuTTY i.e. there are two different Plink(s) in an Xming installer.
The Xming executable has an absolute minimum of fonts; the so-called built-ins. X clients usually need extra fonts to supplement these.
Xming-fonts
This additional installer provides standard core X fonts (which are usually required) and optional extended Bitstream Vera replacement fonts from DejaVue. At least 19.8MB of free disk space is required (for the default selection of fonts). Note: one Xming-fonts installer is common for both 32-bit and 64-bit Xming.
You should install Xming-fonts in the same directory you installed Xming. For an x64 (native 64-bit) installation on 64-bit Windows (x64) this defaults to.
C:\Program Files\Xming (also the default install directory on 32-bit Windows)
and for a native 32-bit WoW64 installation on 64-bit Windows (x64 or ia64) defaults to.
If you have installed both 32 and 64-bit Xming, on 64-bit Windows, you will need Xming-fonts in both the directories above i.e. sub-directory ‘fonts’ and contents.
I separated these fonts from Xming installers, above, since they have a high installed footprint, don’t change very often and modern X applications use client-side fonts instead via fontconfig. Xming-fonts are however needed by traditional X applications e.g. emacs. Since these standard X Window fonts tend to be ugly, you could use better TrueType fonts from your Microsoft system like this.
Instead of installing Xming-fonts, to provide core X fonts, you could use an X font server on your network.
Xming-portablePuTTY
This optional installer provides a fully portable replacement for PuTTY. At least 6.4MB of free disk space is required. You should not install portablePuTTY in the same directory you installed Xming: it is completely autonomous. The x64 version is specific for 64-bit Windows x64.
Don’t install anywhere other than the default directory unless you really know what you are doing and install using right-click ‘Run as administrator’ if necessary.
Xming-portablePuTTY works without requiring access to the Windows registry. The portable Plink executable incorporates the changes for the Plink for Xming SSH client.
Using Xming
| Adept operating systems have X11 Network Transparency, why not Microsoft Windows? | ||
What can you use Xming for?
All the normal X Window Server functions and some you might not have thought of
- Extend the magic of X11 Network Transparency to the ubiquitous Microsoft Desktop.
- Enable your Windows and Linux/Unix machines to integrate as a heterogeneous Private/Personal Cloud by using Xming and PuTTY. Be clear, not cloudy, about where your data is and who may access, or indeed, exploit it!
- Use your Microsoft computer as a thin client terminal to remote Linux/Unix machines
- Headless a Linux/Unix machine by removing its keyboard, mouse, monitor and maybe even its graphics card. Execute commands via PuTTY terminals, and display via Xming, over your network.
- Window’s drivers are often faster and more capable than Linux drivers for hardware-accelerated OpenGL enabled graphics cards. Xming can exploit the capabilities of an OpenGL enabled device, on a Windows machine, by use of its -wgl option in all modes including XDMCP (e.g. -query).
- You can display remote X clients directly on the Windows Desktop without running a remote Display Manager and so free up the resources used by that DM.
- Remote control your Raspberry Pi from Windows. Here is an example XLaunch file to display Midori for Raspbian jessie using Plink.
- Extend server-side X fonts to include any TrueType fonts on your Windows machine. These high quality fonts can be accessed, in situ, and added to the X server font list.
- Use Xming with portablePuTTY as a X server by copying both to a USB flash drive etc. Once made portable; no installed software or access to the Windows registry is needed.
- Old slow redundant Windows machines can be easily re-cycled into slick Linux machines and then accessed with Xming from your latest Windows computer. You will then get the best of both worlds, each with its own separate system architecture, security and philosophy. Xming elegantly and efficiently provides input control and graphical display for software that is running on the remote system.
- Use SSH and X-Forwarding in -multiwindow mode, instead of VNC, to reclaim precious resources (including desktop space) and facilitate cut-and-paste between Windows.
- You can run Xming on multiple monitors in many ways, e.g. if you have two monitors on a Windows machine, you could put the full remote Linux/Unix session on the second monitor using
Xming.query.nodecoration.screen 0 @2.clipboard.wgl
Xming.query.nodecoration.screen 0 @1.screen 1 @2 xinerama.clipboard
Manuals
This documentation is constantly being updated and may be incorrect for old versions. Don’t be put off, there needs to be a lot of it to cover the many uses for the X protocol, but for most users Xming installs quickly and can be started, by the XLaunch wizard, in just a few seconds.
Xming Manual. This doesn’t contain any X server commands. You can view all the applicable X server commands for Xming with -help or run this XLaunch file. These online X.Org Manual pages also give more detail on generic X server and X client options. Note: not all general options are logical for Windows or honoured by Xming.
Manuals are also available for XLaunch, Xmingrc, portablePuTTY, PuTTY, Xmon, the Run utility and command line use of Xming’s install and uninstall programs. All Tools and clients also have Xming manuals.
I also have a Recipe for setting up a headless Raspberry Pi and remote controlling it with PuTTY and Xming.
Getting started
Use XLaunch.find if all you want is to login to a remote machine and interact with its Display Manager via Microsoft Windows (using XDMCP). This is an elegant way to use an xserver but XDMCP mode is not very secure. It is safer to work via X-Forwarding and the SSH protocol, e.g. using PuTTY, on shared networks. Getting started with PuTTY X-Forwarding is described below and in more detail here.
A good tip: get PuTTY working first with Pageant, and use Saved Sessions, before using Xming/Xmingrc/XLaunch. Those Saved Sessions should only use the SSH-2 protocol, ‘Enable X11 forwarding’ and for the following example set ‘X display location’ to ‘localhost:0’.
To simply start Xming in -multiwindow mode from Command Prompt (the Windows cmd console)
“C:\Program Files\Xming\Xming.exe”.multiwindow.clipboard If you now need a Command Prompt: run it from Xming’s notification area icon menu. Many useful variables will then be inherited e.g. %CD% and %DISPLAY%
- You cannot run two X servers with the same display-number; use the :display-number option if you want multiple instances.
- On recent Windows versions: in order to easily use Xming’s notification area icon(s) you should set ‘Show icon and notifications’, for the Xming X server icon.
plink.ssh.2.X firefox either, with user@remote-host plink.load firefox or, with a PuTTY Saved Session name.
The XLaunch wizard
XLaunch is a wizard for simplifying the startup of an Xming X server. Its re-usable XML configuration files also act as mini-session managers. One X client can be selected for concurrent display from a local or remote machine. When remote, the X client is accessed securely via PuTTY or SSH.
Remote login using XDMCP is also provided as well as a host finder and chooser via the -find command and XPing button.
Also use XLaunch to just simply start the X server and then run several X clients later by hand, or from Xmingrc menu entries.
You can select the windowing mode, the way sessions are started and save the configuration for later reuse. An XLaunch configuration file can be just clicked to rerun saved settings without having to go through the wizard pages. Also automatic validation of configuration files against the XLaunch XML Schema Definition is selectable when starting the wizard. Additionally, automatic display-number (i.e. X server) allocation is provided.
Xmingrc and the X icon menu
You can configure the X toolbar icon menu (i.e. the right-click menu on Xming’s notification area icon), Windows icons, styles and system menus (i.e. the right-click menu on a Window’s title bar) using an Xmingrc file. Additionally, on the icon menu, a Host Finder is provided for listing, choosing and then accessing any responding XDMCP hosts on your network, as well as a log file viewer.
It is also possible to not hide the root window (Note: you may lose control of your desktop it you don’t ‘Hide Root Window’) and disable the ‘X11 PRIMARY Selection’ (the highlighted text copying mechanism with X clients).
I use this Xmingrc file to open X Window clients (singly or combined in session files), PuTTY and Command Prompt terminals, and to control access to the X server.
Remote Linux/Unix (and local Windows) programs can be run from Xmingrc menu items. Use of Plink is recommended when starting remote programs.
Xmingrc is a structured text file, so to avoid errors, study the installed default Xmingrc file (plus my Xmingrc file: see screenshots below).
Tools and clients
Many X.Org tools and clients have been ported to Microsoft Windows console (Windows CUI) applications and built modular using MinGW-w64.
| appres | atobm | bitmap | bmtoa | cxpm | editres | ico | listres |
| mkfontscale | oclock | setxkbmap | sxpm | twm | viewres | xauth | xcalc |
| xclipboard | xclock | xcutsel | xdpyinfo | xev | xeyes | xfontsel | xhost |
| xkbcomp | xkill | xlogo | xlsatoms | xlsclients | xlsfonts | xmessage | xmodmap |
| Xmon | xprop | xrandr | xrdb | xset | xsetroot | xwininfo |
Use the links in the table above to view Xming manuals for each entry. Note: xkbcomp is built without a Windows console (Windows GUI), and always installed, as it is used by Xming during X server startup. Also Xmon is sourced here not from X.Org.
xsetroot.cursor_name left_ptr.fg white.bg black.solid SteelBlue setxkbmap de.model pc105 xkbcomp.a :0 %TEMP%/desc.xkb Output the keyboard source, including Комментарии и мнения владельцев. xkill.frame Use in.multiwindow mode to select a client to close. xroot.geometry 50×5050050.color SteelBlue Useful with.rootless and some window managers.
xmonui | xmond Xmonui graphics front-end piped to an xmond console providing trace, for display 1 clients, while an X server is running display 0.
Using PuTTY with Xming is highly recommended as it provides SSH for Windows (typically used to log into remote Linux/Unix machines and execute commands) and Plink is especially useful.
Plink for Xming SSH client
Plink is a command line connection tool, similar to Linux/Unix ssh, that is used for automating secure remote operations from XLaunch and Xmingrc.
The Xming Plink SSH client is made with MinGW-w64 from patched PuTTY code. These modifications substitute Windows prompts for many console ones because XLaunch and Xming are built console free (GUI) and so stdout/stderr messages are hidden when Plink is spawned from them. Use as a replacement for Plink in ‘standard’ PuTTY (i.e. installers or binaries downloaded from Simon Tatham’s website). Note: Xming-portablePuTTY’s Plink incorporates the same changes but is not compatible with ‘standard’ PuTTY (there is a choice of two different Plink(s) in an Xming installer).
An example using Plink in a.js file to display a remote xterm.
The Run utility
The Run utility is an autonomous tool used to start Windows applications with a hidden attached console command window. This is the Manual for run. Its 32-bit binary, 64-bit binary and source code are supplied separately from Project Xming; and licensed GPLv2.
Here is an example Desktop Shortcut using run and Plink to display a remote konsole.
Donations
I greatly appreciate contributions towards improving Xming’s development and hosting resources. Plus, if you found Xming useful, a little thanks gives me the motivation to make it even better. Without updating equipment my Xming development can’t continue or advance, hence this hardware funding initiative.
If the button is faultily not setting £10 (GBP), email me and I’ll setup a PayPal money request instead or just send £10 to my PayPal account. Note: you don’t need a PayPal account to use the donation button and can pay with a credit/debit card.
By donating a minimum of £10 (GBP) you will get a Donor Password, sent by email, enabling download access to Xming Website Releases and Development Snapshots, for one year, and permission to use Xming Website Releases as a private individual. If you can’t donate money for legal reasons just send £10 to my PayPal account or email me for alternatives. My email address and PayPal account are the same: colin@xming.myzen.co.uk
See Terms and Conditions for license purchasing.
Support
I get so much email that I literally do not have time to answer it all. I regret this, but there’s nothing I can do about it. So if you can possibly avoid sending mail to me, I recommend you do so. In particular, support requests are probably better sent to newsgroups, or passed to a local expert if possible. Reports will ALWAYS be ignored by me if your complete Xming log file is not attached, if the report lacks detail and clarity and if you compare Xming with an X server not built directly from X.Org code. If a Plink problem I need the Plink command line used or a copy of your config.xlaunch file and if an Xmingrc problem I need a copy of your Xmingrc file! Tell me, upfront, if you are using virtual machine interfaces between Windows and Linux/Unix installed on the same machine, or starting Xming over RDP. Failing to follow instructions, or answer questions, will quickly lose any interest in your problem. I do however appreciate well formulated reports and suggestions; but read this website’s documentation first before asking a question. I don’t reply if the answer is already here.
Most issues, outside the scope of the Manuals, can be resolved by consulting the Trouble with Xming? documentation and Terms and Conditions.
Terms and Conditions
This URL links to the Project Xming’s TsCs including details on copyright, licensing, donations and purchases with many clarifications.
TsCs may change from time to time. It remains your responsibility to check them whenever you access this website or download, install and use any Project Xming software.
- Screenshots
- Releases
- Links and release status
The Xming website, documentation and images are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England Wales License. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Microsoft product screen shots: “Used with permission from Microsoft.” Copyright © 2005-2023 Colin Harrison All Rights Reserved
