As discussed on IRC, the user ID on my test system is 1000, but we figured out the real problem was the SplitMode=none configuration on my testing system. After disabling that setting (so leaving it to the default SplitMode=uid), the expected behavior was happening again.
Some case could be made that there's a problem/bug around SplitMode=none with user sessions, but I feel like that's not really worth investing time/effort into. Please close this bug as we've found systemd to be working nicely. Thanks again for your time and effort. ________________________________ From: Michael Biebl <bi...@debian.org> Sent: Tuesday, February 27, 2024 12:11:12 PM To: 1064...@bugs.debian.org; Timon de Groot Subject: Re: systemd: User sessions started from system scope have no journal. Control: tags -1 + moreinfo unreproducible On Tue, 27 Feb 2024 09:18:02 +0100 Timon de Groot <timon.degr...@hypernode.com> wrote: > Package: systemd > Version: 252.22-1~deb12u1 > Severity: normal > X-Debbugs-Cc: timon.degr...@hypernode.com > > Dear Maintainer, > > * What led up to the situation? > Upstream systemd bugs: #23679, #26742. Can be reproduced when enabling > linger for user, rebooting and running journalctl --user. > * What exactly did you do (or not do) that was effective (or > ineffective)? > Create a bookworm VM with a normal user. Enable linger for that user > (loginctl enable-linger myuser). Reboot the server. Login as that > user. Run journalctl --user, no new log output from the current > systemd user session. > * What was the outcome of this action? > New output after enabling lingering does seem to get logged into the > user's journal. Either you only see the old log entries > that exist from an older systemd user session or you get to see the > error "No journal files were found, for journalctl" > * What outcome did you expect instead? > Running journalctl --user gives proper output. I'm not able to reproduce the problem given the above instructions. With an up-to-date test VM, I enabled linger for the user "michael", rebooted, then logged in as "michael" and restarted a couple of user services like systemctl --user restart dbus.service As you can see from the screenshot, they do show up in journalctl --user
