What is the expected behaviour of konsole with systemd scopes?

Help
,
1

Hi all.

I’d like some clarification on how konsole is supposed to make use of systemd scope units.
The impression I had is that each tab in konsole gets it’s own scope unit, so that services like systemd-oomd can just kill the tab that triggers the OOM event. See this merge request.

The following is from systemd-cgls. In this scenario konsole has 6 tabs open. Tab 1 is running systemd-cgls,. Tabs 2 and 3 have vim open. The rest just have an idle bash prompt.

├─app-org.kde.konsole@20b73c0ccd4644f08a482ebf848e79d6.service
│ ├─14443 /usr/bin/bash
│ ├─16197 systemd-cgls
│ └─16198 less
├─app-org.kde.konsole-14429.scope
│ ├─14429 /usr/bin/konsole
│ ├─15611 /usr/bin/bash
│ ├─15613 /usr/bin/bash
│ ├─15615 /usr/bin/bash
│ ├─15617 /usr/bin/bash
│ ├─15619 /usr/bin/bash
│ ├─15684 vim text.text
│ └─15692 vim "hello world.txt"

There is clearly no separation between each tab. Only tab 1 is in it’s own control group, and everything else is piled into another.

I’m quite sure this a bug, but I’d just like to make sure I’m not missing anything before opening a bug report.

Regards

Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland

2

I cannot help, but some time ago I was wondering why Konsole gets killed together with the process that triggers the OOM, while the Gnome Terminal does not suffer from this problem.

For posterity, I have connected the two related bugs (both are closed, though).