Same surprise here, after adding a custom
'/etc/sysctl.d/60-core_pattern.conf' to set it to my desired value, I
could not understand why it seemed not applied after a reboot. Finally
discovered the echoing inside '/etc/init/apport.conf' and died a little
internally.
The proper course of action
This is quite frustrating. I wish it would be addressed... somehow...
(still getting this problem on 18.04 LTS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080978
Title:
apport forcefully
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
Just got burned by this as well after upgrading to 12.04 in our
infrastructure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080978
Title:
apport forcefully overrides sysctl kernel.core_pattern
I have also just run into this after I tried to set a core pattern. I
am rather divided on this - I would like to get my core patterns, but I
also appreciate having Apport's functionality. So I would like a way to
set the pattern for cores not handled by Apport. Perhaps a new sysctl
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080978
Title:
