A few days ago we got suddenly affected by this after auto "upgrade apport 2.0.1-0ubuntu17.9 2.0.1-0ubuntu17.10".
We never had any need to change 'kernel.core_pattern' parameter in the past.
Sometimes, our coredumps are several GB large; so i expect apport to fail handling them anyway.
Then one would need the extra resources to now extract the coredump from a crash report.
The worst part is that after removing the package, the new 'kernel.core_pattern=core', which is plain wrong.
Now, we do have to worry about re-setting that back to the standard '/var/tmp/core.%e.%u.%g.%p.%s.%t'.
A few days ago we got suddenly affected by this after auto "upgrade apport 2.0.1-0ubuntu17.9 2.0.1-0ubuntu17 .10". core_pattern' parameter in the past. core_pattern= core', which is plain wrong.
We never had any need to change 'kernel.
Sometimes, our coredumps are several GB large; so i expect apport to fail handling them anyway.
Then one would need the extra resources to now extract the coredump from a crash report.
The worst part is that after removing the package, the new 'kernel.
Now, we do have to worry about re-setting that back to the standard '/var/tmp/ core.%e. %u.%g.% p.%s.%t' .