Changeset d09eb9b


Ignore:
Timestamp:
09/25/2015 01:48:24 PM (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:
1c7e5c8a
Parents:
c81d34a
Message:
  • Fix starting X with startx or sddm ... Part 2. ▪ sddm-0.12.0 ▪ xinit-1.3.4 ▪ ConsoleKit2-1.0.0 ▪ lxde-common-0.99.0 ▪ LXQt Desktop Final Instructions ▪ xfce4-session-4.12.1 ▪ Starting KDE4

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

Files:
9 edited

Legend:

Unmodified
Added
Removed

  • general.ent

    rc81d34a rd09eb9b  
    11<!-- $LastChangedBy$ $Date$ -->
    22
    3 <!ENTITY day          "24">                   <!-- Always 2 digits -->
     3<!ENTITY day          "25">                   <!-- Always 2 digits -->
    44<!ENTITY month        "09">                   <!-- Always 2 digits -->
    55<!ENTITY year         "2015">
    … …  
    77<!ENTITY copyholder   "The BLFS Development Team">
    88<!ENTITY version      "&year;-&month;-&day;">
    9 <!ENTITY releasedate  "September 24th &year;">
     9<!ENTITY releasedate  "September 25th &year;">
    1010<!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
    1111<!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->

  • introduction/welcome/changelog.xml

    rc81d34a rd09eb9b  
    4444
    4545-->
     46
     47    <listitem>
     48      <para>September 25th, 2015</para>
     49      <itemizedlist>
     50        <listitem>
     51          <para>[fernando] - Fix starting X with startx ... Part 2.
     52          Partially fixes
     53          <ulink url="&blfs-ticket-root;6972">#6972</ulink>.</para>
     54        </listitem>
     55      </itemizedlist>
     56    </listitem>
     57
    4658    <listitem>
    4759      <para>September 24th, 2015</para>

  • kde/core/config.xml

    rc81d34a rd09eb9b  
    1818  <bridgehead renderas="sect3">KDE4 Startup Dependencies</bridgehead>
    1919
    20   <bridgehead renderas="sect4">Optional</bridgehead>
    21   <para role="optional">
    22     <xref linkend="dbus"/> (runtime)
     20  <bridgehead renderas="sect4">Recommended Runtime Dependencies</bridgehead>
     21  <para role="recommended">
     22    <xref linkend="consolekit"/> and
     23    <xref linkend="dbus"/>
    2324  </para>
    2425
    … …  
    4950    <para>
    5051      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:
     52      You can switch to another vt<emphasis>n</emphasis> simultaneously
     53      pressing the keys Ctrl-Alt-F<emphasis>n</emphasis>
     54      (<emphasis>n</emphasis>=1, 2, ...).  To switch back to the X session,
     55      normally started at vt7, use Ctrl-Alt-F7. The vt where the command
     56      <command>startx</command> was executed will display many messages,
     57      including X starting messages, applications automatically started with
     58      the session, and eventually, some warning and error messages. You may
     59      prefer to redirect those messages to a log file, which not only will keep
     60      the initial vt uncluttered, but can also be used for debug purposes. This
     61      can be done starting X with:
    5962    </para>
    6063
    6164    <screen><userinput>startx &amp;&gt; ~/.x-session-errors</userinput></screen>
    6265
     66    <note>
     67      <para>
     68        You may wish to drop consolekit and/or dbus-launch, e.g., just using
     69        startkde in .~/.xinitrc, but some functionalities such as mount/umount
     70        file systems from a file manager will not be possible, or the reboot
     71        option will be absent or not functioning, between other problems.
     72      </para>
     73    </note>
     74
    6375    <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.
     76      When shutting down or rebooting, the stopping messages appear on the vt
     77      where X was running. If you wish to see those messages, simultaneously
     78      press keys Alt-F7 (assuming that X was running on vt7).
    6879    </para>
    6980
    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>
     81  </sect2>
    7882
    7983    <sect2 role="content">

  • lxde/desktop/lxde-common.xml

    rc81d34a rd09eb9b  
    9090    </para>
    9191
     92    <bridgehead renderas="sect4">Recommended Runtime Dependencies</bridgehead>
     93    <para role="recommended">
     94      <xref linkend="consolekit"/> and
     95      <xref linkend="dbus"/>
     96    </para>
     97
    9298    <bridgehead renderas="sect4">Optional Runtime Dependencies</bridgehead>
    9399    <para role="optional">
    94       <xref linkend="dbus"/>, and
    95       a notification daemon such as
     100      A notification daemon such as
    96101      <xref linkend="notification-daemon"/> or
    97102      <xref linkend="xfce4-notifyd"/>
    … …  
    157162    <para>
    158163      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:
     164      You can switch to another vt<emphasis>n</emphasis> simultaneously
     165      pressing the keys Ctrl-Alt-F<emphasis>n</emphasis>
     166      (<emphasis>n</emphasis>=1, 2, ...).  To switch back to the X session,
     167      normally started at vt7, use Ctrl-Alt-F7. The vt where the command
     168      <command>startx</command> was executed will display many messages,
     169      including X starting messages, applications automatically started with
     170      the session, and eventually, some warning and error messages. You may
     171      prefer to redirect those messages to a log file, which not only will keep
     172      the initial vt uncluttered, but can also be used for debug purposes. This
     173      can be done starting X with:
    167174    </para>
    168175
    169176    <screen><userinput>startx &amp;&gt; ~/.x-session-errors</userinput></screen>
    170177
    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.
     178    <note>
     179      <para>
     180        You may wish to drop consolekit and/or dbus-launch, e.g., just using
     181        startlxde in .~/.xinitrc, but some functionalities such as mount/umount
     182        file systems from a file manager will not be possible, or the reboot
     183        option will be absent or not functioning, between other problems.
     184      </para>
     185    </note>
     186
     187    <para>
     188      When shutting down or rebooting, the stopping messages appear on the vt
     189      where X was running. If you wish to see those messages, simultaneously
     190      press keys Alt-F7 (assuming that X was running on vt7).
    183191    </para>
    184192

  • lxqt/desktop/post-install.xml

    rc81d34a rd09eb9b  
    4242      reported as the <quote>recommended <application>LXQt</application>
    4343      display manager</quote>) or another Display Manager, e.g.
    44       <xref linkend="lxdm"/>.
     44      <xref linkend="lxdm"/>, and
     45      <xref linkend="dbus"/>
    4546    </para>
    4647
    … …  
    103104    <para>
    104105      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:
     106      You can switch to another vt<emphasis>n</emphasis> simultaneously
     107      pressing the keys Ctrl-Alt-F<emphasis>n</emphasis>
     108      (<emphasis>n</emphasis>=1, 2, ...).  To switch back to the X session,
     109      normally started at vt7, use Ctrl-Alt-F7. The vt where the command
     110      <command>startx</command> was executed will display many messages,
     111      including X starting messages, applications automatically started with
     112      the session, and eventually, some warning and error messages. You may
     113      prefer to redirect those messages to a log file, which not only will keep
     114      the initial vt uncluttered, but can also be used for debug purposes. This
     115      can be done starting X with:
    113116    </para>
    114117
    115118    <screen><userinput>startx &amp;&gt; ~/.x-session-errors</userinput></screen>
    116119
    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>
     120    <note>
     121      <para>
     122        You may wish to drop consolekit and/or dbus-launch, e.g., just using
     123        startlxqt in .~/.xinitrc, but some functionalities such as mount/umount
     124        file systems from a file manager will not be possible, or the reboot
     125        option will be absent or not functioning, between other problems.
     126      </para>
     127    </note>
    123128
    124129    <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.
     130      When shutting down or rebooting, the stopping messages appear on the vt
     131      where X was running. If you wish to see those messages, simultaneously
     132      press keys Alt-F7 (assuming that X was running on vt7).
    129133    </para>
    130134

  • postlfs/security/consolekit.xml

    rc81d34a rd09eb9b  
    165165    <para>
    166166      <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>.
     167      Fix the location of the 90-consolekit.sh script. Notice that the script
     168      has been renamed after installation, because xinitrc only sources script
     169      names ending with extension <emphasis>.sh</emphasis>.
    170170    </para>
    171171

  • x/dm/sddm.xml

    rc81d34a rd09eb9b  
    212212<screen><userinput>sddm --example-config > sddm.example.conf</userinput></screen>
    213213
    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
     214      <note>
     215        <para>
     216          This command generates an <emphasis>example</emphasis> config file,
     217          which depends on several conditions of the system where it is
     218          generated. A few options are <emphasis>defaults</emphasis> from
     219          upstream.  If there is a previously installed
     220          <filename>/etc/sddm.conf</filename>, it will generate a replica. When
     221          it is generated during an X session, some session configurations are
     222          replicated, e.g. if the cursor from the Adwaita theme is already
     223          configured, you will obtain <emphasis>CursorTheme=Adwaita</emphasis>
     224          in the example file generated.
     225        </para>
     226      </note>
     227
     228      <para>
     229        If there is no <filename>/etc/sddm.conf</filename> file yet, as the
    219230        <systemitem class="username">root</systemitem> user, copy the example
    220231        file to <filename>/etc/sddm.conf</filename>:
    … …  
    228239        <systemitem class="username">root</systemitem>
    229240        user to replace the <emphasis>XauthPath</emphasis> default path by
    230         <emphasis>/usr/bin/xauth</emphasis>. Or, as the <systemitem
     241        <emphasis>/opt/xorg/bin/xauth</emphasis>. Or, as the <systemitem
    231242        class="username">root</systemitem> user, issue
    232243      </para>
    … …  
    241252
    242253      <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:
     254        From now on, we will describe how to modify configurations using sed.
     255        Of course, you may instead use your preferred editor as the <systemitem
     256        class="username">root</systemitem> user. For security reasons, you
     257        normally want the default server option in sddm.example.conf, unless a
     258        remote machine needs access to the local X server. In that case, as the
     259        <systemitem class="username">root</systemitem> user, issue:
    250260      </para>
    251261
    … …  
    263273
    264274      <para>
    265         That was for Desktop users. For Notebook users,
    266         replace \"on\" by \"off\", in the command above.
     275        for Desktop users. For Notebook users, replace \"on\" by \"off\",
     276        in the command above.
    267277      </para>
    268278
    … …  
    353363
    354364      <para>
    355         If the sddm bootscript has been installed, start it by running, as
     365        If the sddm bootscript has been installed, start sddm by running, as the
    356366        <systemitem class="username">root</systemitem> user:
    357367      </para>
    … …  
    457467      <para>
    458468        E.g. <command>echo 'setxkbmap "fr,gb,br,us"' &gt;&gt;
    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' &gt;&gt;
    462         /usr/share/sddm/scripts/Xsetup</command>. See man setxkbmap.
     469        /usr/share/sddm/scripts/Xsetup</command>. A very accurate definition
     470        of the keyboard(s) is possible, for example: <command>echo 'setxkbmap
     471        -model pc105 -layout br,us -variant abnt2,dvorak -keycodes evdev'
     472        &gt;&gt; /usr/share/sddm/scripts/Xsetup</command>. See man setxkbmap.
    463473      </para>
    464474
    … …  
    473483
    474484      <para>
    475         It has been reported that this package does not work with Xorg installed
    476         with a prefix other than <filename class="directory">/usr</filename>.
     485        It has been reported that problems may happen with this package, if
     486        Xorg is installed with a prefix other than <filename
     487        class="directory">/usr</filename>. So far, BLFS development team has
     488        not hit any problem, in this case.
    477489      </para>
    478490

  • x/installing/xinit.xml

    rc81d34a rd09eb9b  
    8080    -i startx.cpp</userinput></screen>
    8181
     82    <note>
     83      <para>
     84        If you have already installed this package without the sed above, there
     85        is no need to reinstall. Just modify the installed
     86        <command>startx</command>, issuing, as the <systemitem
     87        class="username">root</systemitem> user:
     88
     89<screen role="root"><userinput>sed -e '/$serverargs $vtarg/ s/serverargs/: #&amp;/' \
     90    -i.orig /usr/bin/startx</userinput></screen>
     91      </para>
     92    </note>
     93
    8294    <para>Install <application>xinit</application> by running the
    8395    following commands:</para>

  • xfce/core/xfce4-session.xml

    rc81d34a rd09eb9b  
    198198    <para>
    199199      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:
     200      You can switch to another vt<emphasis>n</emphasis> simultaneously
     201      pressing the keys Ctrl-Alt-F<emphasis>n</emphasis>
     202      (<emphasis>n</emphasis>=1, 2, ...).  To switch back to the X session,
     203      normally started at vt7, use Ctrl-Alt-F7. The vt where the command
     204      <command>startx</command> was executed will display many messages,
     205      including X starting messages, applications automatically started with
     206      the session, and eventually, some warning and error messages. You may
     207      prefer to redirect those messages to a log file, which not only will keep
     208      the initial vt uncluttered, but can also be used for debug purposes. This
     209      can be done starting X with:
    208210    </para>
    209211
    210212    <screen><userinput>startx &amp;&gt; ~/.x-session-errors</userinput></screen>
    211213
    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.
     214    <note>
     215      <para>
     216        You may wish to drop consolekit and/or dbus-launch, e.g., just using
     217        startxfce4 in .~/.xinitrc, but some functionalities such as mount/umount
     218        file systems from a file manager will not be possible, or the reboot
     219        option will be absent or not functioning, between other problems.
     220      </para>
     221    </note>
     222
     223    <para>
     224      When shutting down or rebooting, the stopping messages appear on the vt
     225      where X was running. If you wish to see those messages, simultaneously
     226      press keys Alt-F7 (assuming that X was running on vt7).
    224227    </para>
    225228
Note: See TracChangeset for help on using the changeset viewer.