This is probably not assigned to the right package. It's not an issue with e2fsprogs, but whatever component is running fsck. This might be systemd, or upstart, or whatever the heck Ubuntu is using these days. I lost track a while ago. :-)
I can tell, you as the Debian maintainer of e2fsprogs, that fsck runs *just* *fine* on Debian testing. With Debian, using systemd (which is the default), the systemd units which run fsck are generated by the systemd-fstab-generator program which is part of systemd. So the main issue is whether anyone on the Canonical/Ubuntu team is paying attention. I pay attention in case people report e2fsprogs bugs, but this is not an e2fsprogs issue. And I don't use Ubuntu so I can't really help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797282 Title: fsck not running at all on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1797282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
