Difference between revisions of "Archive:Getting Started/Run/Full Session"

Jump to: navigation, search
(set all necessary environment variables, make sure dbus sees them, and describe how to fix polkit)
(explain the method that gets most stuff working first)
Line 1: Line 1:
 
= Full KDE 4 session =
 
= Full KDE 4 session =
 
To run a full KDE 4 desktop environment session, you can either start it from the command line as you normally would, with something like this:
 
 
X :1 & export DISPLAY=:1
 
$HOME/startkde-wrapper
 
 
{{Note|If the X server refuses the connection saying something like: <tt>Xlib: connection to ":1.0" refused by server</tt>, try <tt>X -ac :1</tt> instead.}}
 
 
{{path|startkde-wrapper}} sets some environment variables which are required to make KDE run properly in a nun-/usr environment:
 
<syntaxhighlight lang="bash">
 
#!/bin/sh
 
export KDEDIR="$HOME/kde"
 
 
AddToPath() {
 
        eval "export $1=$2\${$1+:\$$1}" # prepend to existing path, if there is one
 
}
 
 
AddToPath PATH "$KDEDIR/bin"
 
AddToPath LD_LIBRARY_PATH "$KDEDIR/lib"
 
AddToPath QT_PLUGIN_PATH "$KDEDIR/lib/kde4/plugins:$KDEDIR/lib/qt4/plugins"
 
AddToPath PKG_CONFIG_PATH "$KDEDIR/lib/pkgconfig"
 
AddToPath CMAKE_PREFIX_PATH "$KDEDIR"
 
export XDG_DATA_DIRS="$KDEDIR/share:/usr/share"
 
export XDG_CONFIG_DIRS="$KDEDIR/etc/xdg:/etc/xdg"
 
export KDEDIRS="$KDEDIR"
 
exec startkde "$@"
 
</syntaxhighlight>
 
 
Replace {{path|$HOME/kde}} in the example above with the prefix you are installing KDE4 into. If you want to, also add "export KDEHOME=$HOME/.kde4" to change the path KDE configuration is stored in.
 
  
 
== Using the login manager (a) ==
 
== Using the login manager (a) ==
  
Alternatively, you can can add it to your login manager. To make sure that even the daemons started by the X login process use the correct files, create a file called {{path|.xsessionrc}} in your home folder, which sets up the environment:
+
You can change your configuration so a normal login using your login manager (KDM, lightdm, whatever you choose) will end up starting your self-compiled KDE. To make sure that even the daemons started by the X login process (most notably dbus) use the correct files, create a file called {{path|.xsessionrc}} in your home folder, which sets up the environment:
  
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
Line 51: Line 22:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Replace {{path|$HOME/kde}} in the example above with the prefix you are installing KDE4 into. Finally, create a file called {{path|$HOME/.xsession}} which actually starts KDE:
+
Replace {{path|$HOME/kde}} in the example above with the prefix you are installing KDE4 into. If you want to, also add "export KDEHOME=$HOME/.kde4" to change the path KDE configuration is stored in. Finally, create a file called {{path|$HOME/.xsession}} which actually starts KDE:
  
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
Line 64: Line 35:
 
<busconfig>
 
<busconfig>
  
   <includedir>/home/usr/kde/etc/dbus-1/system.d</includedir>
+
   <includedir>/home/user/kde/etc/dbus-1/system.d</includedir>
   <servicedir>/home/usr/kde/share/dbus-1/system-services</servicedir>
+
   <servicedir>/home/user/kde/share/dbus-1/system-services</servicedir>
  
 
</busconfig>
 
</busconfig>
Line 82: Line 53:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Using the {{path|startkde-wrapper}} from the top of this page.
+
{{path|startkde-wrapper}} sets some environment variables which are required to make KDE run properly in a non-/usr environment:
 +
<syntaxhighlight lang="bash">
 +
#!/bin/sh
 +
export KDEDIR="$HOME/kde"
 +
 
 +
AddToPath() {
 +
        eval "export $1=$2\${$1+:\$$1}" # prepend to existing path, if there is one
 +
}
 +
 
 +
AddToPath PATH "$KDEDIR/bin"
 +
AddToPath LD_LIBRARY_PATH "$KDEDIR/lib"
 +
AddToPath QT_PLUGIN_PATH "$KDEDIR/lib/kde4/plugins:$KDEDIR/lib/qt4/plugins"
 +
AddToPath PKG_CONFIG_PATH "$KDEDIR/lib/pkgconfig"
 +
AddToPath CMAKE_PREFIX_PATH "$KDEDIR"
 +
export XDG_DATA_DIRS="$KDEDIR/share:/usr/share"
 +
export XDG_CONFIG_DIRS="$KDEDIR/etc/xdg:/etc/xdg"
 +
export KDEDIRS="$KDEDIR"
 +
exec startkde "$@"
 +
</syntaxhighlight>
 +
 
 +
Replace {{path|$HOME/kde}} in the example above with the prefix you are installing KDE4 into.
 +
 
 +
After restarting the login manager (<tt>Alt+e</tt> in KDM) this new entry should appear in the sessions menu. However, since the new environment variables will not effect dbus in this setup, there might be some issues. The notes above regarding polkit also apply.
 +
 
 +
== Directly starting X ==
 +
 
 +
You can also start a full KDE 4 desktop environment session from the command line, with something like this:
 +
 
 +
X :1 & export DISPLAY=:1
 +
$HOME/startkde-wrapper
 +
 
 +
Using the {{path|startkde-wrapper}} from above. However, this again will not set up dbus and polkit properly to use the custom prefix.
 +
 
 +
{{Note|If the X server refuses the connection saying something like: <tt>Xlib: connection to ":1.0" refused by server</tt>, try <tt>X -ac :1</tt> instead.}}
 +
 
  
After restarting the login manager (<tt>Alt+e</tt> in KDM) this new entry should appear in the sessions menu. However, since the new environment variables will not effect dbus in this setup, there might be some issues.
 
  
  
  
 
[[Category:KDE4]]
 
[[Category:KDE4]]

Revision as of 12:47, 23 February 2012

Full KDE 4 session

Using the login manager (a)

You can change your configuration so a normal login using your login manager (KDM, lightdm, whatever you choose) will end up starting your self-compiled KDE. To make sure that even the daemons started by the X login process (most notably dbus) use the correct files, create a file called .xsessionrc in your home folder, which sets up the environment:

export KDEDIR="$HOME/kde"

AddToPath() {
        eval "export $1=$2\${$1+:\$$1}" # prepend to existing path, if there is one
}

AddToPath PATH "$KDEDIR/bin"
AddToPath LD_LIBRARY_PATH "$KDEDIR/lib"
AddToPath QT_PLUGIN_PATH "$KDEDIR/lib/kde4/plugins:$KDEDIR/lib/qt4/plugins"
AddToPath PKG_CONFIG_PATH "$KDEDIR/lib/pkgconfig"
AddToPath CMAKE_PREFIX_PATH "$KDEDIR"
export XDG_DATA_DIRS="$KDEDIR/share:/usr/share"
export XDG_CONFIG_DIRS="$KDEDIR/etc/xdg:/etc/xdg"
export KDEDIRS="$KDEDIR"

Replace $HOME/kde in the example above with the prefix you are installing KDE4 into. If you want to, also add "export KDEHOME=$HOME/.kde4" to change the path KDE configuration is stored in. Finally, create a file called $HOME/.xsession which actually starts KDE:

exec startkde "$@"

However, even after following these steps, authentication of configuration changes using polkit (for example, changing the clock or the KDM settings) will not work. Unfortunately, you can not set up several KDE installations properly to allow this - you can change your system configuration so that your self-compiled KDE will be able to use polkit, but then this will stop working in the distribution-provided KDE, or another self-compiled KDE in a different prefix. To do so, create a file called /etc/dbus-1/system.d/kde-selfcompiled.conf with the following content:

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <includedir>/home/user/kde/etc/dbus-1/system.d</includedir>
  <servicedir>/home/user/kde/share/dbus-1/system-services</servicedir>

</busconfig>

Again, replace /home/user/kde by your installation prefix. In the login manager, make sure you select the "Standard" session.

Using the login manager (b)

The configuration method described above will hard-wire that user to always use your self-compiled KDE, no matter what you select in the login manager (selecting the distro-provided KDE may even result in funny effects). If you are using KDM (or a compatible login manager) and want to be able to select the session type before logging in, create a .desktop file in either $(kde-config --prefix)/share/apps/kdm/sessions/ or in /usr/share/xsessions/. The easiest thing to do is to copy an existing kde.desktop file and name it kde4.desktop. Open this new .desktop file in a text editor and change the Exec, TryExec and Name entries to look something like this:

Exec=$HOME/startkde-wrapper
TryExec=$HOME/startkde-wrapper
Name=KDE4 (self-compiled)

startkde-wrapper sets some environment variables which are required to make KDE run properly in a non-/usr environment:

#!/bin/sh
export KDEDIR="$HOME/kde"

AddToPath() {
        eval "export $1=$2\${$1+:\$$1}" # prepend to existing path, if there is one
}

AddToPath PATH "$KDEDIR/bin"
AddToPath LD_LIBRARY_PATH "$KDEDIR/lib"
AddToPath QT_PLUGIN_PATH "$KDEDIR/lib/kde4/plugins:$KDEDIR/lib/qt4/plugins"
AddToPath PKG_CONFIG_PATH "$KDEDIR/lib/pkgconfig"
AddToPath CMAKE_PREFIX_PATH "$KDEDIR"
export XDG_DATA_DIRS="$KDEDIR/share:/usr/share"
export XDG_CONFIG_DIRS="$KDEDIR/etc/xdg:/etc/xdg"
export KDEDIRS="$KDEDIR"
exec startkde "$@"

Replace $HOME/kde in the example above with the prefix you are installing KDE4 into.

After restarting the login manager (Alt+e in KDM) this new entry should appear in the sessions menu. However, since the new environment variables will not effect dbus in this setup, there might be some issues. The notes above regarding polkit also apply.

Directly starting X

You can also start a full KDE 4 desktop environment session from the command line, with something like this:

X :1 & export DISPLAY=:1
$HOME/startkde-wrapper

Using the startkde-wrapper from above. However, this again will not set up dbus and polkit properly to use the custom prefix.

noframe
 
Note
If the X server refuses the connection saying something like: Xlib: connection to ":1.0" refused by server, try X -ac :1 instead.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.