Changeset eca7a58 for lxde/desktop


Ignore:
Timestamp:
09/25/2015 01:11:15 AM (6 years ago)
Author:
Fernando de Oliveira <fernando@…>
Branches:
10.0, 10.1, 11.0, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, ken/refactor-virt, lazarus, nosym, perl-modules, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
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
  • lxde/desktop/lxde-common.xml

    r1c2bec77 reca7a58  
    139139
    140140    <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>
    141147      To start <application>LXDE</application> using <xref linkend="xinit"/>,
    142148      run the following commands:
     
    144150
    145151<screen><userinput>cat &gt; ~/.xinitrc &lt;&lt; "EOF"
    146 startlxde
     152<literal>ck-launch-session dbus-launch --exit-with-session startlxde</literal>
    147153EOF
    148154
    149155startx</userinput></screen>
    150156
    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 &amp;&gt; ~/.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>
    170184
    171185  </sect2>
Note: See TracChangeset for help on using the changeset viewer.