LINUX.ORG.RU

Выбивает из сессии при выходе из спящего

 ,


0

1

После апгрейда до 20.04 вознила проблема - при выходе из спящего режима и вводе пароля, через интервал от 0.5 до 10 секунд, происходит самопроизвольный запуск окна логина lightdm. После повторного логина все запущенные программы на месте, но задалбывает жутко.

Полез ковыряться в логи, похоже, что systemd гадит (08:34:12 - момент принудительного логина):

/var/log/auth.log

Sep 17 01:40:33 home su: (to eagleivg) root on none
Sep 17 01:40:33 home su: pam_unix(su-l:session): session opened for user eagleivg by (uid=0)
Sep 17 01:40:33 home su: pam_unix(su-l:session): session closed for user eagleivg
Sep 17 08:32:42 home su: (to eagleivg) root on none
Sep 17 08:32:42 home su: pam_unix(su-l:session): session opened for user eagleivg by (uid=0)
Sep 17 08:32:50 home lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Sep 17 08:32:50 home systemd-logind[929]: New session c9 of user lightdm.
Sep 17 08:32:50 home systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Sep 17 08:32:51 home lightdm: gkr-pam: gnome-keyring-daemon started properly
Sep 17 08:32:51 home lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "eagleivg"
Sep 17 08:32:51 home lightdm: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory
Sep 17 08:33:34 home lightdm: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory
Sep 17 08:33:34 home lightdm: gkr-pam: unable to locate daemon control file
Sep 17 08:33:34 home lightdm: gkr-pam: stashed password to try later in open session
Sep 17 08:33:35 home systemd-logind[929]: Removed session c9.
Sep 17 08:34:12 home systemd-logind[929]: Operation 'sleep' finished.
Sep 17 08:34:14 home lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Sep 17 08:34:14 home systemd-logind[929]: New session c10 of user lightdm.
Sep 17 08:34:14 home systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Sep 17 08:34:14 home lightdm: gkr-pam: gnome-keyring-daemon started properly
Sep 17 08:34:14 home lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "eagleivg"
Sep 17 08:34:14 home lightdm: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory
Sep 17 08:34:17 home lightdm: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory
Sep 17 08:34:17 home lightdm: gkr-pam: unable to locate daemon control file
Sep 17 08:34:17 home lightdm: gkr-pam: stashed password to try later in open session
Sep 17 08:34:17 home systemd-logind[929]: Removed session c10.
Sep 17 08:34:50 home su: pam_unix(su-l:session): session closed for user eagleivg
Sep 17 08:35:01 home CRON[9853]: pam_unix(cron:session): session opened for user eagleivg by (uid=0)
Sep 17 08:35:01 home CRON[9853]: pam_unix(cron:session): session closed for user eagleivg 

/var/log/syslog

Sep 17 08:33:45 home systemd[7094]: Closed Sound System.
Sep 17 08:33:45 home systemd[7094]: Reached target Shutdown.
Sep 17 08:33:45 home systemd[7094]: systemd-exit.service: Succeeded.
Sep 17 08:33:45 home systemd[7094]: Finished Exit the Session.
Sep 17 08:33:45 home systemd[7094]: Reached target Exit the Session.
Sep 17 08:33:45 home systemd[1]: user@104.service: Succeeded.
Sep 17 08:33:45 home systemd[1]: Stopped User Manager for UID 104.
Sep 17 08:33:45 home systemd[1]: Stopping User Runtime Directory /run/user/104...
Sep 17 08:33:45 home systemd[1]: run-user-104.mount: Succeeded.
Sep 17 08:33:45 home systemd[1325]: run-user-104.mount: Succeeded.
Sep 17 08:33:45 home systemd[1]: user-runtime-dir@104.service: Succeeded.
Sep 17 08:33:45 home systemd[1]: Stopped User Runtime Directory /run/user/104.
Sep 17 08:33:45 home systemd[1]: Removed slice User Slice of UID 104.
Sep 17 08:34:12 home systemd[1]: systemd-suspend.service: Succeeded.
Sep 17 08:34:12 home systemd[1]: Finished Suspend.
Sep 17 08:34:12 home systemd[1]: Stopped target Sleep.
Sep 17 08:34:12 home systemd[1]: Reached target Suspend.
Sep 17 08:34:12 home systemd[1]: Stopped target Suspend.
Sep 17 08:34:14 home systemd[1]: Created slice User Slice of UID 104.
Sep 17 08:34:14 home systemd[1]: Starting User Runtime Directory /run/user/104...
Sep 17 08:34:14 home systemd[1]: Finished User Runtime Directory /run/user/104.
Sep 17 08:34:14 home systemd[1]: Starting User Manager for UID 104...
Sep 17 08:34:14 home systemd[9648]: Reached target Paths.
Sep 17 08:34:14 home systemd[9648]: Reached target Timers.
Sep 17 08:34:14 home systemd[9648]: Starting D-Bus User Message Bus Socket.
Sep 17 08:34:14 home systemd[9648]: Listening on GnuPG network certificate management daemon.
Sep 17 08:34:14 home systemd[9648]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 17 08:34:14 home systemd[9648]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 17 08:34:14 home systemd[9648]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 17 08:34:14 home systemd[9648]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 17 08:34:14 home systemd[9648]: Listening on debconf communication socket.
Sep 17 08:34:14 home systemd[9648]: Listening on Sound System.
Sep 17 08:34:14 home systemd[9648]: Listening on D-Bus User Message Bus Socket.
Sep 17 08:34:14 home systemd[9648]: Reached target Sockets.
Sep 17 08:34:14 home systemd[9648]: Reached target Basic System.
Sep 17 08:34:14 home systemd[1]: Started User Manager for UID 104.
Sep 17 08:34:14 home systemd[9648]: Starting Sound Service...
Sep 17 08:34:14 home systemd[1]: Started Session c10 of user lightdm.

Что вообще происходит?

08:34:12 home systemd[1]: systemd-suspend.service: Succeeded

Это же по-идее переход в спящий, но какого этот таргет исполняется после выхода из спящего? И да, системд - зло.

★★★★★

но какого этот таргет исполняется после выхода

Это логирование события suspend исполняется после resume.

Много говорит о систем-мде.

LamerOk ★★★★★
()
Ответ на: комментарий от LamerOk

Охрененно. Вот как теперь такие отложеные логи анализировать, таймстампы-то у них текущие? Чем там потный Лёня думал?

eagleivg ★★★★★
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.