/etc/mtab is a normal file (should be a symlink to /proc/mounts)

[Removed by request]

I'm using Ubuntu 15.10 dev with mount 2.26.2-6ubuntu3 and I'm noticing that after booting my system /etc/mtab is only containing an ecryptfs entry for my home folder but nothing else.

[Martin Pitt (pitti)]

/etc/mtab should/must be a symlink to /proc/mounts; is that not the case for you? Please show the output of

  ls -l /etc/mtab

[Removed by request (removed3425744)]

/etc/mtab is a normal file that doesn't point to /proc/mounts and got changed the last time today. But this installation is an older one so maybe this is an upgrading issue? Or maybe something ecryptfs-related has overwritten the symlink to add its own entry?

[Martin Pitt (pitti)]

We indeed did have cases where badly written postinst scripts broke the /etc/mtab symlink, e. g. bug 1419623. debian-fixup.service is supposed to convert it to a symlink at boot -- is it still a symlink after a fresh boot? Can you please show

  sudo systemctl status -l debian-fixup

?

[Removed by request (removed3425744)]

Yes, it was still a file after the last reboot. Here is the output of the command:

root@ubuntu:~# systemctl status -l debian-fixup
Failed to get D-Bus connection: Operation not permitted

I have restricted D-Bus on my system with /etc/dbus-1/session-local.conf and /etc/dbus-1/system-local.conf. I'm wondering now if this does prevent systemd jobs to start at all (but currently I'm still on upstart).

[Martin Pitt (pitti)]

Oh -- well, then debian-fixup.service can't possibly run :-)

[Removed by request (removed3425744)]

I have now temporary removed the D-Bus restrictions but I'm getting still the same error after rebooting my system and executing the command again.

[Removed by request (removed3425744)]

From the information I found this might be because I'm still on upstart. It also looks that this job isn't available for upstart. Since upstart is still in the official repositories maybe core-jobs should also be created for upstart.