Ignore:
Timestamp:
09/25/2015 01:11:15 AM (9 years ago)
Author:
Fernando de Oliveira <fernando@…>
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
Message:
  • 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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • kde/core/config.xml

    r1c2bec77 reca7a58  
    3030  <title>Starting KDE4 from the command prompt</title>
    3131
    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>
    3437
    35 <screen><userinput>cat &gt; ~/.xinitrc &lt;&lt; EOF
    36 <literal># Begin .xinitrc
     38    <para>
     39      To start <application>KDE4</application> using <xref linkend="xinit"/>,
     40      run the following commands:
     41    </para>
    3742
    38 exec ck-launch-session dbus-launch --exit-with-session startkde
     43<screen><userinput>cat &gt; ~/.xinitrc &lt;&lt; "EOF"
     44<literal>ck-launch-session dbus-launch --exit-with-session startkde</literal>
     45EOF
    3946
    40 # End .xinitrc</literal>
    41 EOF</userinput></screen>
     47startx</userinput></screen>
    4248
    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>
    4560
    46     <para>You can now start KDE4 using the <command>startx</command> command.</para>
     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>
    4776
    4877    </sect2>
Note: See TracChangeset for help on using the changeset viewer.