Author: fernando
Date: Thu Sep 24 18:11:15 2015
New Revision: 16461
Log:
• 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
Modified:
trunk/BOOK/introduction/welcome/changelog.xml
trunk/BOOK/kde/core/config.xml
trunk/BOOK/lxde/desktop/lxde-common.xml
trunk/BOOK/lxqt/desktop/post-install.xml
trunk/BOOK/postlfs/security/consolekit.xml
trunk/BOOK/x/dm/sddm.xml
trunk/BOOK/x/installing/xinit.xml
trunk/BOOK/xfce/core/xfce4-session.xml
trunk/bootscripts/ChangeLog
trunk/bootscripts/blfs/init.d/sddm
Modified: trunk/BOOK/introduction/welcome/changelog.xml
==============================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml Thu Sep 24 14:44:04
2015 (r16460)
+++ trunk/BOOK/introduction/welcome/changelog.xml Thu Sep 24 18:11:15
2015 (r16461)
@@ -47,6 +47,11 @@
<para>September 24th, 2015</para>
<itemizedlist>
<listitem>
+ <para>[fernando] - Fix starting X with startx (from xinit) and sddm
+ (with consolekit2 and upowerd) and somwhat related fixes. Fixes
+ <ulink url="&blfs-ticket-root;6972">#6972</ulink>.</para>
+ </listitem>
+ <listitem>
<para>[bdubbs] - Update to KDE Frameworks 5.14. Fixes
<ulink url="&blfs-ticket-root;6810">#6810</ulink>.</para>
</listitem>
Modified: trunk/BOOK/kde/core/config.xml
==============================================================================
--- trunk/BOOK/kde/core/config.xml Thu Sep 24 14:44:04 2015 (r16460)
+++ trunk/BOOK/kde/core/config.xml Thu Sep 24 18:11:15 2015 (r16461)
@@ -29,21 +29,50 @@
<sect2 role="content">
<title>Starting KDE4 from the command prompt</title>
- <para>To start <application>KDE4</application> from the command prompt, you
- first need to modify your <filename>.xinitrc</filename> file:</para>
-
-<screen><userinput>cat > ~/.xinitrc << EOF
-<literal># Begin .xinitrc
-
-exec ck-launch-session dbus-launch --exit-with-session startkde
-
-# End .xinitrc</literal>
-EOF</userinput></screen>
-
- <note><para>If you are not using <application>ConsoleKit</application>,
remove
- <userinput>ck-launch-session</userinput>.</para></note>
-
- <para>You can now start KDE4 using the <command>startx</command>
command.</para>
+ <para>
+ You can start <application>KDE4</application> from runlevel 3, using
+ <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager,
+ such as <xref linkend="sddm"/>.
+ </para>
+
+ <para>
+ To start <application>KDE4</application> using <xref linkend="xinit"/>,
+ run the following commands:
+ </para>
+
+<screen><userinput>cat > ~/.xinitrc << "EOF"
+<literal>ck-launch-session dbus-launch --exit-with-session startkde</literal>
+EOF
+
+startx</userinput></screen>
+
+ <para>
+ The X session starts on the first unused virtual terminal, normally vt7.
+ You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys
+ Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7,
+ use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many
+ messages there, including X starting messages, applications automatically
+ started with the session, and eventually, some warning and error
+ messages. You may prefer to redirect those messages to a log file, which
+ not only will keep vt1 uncluttered, but also can be used for debug
+ purposes. This can be done starting X with:
+ </para>
+
+ <screen><userinput>startx &>
~/.x-session-errors</userinput></screen>
+
+ <para>
+ You may wish to drop consolekit and/or dbus-launch, e.g., just using
+ startlxde in .~/.xinitrc, but some functionalities such as mount/umount
+ file systems from a file manager will not be possible, or the reboot
+ option will be absent or not functioning, between other problems.
+ </para>
+
+ <para>
+ Because X is (normally) on vt7, when you shutdown the vt is switched back
+ to that one where the command starting it was executed. In this case, if
+ you wish to see the shutdown messages, simultaneously press keys Alt-F7,
+ because normally those messages appear on the vt where X was running.
+ </para>
</sect2>
Modified: trunk/BOOK/lxde/desktop/lxde-common.xml
==============================================================================
--- trunk/BOOK/lxde/desktop/lxde-common.xml Thu Sep 24 14:44:04 2015
(r16460)
+++ trunk/BOOK/lxde/desktop/lxde-common.xml Thu Sep 24 18:11:15 2015
(r16461)
@@ -138,35 +138,49 @@
<title>Starting LXDE</title>
<para>
+ You can start <application>LXDE</application> from runlevel 3, using
+ <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager,
+ such as <xref linkend="sddm"/>.
+ </para>
+
+ <para>
To start <application>LXDE</application> using <xref linkend="xinit"/>,
run the following commands:
</para>
<screen><userinput>cat > ~/.xinitrc << "EOF"
-startlxde
+<literal>ck-launch-session dbus-launch --exit-with-session startlxde</literal>
EOF
startx</userinput></screen>
- <note>
<para>
- When <xref linkend="consolekit"/> was built, if you did not use the
- recommended <xref linkend="linux-pam"/> dependency or did not rebuild
- <xref linkend="shadow"/> with Linux-PAM, ~/.xinitrc should have the
- entry:
+ The X session starts on the first unused virtual terminal, normally vt7.
+ You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys
+ Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7,
+ use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many
+ messages there, including X starting messages, applications automatically
+ started with the session, and eventually, some warning and error
+ messages. You may prefer to redirect those messages to a log file, which
+ not only will keep vt1 uncluttered, but also can be used for debug
+ purposes. This can be done starting X with:
</para>
- <screen><userinput>ck-launch-session startlxde</userinput></screen>
+ <screen><userinput>startx &>
~/.x-session-errors</userinput></screen>
+
+ <para>
+ You may wish to drop consolekit and/or dbus-launch, e.g., just using
+ startlxde in .~/.xinitrc, but some functionalities such as mount/umount
+ file systems from a file manager will not be possible, or the reboot
+ option will be absent or not functioning, between other problems.
+ </para>
- <para>to obtain the appropriate permissions for system functions.</para>
-
<para>
- To test if ck-launch-session is needed, run
- <command>ck-list-sessions</command> fropm the command line. If a session
- associated with the current tty is present that is both 'active' and
- 'local' then <command>ck-launch-session</command> is not needed.
+ Because X is (normally) on vt7, when you shutdown the vt is switched back
+ to that one where the command starting it was executed. In this case, if
+ you wish to see the shutdown messages, simultaneously press keys Alt-F7,
+ because normally those messages appear on the vt where X was running.
</para>
- </note>
</sect2>
<!--
Modified: trunk/BOOK/lxqt/desktop/post-install.xml
==============================================================================
--- trunk/BOOK/lxqt/desktop/post-install.xml Thu Sep 24 14:44:04 2015
(r16460)
+++ trunk/BOOK/lxqt/desktop/post-install.xml Thu Sep 24 18:11:15 2015
(r16461)
@@ -84,8 +84,9 @@
<title>Starting LXQt</title>
<para>
- If an optional Display Manager have been installed and you wish to use
it,
- skip the following steps.
+ You can start <application>LXQt</application> from runlevel 3, using
+ <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager,
+ such as <xref linkend="sddm"/>.
</para>
<para>
@@ -93,12 +94,40 @@
run the following commands:
</para>
-<screen><userinput>cat >> ~/.xinitrc << "EOF"
-ck-launch-session startlxqt
+<screen><userinput>cat > ~/.xinitrc << "EOF"
+<literal>ck-launch-session dbus-launch --exit-with-session startlxqt</literal>
EOF
startx</userinput></screen>
+ <para>
+ The X session starts on the first unused virtual terminal, normally vt7.
+ You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys
+ Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7,
+ use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many
+ messages there, including X starting messages, applications automatically
+ started with the session, and eventually, some warning and error
+ messages. You may prefer to redirect those messages to a log file, which
+ not only will keep vt1 uncluttered, but also can be used for debug
+ purposes. This can be done starting X with:
+ </para>
+
+ <screen><userinput>startx &>
~/.x-session-errors</userinput></screen>
+
+ <para>
+ You may wish to drop consolekit and/or dbus-launch, e.g., just using
+ startlxde in .~/.xinitrc, but some functionalities such as mount/umount
+ file systems from a file manager will not be possible, or the reboot
+ option will be absent or not functioning, between other problems.
+ </para>
+
+ <para>
+ Because X is (normally) on vt7, when you shutdown the vt is switched back
+ to that one where the command starting it was executed. In this case, if
+ you wish to see the shutdown messages, simultaneously press keys Alt-F7,
+ because normally those messages appear on the vt where X was running.
+ </para>
+
</sect2>
</sect1>
Modified: trunk/BOOK/postlfs/security/consolekit.xml
==============================================================================
--- trunk/BOOK/postlfs/security/consolekit.xml Thu Sep 24 14:44:04 2015
(r16460)
+++ trunk/BOOK/postlfs/security/consolekit.xml Thu Sep 24 18:11:15 2015
(r16461)
@@ -119,7 +119,9 @@
--enable-udev-acl \
--enable-pam-module \
--enable-polkit \
- --with-systemdsystemunitdir=no &&
+ --with-xinitrc-dir=/etc/X11/app-defaults/xinitrc.d \
+ --docdir=/usr/share/doc/ConsoleKit-&consolekit-version; \
+ --with-systemdsystemunitdir=no &&
make</userinput></screen>
<para>
@@ -130,7 +132,9 @@
Now, as the <systemitem class="username">root</systemitem> user:
</para>
-<screen role="root"><userinput>make install</userinput></screen>
+<screen role="root"><userinput>make install &&
+
+mv -v /etc/X11/app-defaults/xinitrc.d/90-consolekit{,.sh}</userinput></screen>
</sect2>
@@ -150,7 +154,7 @@
<application>PAM</application> module which is needed for
<application>ConsoleKit</application> to work correctly with
<application>PAM</application>. Remove if
- <application>Linux PAM</application> is
+ <application>Linux PAM</application> is
<emphasis role="strong">NOT</emphasis> installed.
</para>
@@ -159,6 +163,13 @@
</para>
<para>
+
<parameter>--with-xinitrc-dir=/etc/X11/app-defaults/xinitrc.d</parameter>:
+ Fix the localization of the 90-consolekit.sh script. Notice that the
+ script was renamed, after installation, because xinitrc expects script
+ names to have extension <emphasis>.sh</emphasis>.
+ </para>
+
+ <para>
<parameter>--with-systemdsystemunitdir=no</parameter>: Disable
attempting to build with systemd libraries.
</para>
@@ -251,11 +262,8 @@
libck-connector.so and pam_ck_connector.so
</seg>
<seg>
- /etc/ConsoleKit,
- /usr/include/ConsoleKit,
- /usr/lib/ConsoleKit,
- /usr/share/doc/ConsoleKit and
- /var/log/ConsoleKit
+ /{etc,usr/{include,lib},var/{log,run}}/ConsoleKit and
+ /usr/share/doc/ConsoleKit-&consolekit-version;
</seg>
</seglistitem>
</segmentedlist>
Modified: trunk/BOOK/x/dm/sddm.xml
==============================================================================
--- trunk/BOOK/x/dm/sddm.xml Thu Sep 24 14:44:04 2015 (r16460)
+++ trunk/BOOK/x/dm/sddm.xml Thu Sep 24 18:11:15 2015 (r16461)
@@ -121,6 +121,18 @@
-s /bin/false sddm</userinput></screen>
<para>
+ First, fix the application to start <command>upowerd</command>,
+ if necessary, and after login, start the session with
+ <command>ck-launch-session</command>:
+ </para>
+
+<screen><userinput>sed -e '/UPOWER_SERVICE)/ s:^://:' \
+ -i src/daemon/PowerManager.cpp &&
+
+sed -e 's/eval exec/& ck-launch-session /' \
+ -i data/scripts/Xsession</userinput></screen>
+
+ <para>
Install <application>SDDM</application> by running the following
commands:
</para>
@@ -131,6 +143,7 @@
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_JOURNALD=OFF \
+ -DDBUS_CONFIG_FILENAME=sddm_org.freedesktop.DisplayManager.conf \
-Wno-dev .. &&
make</userinput></screen>
@@ -161,6 +174,13 @@
</para>
<para>
+
<parameter>-DDBUS_CONFIG_FILENAME=sddm_org.freedesktop.DisplayManager.conf</parameter>:
+ This switch is used for safety reason: other DMs already use
+ <filename>org.freedesktop.DisplayManager.conf</filename>. Verify in your
+ system taht this is not the case, if you wish to remove it.
+ </para>
+
+ <para>
<option>-DBUILD_MAN_PAGES=ON</option>: This switch may be used if you
want
the man pages to be installed. Notice that you need
<ulink url="http://sourceforge.net/projects/docutils/";>Docutils</ulink>
@@ -185,25 +205,33 @@
<para>
This file is not installed with the build instructions, and
- default values are used by sddm. In order to generate the default
- <filename>/etc/sddm.conf</filename>, issue, as the <systemitem
- class="username">root</systemitem> user:
+ default values are used by sddm. In order to generate the example
+ <filename>sddm.example.conf</filename>, issue:
+ </para>
+
+<screen><userinput>sddm --example-config >
sddm.example.conf</userinput></screen>
+
+ <para>
+ We repeat, this command generates an example config file. If there is
+ an already previously installed <filename>/etc/sddm.conf</filename>, it
+ will generate a replica. If there is no yet the
+ <filename>/etc/sddm.conf</filename> file, as the
+ <systemitem class="username">root</systemitem> user, copy the example
+ file to <filename>/etc/sddm.conf</filename>:
</para>
-<screen role="root"><userinput>sddm --example-config >
/etc/sddm.conf</userinput></screen>
+<screen role="root"><userinput>cp -v sddm.example.conf
/etc/sddm.conf</userinput></screen>
<para>
- You need to edit this file, if your system has any unconventional
- characteristics. For example, if Xorg is installed in /opt, use your
- preferred editor as the <systemitem class="username">root</systemitem>
- user to replace the <emphasis>ServerPath</emphasis> and
- <emphasis>XauthPath</emphasis> default paths by
- <emphasis>/opt/xorg/bin/</emphasis>. Or, as the <systemitem
+ Normally, you want to edit this file. For example, if Xorg is installed
+ in /opt, use your preferred editor as the
+ <systemitem class="username">root</systemitem>
+ user to replace the <emphasis>XauthPath</emphasis> default path by
+ <emphasis>/usr/bin/xauth</emphasis>. Or, as the <systemitem
class="username">root</systemitem> user, issue
</para>
<screen role="root"><userinput>sed -e '/ServerPath/ s|usr|opt/xorg|' \
- -e '/XauthPath/ s|usr|opt/xorg|' \
-i.orig /etc/sddm.conf</userinput></screen>
<para>
@@ -211,6 +239,33 @@
file with name <filename>/etc/sddm.conf.orig</filename>.
</para>
+ <para>
+ From now on, we will describe how to modify configurations using sed,
+ but of course you may rather use your preferred editor as the
+ <systemitem class="username">root</systemitem>, instead. You generally
+ want the server option that comes in sddm.example.conf, for security
+ reasons. Unless you want a remote machine to use the local X server,
+ in which case, as the <systemitem class="username">root</systemitem>
+ user, issue:
+ </para>
+
+<screen role="root"><userinput>sed -e 's/-nolisten tcp//'\
+ -i /etc/sddm.conf</userinput></screen>
+
+ <para>
+ Desktop (Notebook) users, normally wish the Num Lock key on (off). For
+ that, as the <systemitem
+ class="username">root</systemitem> user, issue:
+ </para>
+
+<screen role="root"><userinput>sed -e 's/\"none\"/\"on\"/' \
+ -i /etc/sddm.conf</userinput></screen>
+
+ <para>
+ That was for Desktop users. For Notebook users,
+ replace \"on\" by \"off\", in the command above.
+ </para>
+
</sect3>
<sect3 id="sddm-bootscript">
@@ -377,6 +432,16 @@
The BLFS development team have found some issues.
</para>
+ <note>
+ <para>
+ In the next couple of paragraphs, due to a problem with sddm-greeter,
+ we mention how to define the keyboard used there. Notice that this is
+ also the keyboard that will be used in the X session, unless there is
+ a configuration in the Desktop Environment or in the Window Manager
+ overriding it, afterwards.
+ </para>
+ </note>
+
<para>
Keyboard selection: the greeter shows a double question mark or the
wrong keyboard. When you start to type the password or user name
@@ -390,8 +455,11 @@
/usr/share/sddm/scripts/Xsetup</userinput></screen>
<para>
- E.g. <command>echo 'setxkbmap "gb,br,us"' >>
- /usr/share/sddm/scripts/Xsetup</command>
+ E.g. <command>echo 'setxkbmap "fr,gb,br,us"' >>
+ /usr/share/sddm/scripts/Xsetup</command>. You can be accurate defining
+ the keyboard(s), for example: <command>echo 'setxkbmap -model pc105
+ -layout br,us -variant abnt2,dvorak -keycodes evdev' >>
+ /usr/share/sddm/scripts/Xsetup</command>. See man setxkbmap.
</para>
<para>
Modified: trunk/BOOK/x/installing/xinit.xml
==============================================================================
--- trunk/BOOK/x/installing/xinit.xml Thu Sep 24 14:44:04 2015 (r16460)
+++ trunk/BOOK/x/installing/xinit.xml Thu Sep 24 18:11:15 2015 (r16461)
@@ -72,6 +72,13 @@
<sect2 role="installation">
<title>Installation of xinit</title>
+ <para>First, modify <command>startx</command>, hence the X session starts
on
+ the first unused virtual terminal, which normally is vt7:</para>
+ <!--Apparently, this should not be done for systemd systems-->
+
+<screen><userinput>sed -e '/$serverargs $vtarg/ s/serverargs/: #&/' \
+ -i startx.cpp</userinput></screen>
+
<para>Install <application>xinit</application> by running the
following commands:</para>
Modified: trunk/BOOK/xfce/core/xfce4-session.xml
==============================================================================
--- trunk/BOOK/xfce/core/xfce4-session.xml Thu Sep 24 14:44:04 2015
(r16460)
+++ trunk/BOOK/xfce/core/xfce4-session.xml Thu Sep 24 18:11:15 2015
(r16461)
@@ -86,8 +86,8 @@
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
- <xref linkend="desktop-file-utils"/>
- <xref linkend="shared-mime-info"/>, and
+ <xref linkend="desktop-file-utils"/>,
+ <xref linkend="shared-mime-info"/> and
<xref linkend="polkit-gnome"/>
</para>
@@ -149,15 +149,15 @@
<xref linkend="hicolor-icon-theme"/> and
<xref linkend="openssh"/>
</para>
-
+<!--
<para>
To launch <application>Xfce4</application> use the command
<command>startxfce4</command>. If you have <xref linkend="consolekit"/>
- installed, use <command>startxfce4 --with-ck-launch</command>.
+ installed, use <command>startxfce4 -\-with-ck-launch</command>.
<application>ConsoleKit</application> is required to perform any
task that requires administrative access, including shut down
and reboot.
- </para>
+ </para>-->
<para>
When building an <application>Xfce4</application> package, some
@@ -175,6 +175,56 @@
update-mime-database</userinput></screen>
</sect2>
+ <sect2 role="starting">
+ <title>Starting Xfce4</title>
+
+ <para>
+ You can start <application>Xfce4</application> from runlevel 3, using
+ <xref linkend="xinit"/>, or from runlevel 5, using a Display Manager,
+ such as <xref linkend="sddm"/>.
+ </para>
+
+ <para>
+ To start <application>Xfce4</application> using <xref linkend="xinit"/>,
+ run the following commands:
+ </para>
+
+<screen><userinput>cat > ~/.xinitrc << "EOF"
+<literal>ck-launch-session dbus-launch --exit-with-session startxfce4</literal>
+EOF
+
+startx</userinput></screen>
+
+ <para>
+ The X session starts on the first unused virtual terminal, normally vt7.
+ You can switch to a vtn (n=1, 2, ...) simultaneously pressing the keys
+ Ctrl-Alt-Fn. To switch back to the X session, normally started at vt7,
+ use Ctrl-Alt-F7. If started from vt1 (the usual case), you will see many
+ messages there, including X starting messages, applications automatically
+ started with the session, and eventually, some warning and error
+ messages. You may prefer to redirect those messages to a log file, which
+ not only will keep vt1 uncluttered, but also can be used for debug
+ purposes. This can be done starting X with:
+ </para>
+
+ <screen><userinput>startx &>
~/.x-session-errors</userinput></screen>
+
+ <para>
+ You may wish to drop consolekit and/or dbus-launch, e.g., just using
+ startlxde in .~/.xinitrc, but some functionalities such as mount/umount
+ file systems from a file manager will not be possible, or the reboot
+ option will be absent or not functioning, between other problems.
+ </para>
+
+ <para>
+ Because X is (normally) on vt7, when you shutdown the vt is switched back
+ to that one where the command starting it was executed. In this case, if
+ you wish to see the shutdown messages, simultaneously press keys Alt-F7,
+ because normally those messages appear on the vt where X was running.
+ </para>
+
+ </sect2>
+
<sect2 role="content">
<title>Contents</title>
Modified: trunk/bootscripts/ChangeLog
==============================================================================
--- trunk/bootscripts/ChangeLog Thu Sep 24 14:44:04 2015 (r16460)
+++ trunk/bootscripts/ChangeLog Thu Sep 24 18:11:15 2015 (r16461)
@@ -1,3 +1,6 @@
+2015-09-24 Fernando de Oliveira <famobr at yahoo.com.br>
+ * Remove sddm fixes for upowerd.
+
2015-08-23 Fernando de Oliveira <famobr at yahoo.com.br>
* Fix sddm for upowerd stop.
Modified: trunk/bootscripts/blfs/init.d/sddm
==============================================================================
--- trunk/bootscripts/blfs/init.d/sddm Thu Sep 24 14:44:04 2015 (r16460)
+++ trunk/bootscripts/blfs/init.d/sddm Thu Sep 24 18:11:15 2015 (r16461)
@@ -23,20 +23,12 @@
case $1 in
start)
- log_info_msg "Starting upowerd..."
- start_daemon /usr/libexec/upowerd &
- evaluate_retval
-
log_info_msg "Starting SDDM..."
start_daemon $BIN_FILE &
evaluate_retval
;;
stop)
- log_info_msg "Stopping SDDM..."
- killproc $BIN_FILE
- evaluate_retval
-
log_info_msg "Stopping upowerd..."
killproc /usr/libexec/upowerd
evaluate_retval
@@ -50,7 +42,6 @@
status)
statusproc ${BIN_FILE}
- statusproc /usr/libexec/upowerd
;;
*)
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
