https://bugs.kde.org/show_bug.cgi?id=434887
Bug ID: 434887
Summary: Helper processes get reparented to init, making it
hard to identify kde's components in the running
session.
Product: frameworks-kinit
Version: 5.80.0
Platform: Slackware Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: lockyw...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
In the traditional UNIX system, processes are arranged in a nice process tree,
where each child belongs to a single parent, usually the process which launched
the child, thus the process namespace is well structured, and debugging where
unexpected processes are coming from is easy.
However, for some reason, kde's processes get reparented to pid 1, losing this
tree-based sturecture, getting scattered all over the root process namespace,
which makes debugging unexpected system behaviour very hard.
I am using xfce daily, however, as no DE can be providing applications for all
tasks that a user may need, I am ending up using KDE's applications
occasionally. However, launching certain KDE applications (okular in
particular) leads to the whole kde session being started (quite unexpectedly),
and what is more, the helper processes launched by the kde session manager are
not being killed after the original application is terminated, but instead
continue running and interfering with the similar-purpose processes from xfce
(and others).
What is worse, not being an expert in kde makes it very hard to identify those
processes and terminate them manually, since, as mentioned above, the processes
are not arranged in a nice process tree for some reason, but rather scattered
all over the pid 1 namespace.
Please, consider reverting to the traditional UNIX behaviour.
(There may be one case when this behaviour is suboptimal, namely, when kdeinit
is launched as a service from systemd (that is when kde is running as the
primary DE), and kdeinit suddenly dies, the rest of the tree would be killed by
systemd. However, systemd developers knew about such a use-case, and provide
the KillMode=process option for such kind of services (units). Therefore,
systemd-based systems should not be affected by reverting to the traditional
semantics.)
STEPS TO REPRODUCE
1. run xfce
2. launch any application that would require to start kdeinit
3. run pstree to see the processes launched by kdeinit being the adopted
children of pid 1
OBSERVED RESULT
Processes launched by kdeinit are the children of pid 1, as displayed by
pstree.
EXPECTED RESULT
Processes launched by kdeinit are the children of kdeinit, as displayed by
pstree.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.80.0
(available in About System)
KDE Plasma Version: 5.21
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
