© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This bug was not fixed. Wine still gives an error (both 1.0.x and 1.1.x versions).
The real bug is not with procps or the wine package, but with sysctl. The error message occurs when there's keys in the sysctl config files that dont exist.
I'm not sure if my sysctl.conf is a modified version, old version or stock version, but for reference, it contained the following keys that systcl didnt like:
kernel.maps_protect = 1
sys.kernel.
net.ipv4.
I commented these out and a "service procps start" now does not give an error anymore, and wine installs without any error.
The only proper fix for this is to interpret sysctl exit statuses better in /etc/init/procps. I don't know what exactly the status code is, or supposed to be, but it's probably different for real errors than for unknown keys.