OK, I spoke to soon. Aparantly I grep'd for: user_max
instead of max_user, which DOES match: /etc/sysctl.d/30-spideroak.conf I commented out the one line in this file (i.e. add a leading hash mark '#'), and now procps starts. So, IF YOU USE SPIDEROAK, THIS MIGHT BE THE PROBLEM. Hope this is helpful to others. --Doug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
