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

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

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

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

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] [NEW] Leaking sessions in pam_systemd

Public bug reported: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) S

[Touch-packages] [Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent

Just faced this bug on 20.04.3 with service apache2 restart. As noted earlier 'systemctl daemon-reload' did fix it, but this workaround is rather not an obvious solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system

[Touch-packages] [Bug 1424566] [NEW] sensible-editor is unexitable

Public bug reported: On fresh Ubuntu 14.04 (trusty) I start 'crontab -e' and a message is shown suggesting to Select an editor, but it is not possible to escape from that dialog without selecting an editor. ctrl+c is not working, q is not working. had to login from other ssh session and kill that