Всем привет. Использую Arch. Достало окно xscreensaver, которое появляется каждые 40 секунд на заблокированном экране. Вот лог самого xscreensaver:
xscreensaver 5.35, copyright (c) 1991-2016 by Jamie Zawinski <jwz@jwz.org>.
10:48:18: running as xenohunter/users (1000/100)
10:48:18: in process 11626.
10:48:18: running on display ":0.0"
10:48:18: vendor is The X.Org Foundation, 11804000.
10:48:18: useful extensions:
10:48:18: MIT Screen-Saver (disabled at compile time)
10:48:18: Shared Memory (1.2)
10:48:18: Double-Buffering (1.0)
10:48:18: Power Management (1.1)
10:48:18: GLX
10:48:18: XF86 Video-Mode (2.2)
10:48:18: XC Misc (disabled at compile time)
10:48:18: Xinerama (1.1)
10:48:18: Resize-and-Rotate (1.5)
10:48:18: XInput
10:48:18: screen 0 non-colormapped depths: 24.
10:48:18: WARNING: RANDR and Xinerama report different
10:48:18: screen layouts! Believing RANDR.
10:48:18: screens in use: 1
10:48:18: 0/0: 1920x1080+0+0 (eDP1)
10:48:18: rejected screens: 3
10:48:18: 1/0: 1920x1080+0+0 (HDMI1) -- output disabled
10:48:18: 2/0: 1920x1080+0+0 (VGA1) -- output disabled
10:48:18: 3/0: 0x0+0+0 (VIRTUAL1) -- output disabled
10:48:18: selecting RANDR events
10:48:18: not using XInputExtension.
10:48:18: consulting /proc/interrupts for keyboard activity.
10:48:18: 0: visual 0x20 (TrueColor, depth: 24, cmap: default)
10:48:18: 0: saver window is 0x1400001.
10:48:18: selecting events on extant windows... done.
10:48:18: awaiting idleness.
10:48:27: ClientMessage DEACTIVATE received while inactive: resetting idle timer.
10:48:29: LOCK ClientMessage received; activating and locking.
10:48:29: 0: locked mode switching.
10:48:29: user is idle (ClientMessage)
10:48:29: blanking screen at Sat Oct 8 10:48:29 2016.
10:48:29: 0: grabbing keyboard on 0xd4... AlreadyGrabbed.
10:48:30: 0: grabbing keyboard on 0xd4... GrabSuccess.
10:48:30: 0: grabbing mouse on 0xd4... GrabSuccess.
10:48:47: DEACTIVATE ClientMessage received.
10:48:47: user is active (ClientMessage)
10:48:47: pam_start ("xscreensaver", "xenohunter", ...) ==> 0 (Success)
10:48:47: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
10:48:47: pam_authenticate (...) ...
10:48:47: pam_conversation (ECHO_OFF="Password: ") ...
10:48:47: 0: mouse is at 1047,514.
10:48:47: 0: creating password dialog ("")
10:48:47: grabbing server...
10:48:47: 0: ungrabbing mouse (was 0xd4).
10:48:47: 0: grabbing mouse on 0x140003c... GrabSuccess.
10:48:47: ungrabbing server.
10:49:17: input timed out.
10:49:17: pam_conversation (...) ==> PAM_CONV_ERR
10:49:17: pam_authenticate (...) ==> 20 (Authentication token manipulation error)
10:49:17: pam_end (...) ==> 0 (Success)
10:49:17: authentication via PAM timed out.
10:49:17: grabbing server...
10:49:17: 0: ungrabbing mouse (was 0x140003c).
10:49:17: 0: grabbing mouse on 0xd4... GrabSuccess.
10:49:17: ungrabbing server.
10:49:17: 0: moving mouse back to 1047,514.
10:49:17: discarding MotionNotify event.
10:49:17: 0: destroying password dialog.
Также проверял вот этим — evtest /dev/input/event0 > /root/log.0
— потоки событий мыши, клавиатуры и тачпада. Везде пусто.
Единственное, что удалось найти — это записи в journalctl
следующего вида, всегда с промежутком ровно в 40 секунд:
Oct 08 14:02:57 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): conversation failed
Oct 08 14:02:57 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): auth could not identify password for [xenohunter]
Oct 08 14:03:37 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): conversation failed
Oct 08 14:03:37 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): auth could not identify password for [xenohunter]
Oct 08 14:04:17 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): conversation failed
Oct 08 14:04:17 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): auth could not identify password for [xenohunter]
Oct 08 14:04:57 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): conversation failed
Oct 08 14:04:57 regulus xscreensaver[12913]: pam_unix(xscreensaver:auth): auth could not identify password for [xenohunter]
До сентября такого не было, так что, возможно дело в обновлениях, но я не знаю, куда копать.
Задавал вопрос на Unix & Linux SE, пока решение найти не удалось.