package procps 1:3.2.8-9ubuntu1 failed to install/upgrade: start: Job failed to start

[Dr. Tyrell]

Binary package hint: procps

Maverick

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: procps 1:3.2.8-9ubuntu1
Uname: Linux 2.6.34-rc7 x86_64
Architecture: amd64
Date: Wed Jun 9 00:43:36 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100128)
SourcePackage: procps
Title: package procps 1:3.2.8-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[zika (4zika4)]

[code]:~$ cat error.txt
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 procps
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up procps (1:3.2.8-9ubuntu1) ...
start: Job failed to start
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 procps
...
The following partially installed packages will be configured:
  procps
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up procps (1:3.2.8-9ubuntu1) ...
start: Job failed to start
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 procps
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up procps (1:3.2.8-9ubuntu1) ...
start: Job failed to start
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 procps[/code]

[zika (4zika4)]

In /etc/sysctl.d/10-ptrace.conf there was a line: kernel.ptrace_scope = 1 that caused the trouble. After I commented it. all is OK.

[Philip Muškovac (yofel)]

Thank you for reporting this bug. Please upgrade your kernel.
/proc/sys/kernel/ptrace_scope
was added recently. Here the upgrade failed with 34-2 but worked fine with 35-1.

[Erik B. Andersen (azendale)]

I'm able to reliably reproduce this bug on a VM that I'm upgrading from Lucid to Maverick. I say reliably because I've run the upgrade in sandbox mode, and it happens every time. It prevents the upgrade from working. Users shouldn't have to edit text files to make their upgrade work.

[Erik B. Andersen (azendale)]

I just found bug #632584 and a duplicate of it, bug #628824. Apparently, I'm not the only one having problems on the Lucid to Maverick upgrade, the bug #628824 says that it happened while the person was upgrading from Lucid to Maverick.