-- Logs begin at Sat 2018-03-10 14:01:50 MSK, end at Sun 2018-03-11 12:17:31 MSK. --
Mar 11 12:06:06 hostname systemd[1]: Failed to start vboxadd-service.service.
Mar 11 12:06:07 hostname lightdm[880]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 11 12:06:07 hostname lightdm[880]: PAM adding faulty module: pam_kwallet.so
Mar 11 12:06:07 hostname lightdm[880]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 11 12:06:07 hostname lightdm[880]: PAM adding faulty module: pam_kwallet5.so
Mar 11 12:06:08 hostname lightdm[952]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 11 12:06:08 hostname lightdm[952]: PAM adding faulty module: pam_kwallet.so
Mar 11 12:06:08 hostname lightdm[952]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 11 12:06:08 hostname lightdm[952]: PAM adding faulty module: pam_kwallet5.so
Mar 11 12:06:14 hostname spice-vdagent[1596]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Mar 11 12:06:22 hostname pulseaudio[1455]: [alsa-sink-Intel ICH] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Mar 11 12:06:22 hostname pulseaudio[1455]: [alsa-sink-Intel ICH] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_intel8x0'. Please report this issue to the ALSA developers.
Mar 11 12:06:22 hostname pulseaudio[1455]: [alsa-sink-Intel ICH] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Mar 11 12:06:40 hostname pulseaudio[1455]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.