Web lists-archives.com

Re: Plasma5 user sessions

Hi Roman,

thanks for your reply!

Am 15.01.2018 um 23:52 schrieb Roman Gilg:
> Hi Max,
> if you're using Plasma 5.11, then you don't need to look into the
>  "plasma-workspace/startkde/waitforname" folder, because 5.11 has it. So
> the notifications should be delayed on your system already. But of course
> you can still take a look and check the patch out, which added it [1],
> because maybe you find a clue why it doesn't work in your setup.

Thanks for the link! I will have a look into it. I'm just beginning to
understand how user sessions work.

> There is also the folder "$HOME/.config/plasma-workspace/env", whose
> scripts gets executed as well on session start, but late in the process to
> my knowledge. So it might be an idea to put your notification script there.

There are two problems with this approach:

We would have to rely on code in the users home directory. This means
anyone could change the code and break things.

Also this slot is too late, since the ksplash is already running. There
are however cases where user interaction is needed during login process.

And the scripts in "$HOME/.config/plasma-workspace/env" are executed by
startkde to set the environment. This would be in my opinion a misuse.

We hook into the user session the same way the ssh agent does: In
"/etc/X11/Xsession.d" there is a variable $STARTUP build up with
processes wrapping each other, finally wrapping the executable from the
selected session in "/usr/share/xsessions".

> Regarding the logout/shutdown: we are talking about a single desktop PC
> with multiple users being logged in at the same time and one of them in his
> currenctly active session requests a shutdown, right? The user also has the
> right to shutdown while other users are logged in, right? First you didn't
> specify where you hook into at the moment to execute your logout tasks.
> logind provides the D-Bus signal PrepareForShutdown, so maybe try to hook
> into this if you don't do it already. Also two years ago there was a change
> to systemd's behavior in killing processes directly [2], so maybe try to
> reverse this behavior with the respective flag. I assume a properly
> configured system should have no problem with this though.

This also happens with a single user session. And this can be reproduced
with an unchanged kde-neon. Just add some echos to the end of startkde
(see attainment). They will be executed if the user just logs out. But
they won't be executed if the user requests a shutdown. This is either a
bug in kdisplaymanager in plsama-workspace or in logind.

As mentioned above we wrap startkde. Therefore the logout task run when
startkde returns.

The logind Option "KillUserProcesses" is switched off in ubuntu by
default. We didn't change that (yet).

> Also consider using systemd user services instead of putting scripts in "
> /etc/X11/Xsession.d" [3].

This would require that the plsama desktop is also started as systemd
user service. Otherwise the desktop would start in parallel to the login
tasks. Correct me if I am wrong, but this is currently not possible.

> Cheers
> Roman
> [1] https://phabricator.kde.org/D5012
> [2]
> https://www.golem.de/news/aufraeumen-von-prozessen-beim-logout-systemd-neuerung-sorgt-fuer-nutzerkontroversen-1605-121176.html
> [3]
> https://superuser.com/questions/1037466/how-to-start-a-systemd-service-after-user-login-and-stop-it-before-user-logout

#  DEFAULT Plasma STARTUP SCRIPT ( 5.11.95 )

# When the X server dies we get a HUP signal from xinit. We must ignore it
# because we still need to do some cleanup.
trap 'echo GOT SIGHUP' HUP

# Check if a Plasma session already is running and whether it's possible to connect to X
if test $kcheckrunning_result -eq 0 ; then
	echo "Plasma seems to be already running on this display."
	xmessage -geometry 500x100 "Plasma seems to be already running on this display." > /dev/null 2>/dev/null
	exit 1
elif test $kcheckrunning_result -eq 2 ; then
	echo "\$DISPLAY is not set or cannot connect to the X server."
        exit 1

# Boot sequence:
# kdeinit is used to fork off processes which improves memory usage
# and startup time.
# * kdeinit starts klauncher first.
# * Then kded is started. kded is responsible for keeping the sycoca
#   database up to date. When an up to date database is present it goes
#   into the background and the startup continues.
# * Then kdeinit starts kcminit. kcminit performs initialisation of
#   certain devices according to the user's settings
# * Then ksmserver is started which takes control of the rest of the startup sequence

if [  ${XDG_CONFIG_HOME} ]; then
  configDir=${HOME}/.config; #this is the default, http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

# We need to create config folder so we can write startupconfigkeys
mkdir -p $configDir

#This is basically setting defaults so we can use them with kstartupconfig5
cat >$configDir/startupconfigkeys <<EOF
kcminputrc Mouse cursorTheme 'breeze_cursors'
kcminputrc Mouse cursorSize ''
ksplashrc KSplash Theme Breeze
ksplashrc KSplash Engine KSplashQML
kdeglobals KScreen ScaleFactor ''
kdeglobals KScreen ScreenScaleFactors ''
kcmfonts General forceFontDPI 0

# preload the user's locale on first start
test -f $plasmalocalerc || {
cat >$plasmalocalerc <<EOF

# export LC_* variables set by kcmshell5 formats into environment
# so it can be picked up by QLocale and friends.
test -f $exportformatssettings && {
    . $exportformatssettings

# Write a default kdeglobals file to set up the font
test -f $kdeglobalsfile || {
cat >$kdeglobalsfile <<EOF

if test $returncode -ne 0; then
    xmessage -geometry 500x100 "kstartupconfig5 does not exist or fails. The error code is $returncode. Check your installation."
    exit 1
[ -r $configDir/startupconfig ] && . $configDir/startupconfig

#Do not sync any of this section with the wayland versions as there scale factors are
#sent properly over wl_output

if [ "$kdeglobals_kscreen_screenscalefactors" ]; then
    export QT_SCREEN_SCALE_FACTORS="$kdeglobals_kscreen_screenscalefactors"
    export GDK_SCALE=$kdeglobals_kscreen_scalefactor
    export GDK_DPI_SCALE=`awk "BEGIN {print 1/$kdeglobals_kscreen_scalefactor}"`
#Manually disable auto scaling because we are scaling above
#otherwise apps that manually opt in for high DPI get auto scaled by the developer AND manually scaled by us

# XCursor mouse theme needs to be applied here to work even for kded or ksmserver
if test -n "$kcminputrc_mouse_cursortheme" -o -n "$kcminputrc_mouse_cursorsize" ; then

    kapplymousetheme "$kcminputrc_mouse_cursortheme" "$kcminputrc_mouse_cursorsize"
    if test $? -eq 10; then
        export XCURSOR_THEME
    elif test -n "$kcminputrc_mouse_cursortheme"; then
        export XCURSOR_THEME
    if test -n "$kcminputrc_mouse_cursorsize"; then
        export XCURSOR_SIZE

if test "$kcmfonts_general_forcefontdpi" -ne 0; then
    xrdb -quiet -merge -nocpp <<EOF
Xft.dpi: $kcmfonts_general_forcefontdpi

unset DESKTOP_LOCKED # Don't want it in the environment

if test -z "$dl"; then
  # the splashscreen and progress indicator
  case "$ksplashrc_ksplash_engine" in
      ksplash_pid=`ksplashqml "${ksplashrc_ksplash_theme}" --pid`

# Source scripts found in <config locations>/plasma-workspace/env/*.sh
# (where <config locations> correspond to the system and user's configuration
# directory.
# This is where you can define environment variables that will be available to
# all KDE programs, so this is where you can run agents using e.g. eval `ssh-agent`
# or eval `gpg-agent --daemon`.
# Note: if you do that, you should also put "ssh-agent -k" as a shutdown script
# (see end of this file).
# For anything else (that doesn't set env vars, or that needs a window manager),
# better use the Autostart folder.

scriptpath=`echo "$configDir:$sysConfigDirs" | tr ':' '\n'`

for prefix in `echo $scriptpath`; do
  for file in "$prefix"/plasma-workspace/env/*.sh; do
    test -r "$file" && . "$file" || true

# Activate the kde font directories.
# There are 4 directories that may be used for supplying fonts for KDE.
# There are two system directories. These belong to the administrator.
# There are two user directories, where the user may add her own fonts.
# The 'override' versions are for fonts that should come first in the list,
# i.e. if you have a font in your 'override' directory, it will be used in
# preference to any other.
# The preference order looks like this:
# user override, system override, X, user, system
# Where X is the original font database that was set up before this script
# runs.


if test -n "$KDEDIRS"; then
  kdedirs_first=`echo "$KDEDIRS"|sed -e 's/:.*//'`

# We run mkfontdir on the user's font dirs (if we have permission) to pick
# up any new fonts they may have installed. If mkfontdir fails, we still
# add the user's dirs to the font path, as they might simply have been made
# read-only by the administrator, for whatever reason.

test -d "$sys_odir" && xset +fp "$sys_odir"
test -d "$usr_odir" && (mkfontdir "$usr_odir" ; xset +fp "$usr_odir")
test -d "$usr_fdir" && (mkfontdir "$usr_fdir" ; xset fp+ "$usr_fdir")
test -d "$sys_fdir" && xset fp+ "$sys_fdir"

# Ask X11 to rebuild its font list.
xset fp rehash

# Set a left cursor instead of the standard X11 "X" cursor, since I've heard
# from some users that they're confused and don't know what to do. This is
# especially necessary on slow machines, where starting KDE takes one or two
# minutes until anything appears on the screen.
# If the user has overwritten fonts, the cursor font may be different now
# so don't move this up.
xsetroot -cursor_name left_ptr

# Get Ghostscript to look into user's KDE fonts dir for additional Fontmap
if test -n "$GS_LIB" ; then
    export GS_LIB
    export GS_LIB

echo 'startkde: Starting up...'  1>&2

# Make sure that the KDE prefix is first in XDG_DATA_DIRS and that it's set at all.
# The spec allows XDG_DATA_DIRS to be not set, but X session startup scripts tend
# to set it to a list of paths *not* including the KDE prefix if it's not /usr or
# /usr/local.
if test -z "$XDG_DATA_DIRS"; then

# Mark that full KDE session is running (e.g. Konqueror preloading works only
# with full KDE running). The KDE_FULL_SESSION property can be detected by
# any X client connected to the same X session, even if not launched
# directly from the KDE session but e.g. using "ssh -X", kdesu. $KDE_FULL_SESSION
# however guarantees that the application is launched in the same environment
# like the KDE session and that e.g. KDE utilities/libraries are available.
# KDE_FULL_SESSION property is also only available since KDE 3.5.5.
# The matching tests are:
#     if test -n "$KDE_FULL_SESSION"; then ... whatever
#   For KDE_FULL_SESSION property:
#     xprop -root | grep "^KDE_FULL_SESSION" >/dev/null 2>/dev/null
#     if test $? -eq 0; then ... whatever
# Additionally there is (since KDE 3.5.7) $KDE_SESSION_UID with the uid
# of the user running the KDE session. It should be rarely needed (e.g.
# after sudo to prevent desktop-wide functionality in the new user's kded).
# Since KDE4 there is also KDE_SESSION_VERSION, containing the major version number.
# Note that this didn't exist in KDE3, which can be detected by its absense and
# the presence of KDE_FULL_SESSION.
xprop -root -f KDE_FULL_SESSION 8t -set KDE_FULL_SESSION true




# At this point all environment variables are set, let's send it to the DBus session server to update the activation environment
if which dbus-update-activation-environment >/dev/null 2>/dev/null ; then
    dbus-update-activation-environment --systemd --all
if test $? -ne 0; then
  # Startup error
  echo 'startkde: Could not sync environment to dbus.'  1>&2
  test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
  xmessage -geometry 500x100 "Could not sync environment to dbus."
  exit 1

# We set LD_BIND_NOW to increase the efficiency of kdeinit.
# kdeinit unsets this variable before loading applications.
LD_BIND_NOW=true /usr/lib/x86_64-linux-gnu/libexec/kf5/start_kdeinit_wrapper --kded +kcminit_startup
if test $? -ne 0; then
  # Startup error
  echo 'startkde: Could not start kdeinit5. Check your installation.'  1>&2
  test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
  xmessage -geometry 500x100 "Could not start kdeinit5. Check your installation."
  exit 1

qdbus org.kde.KSplash /KSplash org.kde.KSplash.setStage kinit &

# finally, give the session control to the session manager
# see kdebase/ksmserver for the description of the rest of the startup sequence
# if the KDEWM environment variable has been set, then it will be used as KDE's
# window manager instead of kwin.
# if KDEWM is not set, ksmserver will ensure kwin is started.
# kwrapper5 is used to reduce startup time and memory usage
# kwrapper5 does not return useful error codes such as the exit code of ksmserver.
# We only check for 255 which means that the ksmserver process could not be
# started, any problems thereafter, e.g. ksmserver failing to initialize,
# will remain undetected.
test -n "$KDEWM" && KDEWM="--windowmanager $KDEWM"
# If the session should be locked from the start (locked autologin),
# lock now and do the rest of the KDE startup underneath the locker.
test -n "$dl" && KSMSERVEROPTIONS=" --lockscreen"
kwrapper5 /usr/bin/ksmserver $KDEWM $KSMSERVEROPTIONS
if test $? -eq 255; then
  # Startup error
  echo 'startkde: Could not start ksmserver. Check your installation.'  1>&2
  test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
  xmessage -geometry 500x100 "Could not start ksmserver. Check your installation."

#Anything after here is logout/shutdown

echo "Checkpoint 1" > ~/startkde.log

wait_drkonqi=`kreadconfig5 --file startkderc --group WaitForDrKonqi --key Enabled --default true`

echo "Checkpoint 2" >> ~/startkde.log

if test x"$wait_drkonqi"x = x"true"x ; then
    # wait for remaining drkonqi instances with timeout (in seconds)
    wait_drkonqi_timeout=`kreadconfig5 --file startkderc --group WaitForDrKonqi --key Timeout --default 900`
    while qdbus | grep "^[^w]*org.kde.drkonqi" > /dev/null ; do
        sleep 5
        if test "$wait_drkonqi_counter" -ge "$wait_drkonqi_timeout" ; then
            # ask remaining drkonqis to die in a graceful way
            qdbus | grep 'org.kde.drkonqi-' | while read address ; do
                qdbus "$address" "/MainApplication" "quit"

echo "Checkpoint 3" >> ~/startkde.log

echo 'startkde: Shutting down...'  1>&2
# just in case
test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null

echo "Checkpoint 4" >> ~/startkde.log

# Clean up

echo "Checkpoint 5" >> ~/startkde.log

xprop -root -remove KDE_FULL_SESSION
xprop -root -remove KDE_SESSION_VERSION

echo "Checkpoint 6" >> ~/startkde.log

echo 'startkde: Done.'  1>&2