This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1
---------------
makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low
[ Ubuntu Merge-o-Matic ]
* Merge from Debian unstable. Remaining changes:
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
[ Thadeu Lima de Souza Cascardo ]
* Use a different service for vmcore dump. (LP: #1811692)
makedumpfile (1:1.6.5-1) unstable; urgency=medium
* Update to new upstream version 1.6.5.
* debian: remove debian/source/local-options
* [i18n] Move PT debconf translation (Closes: #910465)
makedumpfile (1:1.6.4-3) unstable; urgency=medium
* Reload kdump after memory/CPU hotplug. (LP: #1655280)
* Fix adding crashkernel to zipl.conf when no quotation mark is used.
(LP: #1790788)
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Mon, 14 Jan
2019 15:42:44 -0200
** Changed in: makedumpfile (Ubuntu)
Status: In Progress => 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/1790788
Title:
Customize 'crashkernel' parameter is not properly working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
