<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>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.</p>
<p><br>
</p>
<p>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.<br>
<br>
Please close this bug as we've found systemd to be working nicely. Thanks again for your time and effort.</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div></div>
<div></div>
<br>
<p></p>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Michael Biebl <biebl@debian.org><br>
<b>Sent:</b> Tuesday, February 27, 2024 12:11:12 PM<br>
<b>To:</b> 1064879@bugs.debian.org; Timon de Groot<br>
<b>Subject:</b> Re: systemd: User sessions started from system scope have no journal.</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Control: tags -1 + moreinfo unreproducible<br>
<br>
On Tue, 27 Feb 2024 09:18:02 +0100 Timon de Groot <br>
<timon.degroot@hypernode.com> wrote:<br>
> Package: systemd<br>
> Version: 252.22-1~deb12u1<br>
> Severity: normal<br>
> X-Debbugs-Cc: timon.degroot@hypernode.com<br>
> <br>
> Dear Maintainer,<br>
> <br>
> * What led up to the situation?<br>
> Upstream systemd bugs: #23679, #26742. Can be reproduced when enabling linger for user, rebooting and running journalctl --user.<br>
> * What exactly did you do (or not do) that was effective (or<br>
> ineffective)?<br>
> Create a bookworm VM with a normal user. Enable linger for that user<br>
> (loginctl enable-linger myuser). Reboot the server. Login as that<br>
> user. Run journalctl --user, no new log output from the current<br>
> systemd user session.<br>
> * What was the outcome of this action?<br>
> New output after enabling lingering does seem to get logged into the<br>
> user's journal. Either you only see the old log entries<br>
> that exist from an older systemd user session or you get to see the<br>
> error "No journal files were found, for journalctl"<br>
> * What outcome did you expect instead?<br>
> Running journalctl --user gives proper output.<br>
<br>
<br>
I'm not able to reproduce the problem given the above instructions.<br>
With an up-to-date test VM, I enabled linger for the user "michael", <br>
rebooted, then logged in as "michael" and restarted a couple of user <br>
services like systemctl --user restart dbus.service<br>
<br>
As you can see from the screenshot, they do show up in journalctl --user<br>
<br>
</div>
</span></font>
</body>
</html>