Comment 3 for bug 1977652

Funny you should ask. I tempted to ask where you think I got the output from in the first place. But I shall refrain from sarcasm as that won't do any good.

This does put me in a bit of a pickle. Because in order for the journalctl output to be more useful than just the 40.000 message I referenced, I should leave it untouched. But I cannot give it to you unsanitized either.

I'm attaching the log uniq -c'd, starting just before the issue at hand, so I could inspect it for private details. Observe that the `1501` on the left means 1501x the same message in lines like:

   1501 jun 04 15:01:55 myhostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.

I hope this is convincing enough that I'm not making this up.

As for the:

> I believe the commit you referenced has been in jammy since 249.9-0ubuntu1.

Okay. Well. If I apt-get source systemd, I would assume that I'd get that as a patch file. But grepping for "unit_has_failed_condition_or_assert" in ./debian/patches yields nothing. Grepping for -i "condition": no relevant hits.

Are you sure this patch is included? If so, then only parts if it maybe?

Regards,
Walter