Changeset eca7a58
- Timestamp:
- 09/25/2015 01:11:15 AM (9 years ago)
- Branches:
- 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
- Children:
- c81d34a
- Parents:
- 1c2bec77
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/changelog.xml
r1c2bec77 reca7a58 47 47 <para>September 24th, 2015</para> 48 48 <itemizedlist> 49 <listitem> 50 <para>[fernando] - Fix starting X with startx (from xinit) and sddm 51 (with consolekit2 and upowerd) and somwhat related fixes. Fixes 52 <ulink url="&blfs-ticket-root;6972">#6972</ulink>.</para> 53 </listitem> 49 54 <listitem> 50 55 <para>[bdubbs] - Update to KDE Frameworks 5.14. Fixes -
kde/core/config.xml
r1c2bec77 reca7a58 30 30 <title>Starting KDE4 from the command prompt</title> 31 31 32 <para>To start <application>KDE4</application> from the command prompt, you 33 first need to modify your <filename>.xinitrc</filename> file:</para> 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> 34 37 35 <screen><userinput>cat > ~/.xinitrc << EOF 36 <literal># Begin .xinitrc 38 <para> 39 To start <application>KDE4</application> using <xref linkend="xinit"/>, 40 run the following commands: 41 </para> 37 42 38 exec ck-launch-session dbus-launch --exit-with-session startkde 43 <screen><userinput>cat > ~/.xinitrc << "EOF" 44 <literal>ck-launch-session dbus-launch --exit-with-session startkde</literal> 45 EOF 39 46 40 # End .xinitrc</literal> 41 EOF</userinput></screen> 47 startx</userinput></screen> 42 48 43 <note><para>If you are not using <application>ConsoleKit</application>, remove 44 <userinput>ck-launch-session</userinput>.</para></note> 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> 45 60 46 <para>You can now start KDE4 using the <command>startx</command> command.</para> 61 <screen><userinput>startx &> ~/.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> 47 76 48 77 </sect2> -
lxde/desktop/lxde-common.xml
r1c2bec77 reca7a58 139 139 140 140 <para> 141 You can start <application>LXDE</application> from runlevel 3, using 142 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, 143 such as <xref linkend="sddm"/>. 144 </para> 145 146 <para> 141 147 To start <application>LXDE</application> using <xref linkend="xinit"/>, 142 148 run the following commands: … … 144 150 145 151 <screen><userinput>cat > ~/.xinitrc << "EOF" 146 startlxde 152 <literal>ck-launch-session dbus-launch --exit-with-session startlxde</literal> 147 153 EOF 148 154 149 155 startx</userinput></screen> 150 156 151 <note> 152 <para> 153 When <xref linkend="consolekit"/> was built, if you did not use the 154 recommended <xref linkend="linux-pam"/> dependency or did not rebuild 155 <xref linkend="shadow"/> with Linux-PAM, ~/.xinitrc should have the 156 entry: 157 </para> 158 159 <screen><userinput>ck-launch-session startlxde</userinput></screen> 160 161 <para>to obtain the appropriate permissions for system functions.</para> 162 163 <para> 164 To test if ck-launch-session is needed, run 165 <command>ck-list-sessions</command> fropm the command line. If a session 166 associated with the current tty is present that is both 'active' and 167 'local' then <command>ck-launch-session</command> is not needed. 168 </para> 169 </note> 157 <para> 158 The X session starts on the first unused virtual terminal, normally vt7. 159 You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys 160 Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7, 161 use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many 162 messages there, including X starting messages, applications automatically 163 started with the session, and eventually, some warning and error 164 messages. You may prefer to redirect those messages to a log file, which 165 not only will keep vt1 uncluttered, but also can be used for debug 166 purposes. This can be done starting X with: 167 </para> 168 169 <screen><userinput>startx &> ~/.x-session-errors</userinput></screen> 170 171 <para> 172 You may wish to drop consolekit and/or dbus-launch, e.g., just using 173 startlxde in .~/.xinitrc, but some functionalities such as mount/umount 174 file systems from a file manager will not be possible, or the reboot 175 option will be absent or not functioning, between other problems. 176 </para> 177 178 <para> 179 Because X is (normally) on vt7, when you shutdown the vt is switched back 180 to that one where the command starting it was executed. In this case, if 181 you wish to see the shutdown messages, simultaneously press keys Alt-F7, 182 because normally those messages appear on the vt where X was running. 183 </para> 170 184 171 185 </sect2> -
lxqt/desktop/post-install.xml
r1c2bec77 reca7a58 85 85 86 86 <para> 87 If an optional Display Manager have been installed and you wish to use it, 88 skip the following steps. 87 You can start <application>LXQt</application> from runlevel 3, using 88 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, 89 such as <xref linkend="sddm"/>. 89 90 </para> 90 91 … … 94 95 </para> 95 96 96 <screen><userinput>cat > >~/.xinitrc << "EOF"97 ck-launch-session startlxqt 97 <screen><userinput>cat > ~/.xinitrc << "EOF" 98 <literal>ck-launch-session dbus-launch --exit-with-session startlxqt</literal> 98 99 EOF 99 100 100 101 startx</userinput></screen> 101 102 103 <para> 104 The X session starts on the first unused virtual terminal, normally vt7. 105 You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys 106 Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7, 107 use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many 108 messages there, including X starting messages, applications automatically 109 started with the session, and eventually, some warning and error 110 messages. You may prefer to redirect those messages to a log file, which 111 not only will keep vt1 uncluttered, but also can be used for debug 112 purposes. This can be done starting X with: 113 </para> 114 115 <screen><userinput>startx &> ~/.x-session-errors</userinput></screen> 116 117 <para> 118 You may wish to drop consolekit and/or dbus-launch, e.g., just using 119 startlxde in .~/.xinitrc, but some functionalities such as mount/umount 120 file systems from a file manager will not be possible, or the reboot 121 option will be absent or not functioning, between other problems. 122 </para> 123 124 <para> 125 Because X is (normally) on vt7, when you shutdown the vt is switched back 126 to that one where the command starting it was executed. In this case, if 127 you wish to see the shutdown messages, simultaneously press keys Alt-F7, 128 because normally those messages appear on the vt where X was running. 129 </para> 130 102 131 </sect2> 103 132 -
postlfs/security/consolekit.xml
r1c2bec77 reca7a58 120 120 --enable-pam-module \ 121 121 --enable-polkit \ 122 --with-systemdsystemunitdir=no && 122 --with-xinitrc-dir=/etc/X11/app-defaults/xinitrc.d \ 123 --docdir=/usr/share/doc/ConsoleKit-&consolekit-version; \ 124 --with-systemdsystemunitdir=no && 123 125 make</userinput></screen> 124 126 … … 131 133 </para> 132 134 133 <screen role="root"><userinput>make install</userinput></screen> 135 <screen role="root"><userinput>make install && 136 137 mv -v /etc/X11/app-defaults/xinitrc.d/90-consolekit{,.sh}</userinput></screen> 134 138 135 139 </sect2> … … 151 155 <application>ConsoleKit</application> to work correctly with 152 156 <application>PAM</application>. Remove if 153 <application>Linux PAM</application> is 157 <application>Linux PAM</application> is 154 158 <emphasis role="strong">NOT</emphasis> installed. 155 159 </para> … … 157 161 <para> 158 162 <parameter>--enable-polkit</parameter>: Enable PolicyKit support. 163 </para> 164 165 <para> 166 <parameter>--with-xinitrc-dir=/etc/X11/app-defaults/xinitrc.d</parameter>: 167 Fix the localization of the 90-consolekit.sh script. Notice that the 168 script was renamed, after installation, because xinitrc expects script 169 names to have extension <emphasis>.sh</emphasis>. 159 170 </para> 160 171 … … 252 263 </seg> 253 264 <seg> 254 /etc/ConsoleKit, 255 /usr/include/ConsoleKit, 256 /usr/lib/ConsoleKit, 257 /usr/share/doc/ConsoleKit and 258 /var/log/ConsoleKit 265 /{etc,usr/{include,lib},var/{log,run}}/ConsoleKit and 266 /usr/share/doc/ConsoleKit-&consolekit-version; 259 267 </seg> 260 268 </seglistitem> -
x/dm/sddm.xml
r1c2bec77 reca7a58 122 122 123 123 <para> 124 First, fix the application to start <command>upowerd</command>, 125 if necessary, and after login, start the session with 126 <command>ck-launch-session</command>: 127 </para> 128 129 <screen><userinput>sed -e '/UPOWER_SERVICE)/ s:^://:' \ 130 -i src/daemon/PowerManager.cpp && 131 132 sed -e 's/eval exec/& ck-launch-session /' \ 133 -i data/scripts/Xsession</userinput></screen> 134 135 <para> 124 136 Install <application>SDDM</application> by running the following 125 137 commands: … … 132 144 -DCMAKE_BUILD_TYPE=Release \ 133 145 -DENABLE_JOURNALD=OFF \ 146 -DDBUS_CONFIG_FILENAME=sddm_org.freedesktop.DisplayManager.conf \ 134 147 -Wno-dev .. && 135 148 make</userinput></screen> … … 159 172 <parameter>-DENABLE_JOURNALD=OFF</parameter>: This switch is used because 160 173 BLFS does not support <application>systemd</application>. 174 </para> 175 176 <para> 177 <parameter>-DDBUS_CONFIG_FILENAME=sddm_org.freedesktop.DisplayManager.conf</parameter>: 178 This switch is used for safety reason: other DMs already use 179 <filename>org.freedesktop.DisplayManager.conf</filename>. Verify in your 180 system taht this is not the case, if you wish to remove it. 161 181 </para> 162 182 … … 186 206 <para> 187 207 This file is not installed with the build instructions, and 188 default values are used by sddm. In order to generate the default 189 <filename>/etc/sddm.conf</filename>, issue, as the <systemitem 190 class="username">root</systemitem> user: 191 </para> 192 193 <screen role="root"><userinput>sddm --example-config > /etc/sddm.conf</userinput></screen> 194 195 <para> 196 You need to edit this file, if your system has any unconventional 197 characteristics. For example, if Xorg is installed in /opt, use your 198 preferred editor as the <systemitem class="username">root</systemitem> 199 user to replace the <emphasis>ServerPath</emphasis> and 200 <emphasis>XauthPath</emphasis> default paths by 201 <emphasis>/opt/xorg/bin/</emphasis>. Or, as the <systemitem 208 default values are used by sddm. In order to generate the example 209 <filename>sddm.example.conf</filename>, issue: 210 </para> 211 212 <screen><userinput>sddm --example-config > sddm.example.conf</userinput></screen> 213 214 <para> 215 We repeat, this command generates an example config file. If there is 216 an already previously installed <filename>/etc/sddm.conf</filename>, it 217 will generate a replica. If there is no yet the 218 <filename>/etc/sddm.conf</filename> file, as the 219 <systemitem class="username">root</systemitem> user, copy the example 220 file to <filename>/etc/sddm.conf</filename>: 221 </para> 222 223 <screen role="root"><userinput>cp -v sddm.example.conf /etc/sddm.conf</userinput></screen> 224 225 <para> 226 Normally, you want to edit this file. For example, if Xorg is installed 227 in /opt, use your preferred editor as the 228 <systemitem class="username">root</systemitem> 229 user to replace the <emphasis>XauthPath</emphasis> default path by 230 <emphasis>/usr/bin/xauth</emphasis>. Or, as the <systemitem 202 231 class="username">root</systemitem> user, issue 203 232 </para> 204 233 205 234 <screen role="root"><userinput>sed -e '/ServerPath/ s|usr|opt/xorg|' \ 206 -e '/XauthPath/ s|usr|opt/xorg|' \207 235 -i.orig /etc/sddm.conf</userinput></screen> 208 236 … … 210 238 This command will do the substitution and create a copy of the original 211 239 file with name <filename>/etc/sddm.conf.orig</filename>. 240 </para> 241 242 <para> 243 From now on, we will describe how to modify configurations using sed, 244 but of course you may rather use your preferred editor as the 245 <systemitem class="username">root</systemitem>, instead. You generally 246 want the server option that comes in sddm.example.conf, for security 247 reasons. Unless you want a remote machine to use the local X server, 248 in which case, as the <systemitem class="username">root</systemitem> 249 user, issue: 250 </para> 251 252 <screen role="root"><userinput>sed -e 's/-nolisten tcp//'\ 253 -i /etc/sddm.conf</userinput></screen> 254 255 <para> 256 Desktop (Notebook) users, normally wish the Num Lock key on (off). For 257 that, as the <systemitem 258 class="username">root</systemitem> user, issue: 259 </para> 260 261 <screen role="root"><userinput>sed -e 's/\"none\"/\"on\"/' \ 262 -i /etc/sddm.conf</userinput></screen> 263 264 <para> 265 That was for Desktop users. For Notebook users, 266 replace \"on\" by \"off\", in the command above. 212 267 </para> 213 268 … … 378 433 </para> 379 434 435 <note> 436 <para> 437 In the next couple of paragraphs, due to a problem with sddm-greeter, 438 we mention how to define the keyboard used there. Notice that this is 439 also the keyboard that will be used in the X session, unless there is 440 a configuration in the Desktop Environment or in the Window Manager 441 overriding it, afterwards. 442 </para> 443 </note> 444 380 445 <para> 381 446 Keyboard selection: the greeter shows a double question mark or the … … 391 456 392 457 <para> 393 E.g. <command>echo 'setxkbmap "gb,br,us"' >> 394 /usr/share/sddm/scripts/Xsetup</command> 458 E.g. <command>echo 'setxkbmap "fr,gb,br,us"' >> 459 /usr/share/sddm/scripts/Xsetup</command>. You can be accurate defining 460 the keyboard(s), for example: <command>echo 'setxkbmap -model pc105 461 -layout br,us -variant abnt2,dvorak -keycodes evdev' >> 462 /usr/share/sddm/scripts/Xsetup</command>. See man setxkbmap. 395 463 </para> 396 464 -
x/installing/xinit.xml
r1c2bec77 reca7a58 73 73 <title>Installation of xinit</title> 74 74 75 <para>First, modify <command>startx</command>, hence the X session starts on 76 the first unused virtual terminal, which normally is vt7:</para> 77 <!--Apparently, this should not be done for systemd systems--> 78 79 <screen><userinput>sed -e '/$serverargs $vtarg/ s/serverargs/: #&/' \ 80 -i startx.cpp</userinput></screen> 81 75 82 <para>Install <application>xinit</application> by running the 76 83 following commands:</para> -
xfce/core/xfce4-session.xml
r1c2bec77 reca7a58 87 87 <bridgehead renderas="sect4">Recommended</bridgehead> 88 88 <para role="recommended"> 89 <xref linkend="desktop-file-utils"/> 90 <xref linkend="shared-mime-info"/> ,and89 <xref linkend="desktop-file-utils"/>, 90 <xref linkend="shared-mime-info"/> and 91 91 <xref linkend="polkit-gnome"/> 92 92 </para> … … 150 150 <xref linkend="openssh"/> 151 151 </para> 152 152 <!-- 153 153 <para> 154 154 To launch <application>Xfce4</application> use the command 155 155 <command>startxfce4</command>. If you have <xref linkend="consolekit"/> 156 installed, use <command>startxfce4 - -with-ck-launch</command>.156 installed, use <command>startxfce4 -\-with-ck-launch</command>. 157 157 <application>ConsoleKit</application> is required to perform any 158 158 task that requires administrative access, including shut down 159 159 and reboot. 160 </para> 160 </para>--> 161 161 162 162 <para> … … 174 174 <screen role="root"><userinput>update-desktop-database && 175 175 update-mime-database</userinput></screen> 176 </sect2> 177 178 <sect2 role="starting"> 179 <title>Starting Xfce4</title> 180 181 <para> 182 You can start <application>Xfce4</application> from runlevel 3, using 183 <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager, 184 such as <xref linkend="sddm"/>. 185 </para> 186 187 <para> 188 To start <application>Xfce4</application> using <xref linkend="xinit"/>, 189 run the following commands: 190 </para> 191 192 <screen><userinput>cat > ~/.xinitrc << "EOF" 193 <literal>ck-launch-session dbus-launch --exit-with-session startxfce4</literal> 194 EOF 195 196 startx</userinput></screen> 197 198 <para> 199 The X session starts on the first unused virtual terminal, normally vt7. 200 You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys 201 Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7, 202 use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many 203 messages there, including X starting messages, applications automatically 204 started with the session, and eventually, some warning and error 205 messages. You may prefer to redirect those messages to a log file, which 206 not only will keep vt1 uncluttered, but also can be used for debug 207 purposes. This can be done starting X with: 208 </para> 209 210 <screen><userinput>startx &> ~/.x-session-errors</userinput></screen> 211 212 <para> 213 You may wish to drop consolekit and/or dbus-launch, e.g., just using 214 startlxde in .~/.xinitrc, but some functionalities such as mount/umount 215 file systems from a file manager will not be possible, or the reboot 216 option will be absent or not functioning, between other problems. 217 </para> 218 219 <para> 220 Because X is (normally) on vt7, when you shutdown the vt is switched back 221 to that one where the command starting it was executed. In this case, if 222 you wish to see the shutdown messages, simultaneously press keys Alt-F7, 223 because normally those messages appear on the vt where X was running. 224 </para> 225 176 226 </sect2> 177 227
Note:
See TracChangeset
for help on using the changeset viewer.