Re: [Evolution] Proposal regarding apparent race condition on Evolution start-up - SOLVED

[Patrick O'Callaghan <poc usb ve>]

On Wed, 2020-02-12 at 17:11 +0000, Patrick O'Callaghan wrote:
> On Wed, 2020-02-12 at 14:37 +0100, Milan Crha via evolution-list wrote:
> > Using `loginctl list-sessions` and being logged in as a root in a text
> > terminal I see that there are two sessions, one for the root and one
> > for the logged used in the KDE desktop. When I log out of the KDE,
> > there are left both sessions as before and one is added, for user
> > 'sddm'. When I log in as the previous user again the loginctl shows 3
> > sessions, two for the user I used for KDE login and the one for root. I
> > definitely should not have running two sessions for my user. (In other
> > words, the issue in the above mentioned bug is not specific to gnome-
> > session only, even it is filled against it.)
>
> This is looking like the root problem (or one of them ...). I tried
> listing sessions. logging out and in again, and listing them again:
>
> SESSION  UID USER SEAT  TTY 
>      11 1000 poc  seat0     
>      13 1000 poc  seat0     
>       2    0 root seat0 tty2
>       4 1000 poc  seat0     
>       8 1000 poc  seat0     
>
> 5 sessions listed.
> ---
>
> SESSION  UID USER SEAT  TTY 
>      11 1000 poc  seat0     
>      13 1000 poc  seat0     
>      15 1000 poc  seat0     
>       2    0 root seat0 tty2
>       4 1000 poc  seat0     
>       8 1000 poc  seat0     
>
> 6 sessions listed.
> ---
>
> IOW each login is creating a new session, but logging out is not
> terminating it. This definitely looks like a bug of some kind. Whether
> or not it's what causes the g-k-r problem is not clear, but it should
> be investigated. I'll take it to the KDE list and possibly BZ.

OK, after a brief discussion on the KDE list (thanks Ed) I modified
/etc/systemd/logind.conf to change the KillUserProcesses entry to
'yes'. I also rebooted.

Now when I log out of KDE, g-k-r is not left running and there are no
abandoned sessions under my userid. Logging in starts up Evo with no
password pop-up, every time.

My theory is that previously there were extraneous processes sitting on
the DBus entry and mixing things up in some way, possibly in a race
condition.

As of now, touch wood, the problem appears to be solved.

Thanks to all.

poc