[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2024-02-23 Thread Nick Rosbrook
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2020177 Title: Leaking sessions in pam_systemd Status

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-13 Thread Nick Rosbrook
You don't have any logs for systemd-logind? Have you modified the log level at some point? I guess that bug does sound similar, but it is unclear and there is no real resolution on that bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is s

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-13 Thread non7top
My systemd reports # systemd --version systemd 245 (245.4-4ubuntu3.21) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid -- You received this bug notification becaus

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-13 Thread non7top
Could be this bug https://github.com/systemd/systemd/issues/8672 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2020177 Title: Leaking sessions in pam_systemd Status in

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-13 Thread non7top
Not sure what the "boot" is, but here are the outputs from the same system: # journalctl -u systemd-logind.service -b 0 -- Logs begin at Tue 2023-06-13 11:39:06 MSK, end at Tue 2023-06-13 12:44:33 MSK. -- -- No entries -- # loginctl session-status 302548700 302548700 - topaz (450) Si

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-12 Thread Nick Rosbrook
Can you please attach logs from a boot where this was seen? If the current boot exhibits this, you can use 0 as the boot id: $ journalctl -u systemd-logind.service -b $boot_id > systemd-logind- logs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded package

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-12 Thread non7top
Well. I don't see any processes in the OS that would correspond to those sessions. The state of most of them is Closing. systemd also spams a lot about too many sessions. Looks like systemd doesn't close sessions properly. -- You received this bug notification because you are a member of Ubuntu T

[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd

2023-06-09 Thread Nick Rosbrook
What makes you say the sessions are "leaked", exactly? Is there something odd about the sessions listed? I realize that is a large number, however. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seed