https://bugs.kde.org/show_bug.cgi?id=356580
Bug ID: 356580
Summary: startplasmacompositor - kwin_wayland -
"/usr/lib/startplasma" - hangs at
"start_kdeinit_wrapper"
Product: frameworks-kinit
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: ja...@nurealm.net
CC: kdelibs-b...@kde.org
Arch Linux
plasma-workspace 5.5.0-4 - /usr/bin/startplasmacompositor and
/usr/lib/startplasma and /usr/bin/ksmserver
kwin 5.5.0-2 - /usr/bin/kwin_wayland
kinit 5.17.0-1 - /usr/lib/kf5/start_kdeinit_wrapper and /usr/bin/kdeinit5
Reproducible: Always
Steps to Reproduce:
/usr/bin/startplasmacompositor begets /usr/bin/kwin_wayland which begets
/usr/lib/startplasma, which gets as far as
LD_BIND_NOW=true /usr/lib/kf5/start_kdeinit_wrapper --kded +kcminit_startup
which hangs, and blocks the subsequent /usr/bin/ksmserver.
Actual Results:
The user will see the splash screen and then only a blank desktop with a
working mouse. Applications can be started from another terminal, or the
session can be killed from another terminal, but only if the user remembers to
"Ctrl-Alt-F2". The session cannot be killed from within the Wayland display
since the graphic shell never starts.
Martin Gräßlin, at https://git.reviewboard.kde.org/r/124293/, 2015 July,
mentions explicitly about "startplasma" that "There's still the problem that it
needs a patched kdeinit with OOM_PROTECT disabled." And again, at
https://plus.google.com/+MartinGräßlin/posts/4T3D7bpZESv
Martin mentions "kdeinit dead locks with the oom protection."
But, the "/usr/bin/kdeinit5" provided by the recent kinit 5.17.0-1 runs as
/usr/bin/kdeinit5 --oom-pipe 4 --kded +kcminit_startup
apparently with OOM_PROTECT still enabled, *by default*. We still see in
"kinit-5.17.0/src/CMakeLists.txt"
set(KDEINIT_OOM_PROTECT 1)
which can be seen to apply to src/kdeinit/kinit.cpp,
src/start_kdeinit/start_kdeinit.c, and
src/start_kdeinit/start_kdeinit_wrapper.c.
Soooooo - In order to allow people to run kwin_wayland, for now, until the OOM
problem is resolved, it would seem better to choose
set(KDEINIT_OOM_PROTECT)
to "unset" KDEINIT_OOM_PROTECT, *as the default* - or, at least provide a big
fat end-user visible warning about the use of "startplasmacompositor", with
respect to being "available" or "not available".
Also, KDEINIT_OOM_PROTECT cannot be "unset" from the toplevel CMakeLists.txt,
so some changes there would also be useful.
--
You are receiving this mail because:
You are watching all bug changes.
