As part of an ongoing thread on the Evolution list: https://mail.gnome.org/archives/evolution-list/2020-February/msg00041.html it turns out that logging into KDE creates a new session (in the sense of loginctl(1)) but logging out doesn't terminate it. Thus every time you log out and in again the number of sessions increases. You can verify this by running 'loginctl --list-sessions'. Is this a bug?

On 2020-02-13 01:16, Patrick O'Callaghan wrote: > As part of an ongoing thread on the Evolution list: > > https://mail.gnome.org/archives/evolution-list/2020-February/msg00041.html > > it turns out that logging into KDE creates a new session (in the sense > of loginctl(1)) but logging out doesn't terminate it. Thus every time > you log out and in again the number of sessions increases. You can > verify this by running 'loginctl --list-sessions'. > > Is this a bug? > I don't think so. But I did have issues with that "feature". (Can't recall what as it was some time ago) So, I always will edit /etc/systemd/logind.conf to have KillUserProcesses=yes

This isn't a KDE thing, it's systemd. See e.g. [1] and [2]. [1] https://forum.xfce.org/viewtopic.php?id=12994 [2] https://wiki.archlinux.org/index.php/Systemd/User#Kill_user_processes_on_...

On Thu, 13 Feb 2020 at 11:56, Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; wrote: > On Thu, 2020-02-13 at 00:34 +0100, Iñaki Ucar wrote: > > This isn't a KDE thing, it's systemd. See e.g. [1] and [2]. > > > > [1] https://forum.xfce.org/viewtopic.php?id=12994 > > [2] https://wiki.archlinux.org/index.php/Systemd/User#Kill_user_processes_on_... > > I know what causes it. My point is that the problem occurs with KDE and > other desktops, but not apparently with Gnome, so it would be > interesting to know why this is. Does systemd treat Gnome specially, or > does Gnome have some kind of built-in workaraound that avoids this > issue? Are you sure that this doesn't happen with Gnome?

There was a change in systemd some years ago [1] to KillUSerProcesses by default, and if you follow the trail, this triggered lively debate. Particularly, we had [2] in Fedora, and there was even a change proposal [3] to follow the decision upstream, but it was first delayed and then never implemented [4]. Maybe Zbigniew (in CC), the owner, could tell us why.

And maybe this topic could be resurrected in devel if there's renewed interest, but you are probably going to find opposition; because this is fine for multi-user workstations, but it breaks things in servers. IMHO, in a perfect world, each flavour (Workstation, Server, KDE...) should decide and explicitly set the default option.

On Thu, 13 Feb 2020 at 13:43, Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; wrote: > On Thu, 2020-02-13 at 13:15 +0100, Iñaki Ucar wrote: > > On Thu, 13 Feb 2020 at 11:56, Patrick O'Callaghan <pocallaghan(a)gmail.com&gt; wrote: > > > On Thu, 2020-02-13 at 00:34 +0100, Iñaki Ucar wrote: > > > > This isn't a KDE thing, it's systemd. See e.g. [1] and [2]. > > > > > > > > [1] https://forum.xfce.org/viewtopic.php?id=12994 > > > > [2] https://wiki.archlinux.org/index.php/Systemd/User#Kill_user_processes_on_... > > > > > > I know what causes it. My point is that the problem occurs with KDE and > > > other desktops, but not apparently with Gnome, so it would be > > > interesting to know why this is. Does systemd treat Gnome specially, or > > > does Gnome have some kind of built-in workaraound that avoids this > > > issue? > > > > Are you sure that this doesn't happen with Gnome? > > No, I'm simply relying on some comments in the above references. AFAIK, it does happen in Gnome too, because that's entirely to systemd (unless gdm does something special nowadays). E.g.: https://bbs.archlinux.org/viewtopic.php?id=204307

> > There was a change in systemd some years ago [1] to KillUSerProcesses > > by default, and if you follow the trail, this triggered lively debate. > > Particularly, we had [2] in Fedora, and there was even a change > > proposal [3] to follow the decision upstream, but it was first delayed > > and then never implemented [4]. Maybe Zbigniew (in CC), the owner, > > could tell us why. > > I'll take a look at those, thanks. > > > And maybe this topic could be resurrected in devel if there's renewed > > interest, but you are probably going to find opposition; because this > > is fine for multi-user workstations, but it breaks things in servers. > > IMHO, in a perfect world, each flavour (Workstation, Server, KDE...) > > should decide and explicitly set the default option. > > Sounds like a good idea. I don't see why it should break things in > servers, but maybe that's clarified in the links you mention. TL;DR: it kills processes when you log out. So if you ssh into the machine, launch something using tmux/screen/nohup, and then log out, these processes get killed. You have further details and discussion in the links provided (and in other forums in other distros if you take a look too).

don't understand is https://fedoraproject.org/wiki/Changes/KillUserProcesses_by_default which says that KillUserProcesses is now the default, when it clearly isn't. I did a fresh install of F31 a couple of months ago and that setting had not changed until I edited it myself.

On Thursday, February 13, 2020 2:06:06 PM CET Patrick O'Callaghan wrote: What I > don't understand is > https://fedoraproject.org/wiki/Changes/KillUserProcesses_by_default > which says that KillUserProcesses is now the default, when it clearly isn't. > I did a fresh install of F31 a couple of months ago and that setting had > not changed until I edited it myself. That wiki page is only a proposal that was never accepted in any Fedora release. Unfortunately, the only way I know to detect if a proposal has been accepted is to look at the wiki page categories, at the bottom of the page. Accepted changes like the following one have a special category, like "ChangeAccepted26": https://fedoraproject.org/wiki/Changes/Python3.6