-- Logs begin at Sat 2018-03-10 11:43:16 EST, end at Sat 2018-03-10 12:11:10 EST. --
Mar 10 11:56:03 username-VirtualBox lightdm[944]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 10 11:56:03 username-VirtualBox lightdm[944]: PAM adding faulty module: pam_kwallet.so
Mar 10 11:56:03 username-VirtualBox lightdm[944]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 10 11:56:03 username-VirtualBox lightdm[944]: PAM adding faulty module: pam_kwallet5.so
Mar 10 11:56:04 username-VirtualBox lightdm[1018]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 10 11:56:04 username-VirtualBox lightdm[1018]: PAM adding faulty module: pam_kwallet.so
Mar 10 11:56:04 username-VirtualBox lightdm[1018]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 10 11:56:04 username-VirtualBox lightdm[1018]: PAM adding faulty module: pam_kwallet5.so
Mar 10 11:57:29 username-VirtualBox spice-vdagent[1564]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Mar 10 11:57:30 username-VirtualBox pulseaudio[1488]: [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 10 11:57:30 username-VirtualBox pulseaudio[1488]: [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 10 11:57:30 username-VirtualBox pulseaudio[1488]: [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 10 11:57:54 username-VirtualBox pulseaudio[1488]: [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.
Mar 10 12:07:39 username-VirtualBox trashapplet[3026]: The program 'trashapplet' received an X Window System error.
                                                   This probably reflects a bug in the program.
                                                   The error was 'RenderBadPicture (invalid Picture parameter)'.
                                                     (Details: serial 699 error_code 143 request_code 139 (RENDER) minor_code 7)
                                                     (Note to programmers: normally, X errors are reported asynchronously;
                                                      that is, you will receive the error a while after causing it.
                                                      To debug your program, run it with the GDK_SYNCHRONIZE environment
                                                      variable to change this behavior. You can then get a meaningful
                                                      backtrace from your debugger if you break on the gdk_x_error() function.)