-- Logs begin at Thu 2018-01-04 11:09:49 AST, end at Sun 2018-03-25 15:17:13 AST. --
mrt 25 15:12:50 hostname kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
mrt 25 15:13:20 hostname gnome-session-binary[1172]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
mrt 25 15:13:34 hostname spice-vdagent[1705]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mrt 25 15:13:55 hostname pulseaudio[2207]: [alsa-sink-STAC9221 A1 Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
mrt 25 15:13:55 hostname pulseaudio[2207]: [alsa-sink-STAC9221 A1 Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
mrt 25 15:13:55 hostname pulseaudio[2207]: [alsa-sink-STAC9221 A1 Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
mrt 25 15:13:58 hostname spice-vdagent[2574]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mrt 25 15:14:20 hostname pulseaudio[2207]: [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.