[Systems] Fwd: Killing the systemd user session on logout

[Bernie Innocenti]

I didn't know this!


 From the opendkim.conf manpage:

---cut---
Canonicalization (string)
Selects the canonicalization method(s) to be used when signing messages. 
  When verifying, the message's DKIM-Signature: header  field  specifies 
  the canonicalization  method.   The recognized values are relaxed and 
simple as defined by the DKIM specification.  The default is simple. 
The value may include two different canonicalizations separated by a 
slash ("/") character, in which case the first will be applied to the 
header and the second to the body.
---cut---

I'll try changing it...

-------- Forwarded Message --------
Subject: Re: Killing the systemd user session on logout
Date: Sun, 12 Jul 2020 07:02:51 +1200
From: Ben Cooksley <bcooksley at kde.org>
To: bernie at codewiz.org

Hi Bernie,

Just as a note, about half of the subscribers to the list won't have
seen your email as the DKIM signature on your email broke when it
transitioned through KDE.org infrastructure. As a consequence, your
DMARC policies for the domain will cause providers to either refuse or
immediately send the email to spam (which is what happened for me)

This is due to your DKIM signature being in c=simple/simple mode,
rather than c=relaxed/relaxed mode.

When in simple mode, any changes to the technical formatting of a
message cause the signature to break, even if the actual content is
left completely unchanged. Unfortunately when messages pass via
Mailman, it re-encodes the content of the message, which often breaks
these c=simple/simple signatures.

If you could change your setup (looks like sugarlabs.org run it for
you) to use relaxed/relaxed mode, then this should be resolved. If
they're using OpenDKIM then they can do this using the following
setting:
Canonicalization        relaxed/relaxed

Regards,
Ben


On Sun, Jul 12, 2020 at 3:15 AM Bernie Innocenti <bernie at codewiz.org> wrote:
>
> I'm trying to fix this longstanding bug where there are dangling user
> processes after the desktop session exists:
>
>    https://bugs.kde.org/show_bug.cgi?id=359651
>
> This is reproducible every time on multiple distributions and KDE
> versions. It also causes subsequent logins to fail or behave
> surprisingly due to the presence of extraneous dbus services, pulseaudio
> clients, etc.
>
> I looked into plasma-workspace/startkde, and there's no hint of it
> starting "systemd --user" directly. There's this cli tool called
> "kde-systemd-start-condition" (which appears to be unused), and a few
> other mentions of logind and systemd, but nothing really relevant.
>
> Am I looking in the wrong place?
>
> --
> _ // Bernie Innocenti
> \X/  https://codewiz.org/