Weird mount dependency errors delaying boot up

[oshunluvr]

Went away on it's own. I also this this which I solved:

[DEPEND] Dependency failed for sssd-nss.soc… SSSD NSS Service responder socket.
[DEPEND] Dependency failed for sssd-autofs.…SD AutoFS Service responder socket.
[DEPEND] Dependency failed for sssd-pac.soc… SSSD PAC Service responder socket.
[DEPEND] Dependency failed for sssd-pam-pri…M Service responder private socket.
[DEPEND] Dependency failed for sssd-pam.soc… SSSD PAM Service responder socket.
[DEPEND] Dependency failed for sssd-ssh.soc… SSSD SSH Service responder socket.
[DEPEND] Dependency failed for sssd-sudo.so…SSSD Sudo Service responder socket.

If you see this in your boot log, it's caused by a config file that's not in the right place. I solved it with:

sudo cp /usr/lib/x86_64-linux-gnu/sssd/conf/sssd.conf /etc/sssd/.
sudo cp /usr/lib/x86_64-linux-gnu/sssd/conf/sssd.conf /etc/sssd/conf.d/.

I'm not sure which copy resulted in the solution, but the errors are gone now.

In my searching, I also discovered a known problem with Breeze splash and KDEneon that causes a 20-30 second delay between logging in and the desktop appearing - something I have been suffering through for quite awhile. Simply turning off the splash screen in system settings makes my desktop launch 10x faster.

[oshunluvr]

By accident when fixing some other problem, I discovered this issue. From boot.log:

Gave up waiting for suspend/resume device
[ TIME ] Timed out waiting for device dev-d….device - /dev/disk/by-label/Steam.
[DEPEND] Dependency failed for mnt-steam.mount - /mnt/steam.
[DEPEND] Dependency failed for local-fs.target - Local File Systems.
[ TIME ] Timed out waiting for device dev-d…vice - /dev/disk/by-label/vm_drive.
[DEPEND] Dependency failed for mnt-vm_drive.mount - /mnt/vm_drive.
[ TIME ] Timed out waiting for device dev-d…e06117-4c44-450c-b3e5-ceefa4de0d86.
[DEPEND] Dependency failed for dev-disk-by\…e06117-4c44-450c-b3e5-ceefa4de0d86.
[DEPEND] Dependency failed for swap.target - Swaps.

I have been unable to find an applicable fix on the 'net. As far as I can tell, fstab is fine and when boot up is complete, the mounts in question are, in fact, mounted.