top of page
Search
jaylincadotte621c3

Using Xnest to start another Xorg session (Kubuntu): Best practices and recommendations



I am hoping someone can help me with this. I am using KDE4, trying to run a Xephyr session that will load KDM and allow me to login another desktop user in a window of my host KDE session. I have Xephyr installed, and I am using the command:




Using Xnest to start another Xorg session (Kubuntu)



But even before there was anything called Linux, people were running X applications on X terminals which were were indeed true terminals - incapable of running any applications locally. The protocol for provisioning such a device is called XDMCP. A quick google and I found this which describes how to provision the display manager - which is the X client providing the initial login capability. That article only mentions using xnest at the server (the thing with the screen and keyboard) but it's also possible to use the full display exclusively for the remote session with


When Xorg is run in rootless mode, Xorg logs are saved to /.local/share/xorg/Xorg.log. However, the stdout and stderr output from the Xorg session is not redirected to this log. To re-enable redirection, start Xorg with the -keeptty flag and redirect the stdout and stderr output to a file:


You have to leave the original X server running. You can start another X server on another tty. So, on a typical system, do ctrl+alt+f1, then log in and run startx -- :1. You should end up with another X session on reachable by ctrl+alt+f8.


Starting separate X for testing KWin: use a separate user, login to a text console and run"( X vt10 :1 -terminate &); sleep 5; DISPLAY=:1 xterm". This launches another X with DISPLAY=:1on virtual console 10 (Ctrl+Alt+F10) with xterm. Then it's normally possible to run just KWinor whole KDE with startkde (in which case it's a good idea to disable xterm from session managementin KControl->KDE components->Session manager).


>> why don't create another X server with xinit -- :1 and use VTs to switch between X servers ?>>Because it is annoying. Especially if want to switch to other X server often... you have to witness a bad "flicker".I use nested X for running programs that have a tendency to lock up my entire X session. I would recommend Xephyr instead of xnest though.


Try startx to start up the X server. startx is a script (it's installed by x11-apps/xinit) that executes an X session; that is, it starts the X server and some graphical applications on top of it. It decides which applications to run using the following logic:


Using the VGL Transport with XDMCP is conceptually similar to using the VGL Transport with a direct X11 connection. The major difference is that, rather than remotely displaying individual X windows to the 2D X server, XDMCP remotely displays a complete desktop session from the application server. Any applications that are started within this desktop session will run on the application server, not the client. Thus, vglconnect cannot be used in this case. Instead, it is necessary to start vglclient manually on the client machine. 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comentarios


bottom of page