source: kde/core/config.xml@ c81d34a

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since c81d34a was eca7a58, checked in by Fernando de Oliveira <fernando@…>, 9 years ago
  • Fix starting X with startx (from xinit) and sddm (with consolekit2 and upowerd) and somwhat related fixes

◦ sddm-0.12.0: fixes for upauer, Consolekit2, DBUS_CONFIG_FILENAME,

example-config, nolisten tcp, numlock, and setxkbmap.

◦ sddm bootscript: remove upowerd parts.
◦ xinit-1.3.4: Fix startx to use the first available virtual terminal
◦ ConsoleKit2-1.0.0: Fix docdir and xinitrc.d script 90-consolekit.sh

name and place

◦ lxde-common-0.99.0: Fix lxde session start
◦ LXQt Desktop Final Instructions: Fix lxde session start
◦ xfce4-session-4.12.1: Fix lxde session start
◦ Starting KDE4: Fix lxde session start

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@16461 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 4.6 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="kde-core-config" xreflabel="Starting KDE4">
9 <?dbhtml filename="config.html"?>
10
11 <sect1info>
12 <othername>$LastChangedBy$</othername>
13 <date>$Date$</date>
14 </sect1info>
15
16 <title>Starting KDE4</title>
17
18 <bridgehead renderas="sect3">KDE4 Startup Dependencies</bridgehead>
19
20 <bridgehead renderas="sect4">Optional</bridgehead>
21 <para role="optional">
22 <xref linkend="dbus"/> (runtime)
23 </para>
24
25 <para>After <application>Kde-workspace</application> has been installed, the
26 first important milestone has been reached. Now you need to configure your
27 system to start KDE4.</para>
28
29 <sect2 role="content">
30 <title>Starting KDE4 from the command prompt</title>
31
32 <para>
33 You can start <application>KDE4</application> from runlevel 3, using
34 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager,
35 such as <xref linkend="sddm"/>.
36 </para>
37
38 <para>
39 To start <application>KDE4</application> using <xref linkend="xinit"/>,
40 run the following commands:
41 </para>
42
43<screen><userinput>cat &gt; ~/.xinitrc &lt;&lt; "EOF"
44<literal>ck-launch-session dbus-launch --exit-with-session startkde</literal>
45EOF
46
47startx</userinput></screen>
48
49 <para>
50 The X session starts on the first unused virtual terminal, normally vt7.
51 You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys
52 Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7,
53 use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many
54 messages there, including X starting messages, applications automatically
55 started with the session, and eventually, some warning and error
56 messages. You may prefer to redirect those messages to a log file, which
57 not only will keep vt1 uncluttered, but also can be used for debug
58 purposes. This can be done starting X with:
59 </para>
60
61 <screen><userinput>startx &amp;&gt; ~/.x-session-errors</userinput></screen>
62
63 <para>
64 You may wish to drop consolekit and/or dbus-launch, e.g., just using
65 startlxde in .~/.xinitrc, but some functionalities such as mount/umount
66 file systems from a file manager will not be possible, or the reboot
67 option will be absent or not functioning, between other problems.
68 </para>
69
70 <para>
71 Because X is (normally) on vt7, when you shutdown the vt is switched back
72 to that one where the command starting it was executed. In this case, if
73 you wish to see the shutdown messages, simultaneously press keys Alt-F7,
74 because normally those messages appear on the vt where X was running.
75 </para>
76
77 </sect2>
78
79 <sect2 role="content">
80 <title>Starting KDE4 at boot</title>
81
82 <para>KDE4 comes with a graphical login interface called KDM (the KDE4 Display
83 Manager), which provides a customizable graphical login at boot. To use KDM,
84 you need to edit your <filename>/etc/inittab</filename> file (as the
85 <systemitem class="username">root</systemitem> user).
86 First, setup run-level 5 to start KDM (adjust
87 the path to kdm according to your system):</para>
88
89<screen><userinput>cat &gt;&gt; /etc/inittab &lt;&lt; EOF
90<literal>kd:5:respawn:/opt/kde/bin/kdm</literal>
91EOF</userinput></screen>
92
93 <para>Additionally, you need to change the default run-level from 3 to 5:</para>
94
95<screen><userinput>sed -i 's#id:3:initdefault:#id:5:initdefault:#' /etc/inittab</userinput></screen>
96
97 <para>You can now restart your system and see the KDE4 login
98 screen.</para>
99
100 </sect2>
101
102 <sect2 role="content">
103 <title>Installing further languages (l10n)</title>
104
105 <para>You may want to install support for your locale language. The l10n
106 packages can be found at <ulink
107 url="&kde-download-http;applications/&kde-apps-version;/src/kde-l10n/">
108 &kde-download-http;applications/&kde-apps-version;/src/kde-l10n/</ulink>.
109 See <xref linkend="kde-add-pkgs"/> for build instructions. If you are in a
110 KDE4 session when installing a new language and configure KDE4 to use it, the
111 session needs to be restarted, in order to see the effects.</para>
112
113 </sect2>
114
115 <sect2 role="content">
116 <title>Installing further KDE4 packages</title>
117
118 <para>Every subsequent package can be built while having
119 <application>KDE4</application> up and running, but remember to keep
120 <envar>&kde-dir;</envar> and <envar>&qt4-dir;</envar> set.</para>
121
122 </sect2>
123
124</sect1>
Note: See TracBrowser for help on using the repository browser.