Thanks for this feedback pbear, which got me to dig a bit more thoroughly into what might be automatically launched with mate, but that still reveals nothing to give me a y clue.
I have essentially the same setup as your test box, so that adds to the mystery -- especially having not added very much since the same plain vanilla bookworm installation (also with autologin through LightDM) you have.
I get mail through evolution, which is the only thing set up to use the keyring, but I only have that running when I launch it manually. I do know it is highly integrated with the keyring system, e.g. trying to remove the package gnome-keyring forces the removal of evolution, so perhaps installing this latest version of evolution somehow is doing this (which was not the case in the version that came with stretch - the last debian I had before bookworm).
Can you see if just installing evolution on your test box creates the same issue for you? If so, then we have at least nailed down the cause to be somehow connected to the installation of evolution.
I have unchecked the only possibly related culprit under "System -> Control Center -> Startup Applications", the "SSH Key Agent", but that makes no difference.
Nothing in /etc/init.d launches it directly, but maybe someone can tell whether anything I have in there might be forcing the keyring to start indirectly:I am now very curious to get to the bottom of this, as it seems well beyond my present debugging capabilities ![:cry:]( "Crying or Very sad")
I have essentially the same setup as your test box, so that adds to the mystery -- especially having not added very much since the same plain vanilla bookworm installation (also with autologin through LightDM) you have.
I get mail through evolution, which is the only thing set up to use the keyring, but I only have that running when I launch it manually. I do know it is highly integrated with the keyring system, e.g. trying to remove the package gnome-keyring forces the removal of evolution, so perhaps installing this latest version of evolution somehow is doing this (which was not the case in the version that came with stretch - the last debian I had before bookworm).
Can you see if just installing evolution on your test box creates the same issue for you? If so, then we have at least nailed down the cause to be somehow connected to the installation of evolution.
I have unchecked the only possibly related culprit under "System -> Control Center -> Startup Applications", the "SSH Key Agent", but that makes no difference.
Nothing in /etc/init.d launches it directly, but maybe someone can tell whether anything I have in there might be forcing the keyring to start indirectly:
Code:
root@nickspanasonic:~# ls -l /etc/init.dtotal 104-rwxr-xr-x 1 root root 5623 Nov 30 2022 alsa-utils-rwxr-xr-x 1 root root 2055 Jan 10 2023 anacron-rwxr-xr-x 1 root root 3740 Feb 14 2023 apparmor-rwxr-xr-x 1 root root 2948 Dec 10 08:57 bluetooth-rwxr-xr-x 1 root root 1235 May 21 2023 console-setup.sh-rwxr-xr-x 1 root root 3059 Jul 17 2022 cron-rwxr-xr-x 1 root root 2804 Dec 1 11:35 cups-rwxr-xr-x 1 root root 1961 May 19 2023 cups-browsed-rwxr-xr-x 1 root root 3152 Sep 16 2023 dbus-rwxr-xr-x 1 root root 3029 Jan 29 2023 gdm3-rwxr-xr-x 1 root root 1748 Feb 13 2023 hwclock.sh-rwxr-xr-x 1 root root 1482 Jul 18 2022 keyboard-setup.sh-rwxr-xr-x 1 root root 2063 Dec 9 2022 kmod-rwxr-xr-x 1 root root 2610 Jan 11 2022 lightdm-rwxr-xr-x 1 root root 4531 Jan 23 2023 networking-rwxr-xr-x 1 root root 1386 Feb 1 2023 plymouth-rwxr-xr-x 1 root root 760 Feb 1 2023 plymouth-log-rwxr-xr-x 1 root root 959 Dec 18 2022 procps-rwxr-xr-x 1 root root 2224 May 16 2023 saned-rwxr-xr-x 1 root root 2040 Sep 25 2022 speech-dispatcher-rwxr-xr-x 1 root root 1161 Jun 27 2023 sudo-rwxr-xr-x 1 root root 6871 Jan 26 13:46 udev-rwxr-xr-x 1 root root 2762 Aug 18 2021 x11-commonroot@nickspanasonic:~# 
Statistics: Posted by gurfle — 2024-04-06 22:22