The user session should run under systemd

[Andrea Azzarone]

Currently the user session doesn't run under systemd.
As a consequence:

[Original Description]
In Bionic the systemd .path units are not properly activated.

[Steve Langasek (vorlon)]

We discussed on IRC that this is because *no* systemd units are being activated; the user session is not being run under systemd. This is a regression vs. unity, and should be considered a bug in the desktop session as a whole.

Reassigning this to gnome-session, which seems like the correct starting point.

[Sebastien Bacher (seb128)]

Iain is working on re-enabling the use of systemd user sessions we had under Unity

[Paride Legovini (paride)]

This bug was filed pre-Bionic and explicitly mentions Bionic, but looks like the issue is still present in Jammy:

$ systemctl --user is-active graphical-session.target
inactive

verified in a clean Jammy install and also on Impish (thanks ~ogayot).

Other than the .path units under /usr/lib/systemd/user/graphical-session.target.wants/ all the .service units under /usr/lib/systemd/user/graphical-session-pre.target.wants/ are also not being executed. These are:

  gnome-keyring-ssh.service
  gnome-keyring.service
  session-migration.service
  ssh-agent.service

I'm retitling the bug as it's not only about .path units.

[Paride Legovini (paride)]

Maybe useful: https://wiki.gnome.org/Initiatives/SystemdUser

I'll add that I was confused by this as systemd.special(7) says about graphical-session.target:

  This target is active whenever any graphical session is running. [...]

and it took me a while to figure out that's not true in our case.

[Olivier Gayot (ogayot)]

Apologies for the confusion. I was not using a fresh Impish install.
I just did a clean install and graphical-session.target is reported as active.

[Paride Legovini (paride)]

Interesting, thanks for verifying. I just re-tested this and indeed for `systemctl --user is-active graphical-session.target` we have

 - Impish clean install: active
 - Jammy clean install: inactive

So looks like this we switched to systemd sessions at some point, but this bug never got closed, and then something regressed in Jammy.

[Sebastien Bacher (seb128)]

@Paride, thanks, I'm going to close it if it was fixed it's not the same issue anymore, also Iain isn't working on it at this point? Bug #1959596 is likely the regression you mentioned