This bug was fixed in the package procps - 2:3.3.10-4ubuntu2.2
---
procps (2:3.3.10-4ubuntu2.2) xenial; urgency=medium
* Don't start procps on install. This avoids errors on upgrade
within a container. Backported from yakkety. (LP: #1637300)
procps (2:3.3.10-4ubuntu2.1)
root@vps137255:~# apt-get install procps/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '2:3.3.10-4ubuntu2.2' (Ubuntu:16.04/xenial-proposed [amd64])
for 'procps'
The following packages were automatically installed and are
root@procpstest:~# apt install procps -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
procps
1 upgraded, 0 newly installed, 0 to remove and 46 not upgraded.
Need to get 208 kB of archives.
After this
Hello dann, or anyone else affected,
Accepted procps into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.10-4ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This seems fine to me. I just replied to
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026/comments/4
before realizing that this issue is tracked here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: procps (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637300
Title:
procps upgrades fail in a LXD container
To manage notifications
** Bug watch added: Debian Bug tracker #827423
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827423
** Also affects: procps (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827423
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Note that, though procps itself is patched to ignore errors when writing
to /proc/sys, the problem here is that the initscript causes the
systemd-sysctl service to get triggered, and that does not fail
gracefully:
ubuntu@procps:~$ sudo /lib/systemd/systemd-sysctl
Couldn't write '1' to
** Patch added: "proposed debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637300/+attachment/4768378/+files/procps-no-init-on-upgrade.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
