Hi Michael, hi Sven! Yes, you are right, I have indeed errors.
systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● speech-dispatcher.service loaded failed failed LSB: Speech Dispatcher ● systemd-modules-load.service loaded failed failed Load Kernel Modules ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems But this pushes me into another problem. Speechdispatcher is working. And the other thing might be a misconfiguration in /etc/fstab. However, everything is working well, as far as I see. Maybe it is, because I am using encrypted filesystems? Or because of using a SSD-drive? This is a extraction of my fstab: UUID=hidden_by_me_in_this_mail /boot ext2 defaults 0 1 /dev/mapper/home /home ext4 noatime,defaults,errors=remount- ro,discard 0 2 / Do you see any misconfigurations? Thanks for taking a look at. Hans > Sven is right, this is most likely due to the new behaviour of systemd, > to automatically switch into verbose mode, if a unit failed or hit a > timeout. You can change this behaviour by setting the > systemd.show_status parameter. The default is "auto". If you want to > suppress the messages, you can set that to "false". > > That said, it's probably better to find the failing service (with the > command Sven gave you) and fix the root of the problem. > > > > > [1] > http://www.freedesktop.org/software/systemd/man/systemd.html#systemd.show_st > atus=
signature.asc
Description: This is a digitally signed message part.