Bug 516103

SUMMARY
When starting a non-KDE session (e.g., GNOME), a `ksecretd` process automatically starts, presumably by the following lines in `/etc/pam.d/passwd`:

```
-password	optional	pam_gnome_keyring.so
-password	optional	pam_kwallet5.so
```

I'm unsure if it should start in non-KDE session or not. Anyway, when logged out of the session, the process remains, and blocking `systemd --user` and a few services from stopping. So a few processes of the user would remain after logout.

`loginctl user-status <user>` would show the status as "closing".

Manually killing the `ksecretd` process would cause `systemd --user` and other services to correctly stop.

STEPS TO REPRODUCE
1. Create a new user "test".
2. Login to the user "test" in a GNOME session.
3. Logout.

OBSERVED RESULT
`htop` would show a few processes belonging to the user "test" still running, including `ksecretd`.
Killing `ksecretd`, then all other processes of the user "test" will also quit.

EXPECTED RESULT
`htop` would show no processes belonging to the user "test".

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.91
KDE Frameworks Version: 6.23.0
Qt Version: 6.11.0
Kernel Version: 6.18.9-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics