Archive:Getting Started/Run/Nested Session: Difference between revisions

Revision as of 07:58, 1 June 2011

Getting_Started/Run/Nested_Session

Nested KDE 4 Session

Instead of using a full-blown new X session for developing software you can use Xephyr to run your development build of KDE 4 in a session parallell to your normal working session.

You can also do this with xnest, but as xnest cannot handle extensions like Render many people prefer Xephyr.

Note

In some cases Xephyr/xnest will make the keyboard not work correctly because of bug:19365. The workaround is to run KDE on a standalone X as described below.

Assuming you setup your build enviroment following the instructions in Getting_Started/Build/Environment, simply put the following script in ~/kde/src/run_kde_nested.

!/bin/bash

Xephyr :1 -screen 1024x768 & sleep 3 export DISPLAY=:1 dbus-launch $KDEDIR/bin/startkde And make this file executable. Entering the ~/kde/src directory should setup the required enviroment variables, so do that before running the script.

You can also use Xephyr with KDM via the Xdmcp protocol and simply a new KDE 4 session to KDM.

On Kubuntu, you can enable it by changing

[Xdmcp]

Whether KDM should listen to incoming XDMCP requests.
Default is true

Enable=false

in /etc/kde3/kdm/kdmrc to

[Xdmcp]

Whether KDM should listen to incoming XDMCP requests.
Default is true

Enable=true

and adjust your /etc/kde3/kdm/Xaccess to allow your local machine access. Additionally you should make sure to set up a port blocking policy on all external interfaces for the Xdmcp port if you are doing this on a laptop or a PC in an untrusted environment.

If you are done, simply launch Xephyr:

Xephyr -query localhost :1 -host-cursor -screen 1024x768&

where -host-cursor tries to reuse the host's cursor and -screen sets the screen dimensions.

Note

If you get lots of refused connection errors, you might want to use the -ac option of Xephyr. When I tried to launch an application into the Xephyr instance, but I received 3-4 "No protocol specified", after finally saying "could not connect to X Server :1". The below code fixed it for me. It only happens when I am crossing users though, as opposed to doing it all in my main user.

Xephyr -ac :1&

Another option to try if you get lots of refused connection errors is you may need to grant assess to your kde-devel user to your X server. Do that using:

xhost +local:kde-devel

If you do not have Xephyr, you can also use Xnest:

Xnest -ac :1& export DISPLAY=:1

If you run into

"Call to lnusertemp failed (temporary directories full?).
 Check your installation."

try this:

mkdir /var/tmp/kde-devel-kde4

The above code assumes you work with user kde-devel.

@@ Line 6: / Line 6: @@
      |}
-Instead of using a full-blown new virtual X for developing software you can use Xephyr to embed your KDE 4 session into your working KDE 3 or other X11 environment.
+Instead of using a full-blown new X session for developing software you can use Xephyr to run your development build of KDE 4 in a session parallell to your normal working session.
 You can also do this with xnest, but as xnest cannot handle extensions like Render many people prefer Xephyr.
@@ Line 12: / Line 12: @@
 {{Note|1=In some cases Xephyr/xnest will make the keyboard not work correctly because of [https://bugs.freedesktop.org/show_bug.cgi?id=19365 bug:19365]. The workaround is to run KDE on a standalone X as described below.}}
-If you want to get a minimal KDE session up and running, just launch Xephyr (available in Kubuntu as xserver-xephyr; Gentoo users compile x11-base/xorg-server with USE="kdrive"):
+Assuming you setup your build enviroment following the instructions in [[Getting_Started/Build/Environment]], simply put the following script in {{path|~/kde/src/run_kde_nested}}.
- Xephyr :1 -extension GLX &
-You can now launch KDE:
 <code bash>
-su - $USER
+#!/bin/bash
+Xephyr :1 -screen 1024x768 &
+sleep 3
 export DISPLAY=:1
-/path/to/kde4/bin/startkde-modified &
+dbus-launch $KDEDIR/bin/startkde
-</code>
-startkde-modified is a copy of the startkde-script which includes the following lines on the top:
-<code bash>
-export KDEDIR=`kde4-config --prefix`
-export LD_LIBRARY_PATH=$KDEDIR/lib
-export PATH=$KDEDIR/bin/:$PATH
-export KDEHOME=~/.kde4
 </code>
+And make this file executable. Entering the {{path|~/kde/src}} directory should setup the required enviroment variables, so do that before running the script.
 You can also use Xephyr with KDM via the Xdmcp protocol and simply a new KDE 4 session to KDM.
@@ Line 65: / Line 54: @@
   Xephyr -ac :1&
-Another option to try if you get lots of refused connection errors is you may need to grant assess to your kde-devel user to your X server.  As root or using sudo execute:
+Another option to try if you get lots of refused connection errors is you may need to grant assess to your kde-devel user to your X server.  Do that using:
   xhost +local:kde-devel
@@ Line 75: / Line 64: @@
 <BR>
 -----
-{{improve}}
-[[User:Sping|Sping]] 00:25, 9 April 2007 (CEST)<BR>
-I use this for my start script ''nested_kde4.sh'':
- #! /bin/bash
- NESTED_KDE_DISPLAY_BACKUP=$DISPLAY
- export DISPLAY=:0
- Xephyr :1 -screen 1024x768 &
- export DISPLAY=:1
- $HOME/kde/bin/startkde-modified &
- export DISPLAY=${NESTED_KDE_DISPLAY_BACKUP}
 If you run into
@@ Line 97: / Line 75: @@
 The above code assumes you work with user ''kde-devel''.
-{{Note|In most cases you have to replace ''startkde-modified'' with ''startkde''}}
 -----
 [[Category:KDE4]]