Activity log for bug #1800562

Date Who What changed Old value New value Message
2018-10-29 22:29:30 Guilherme G. Piccoli bug added bug
2018-10-29 22:30:07 Guilherme G. Piccoli affects linux (Ubuntu) makedumpfile (Ubuntu)
2018-10-29 22:30:31 Guilherme G. Piccoli nominated for series Ubuntu Xenial
2018-10-29 22:30:31 Guilherme G. Piccoli nominated for series Ubuntu Dd-series
2018-10-29 22:30:31 Guilherme G. Piccoli nominated for series Ubuntu Bionic
2018-10-29 22:30:31 Guilherme G. Piccoli nominated for series Ubuntu Cosmic
2018-10-29 23:18:41 Guilherme G. Piccoli bug added subscriber Thadeu Lima de Souza Cascardo
2019-01-09 15:42:14 Eric Desrochers bug task added makedumpfile (Ubuntu Bionic)
2019-01-09 15:42:20 Eric Desrochers bug task added makedumpfile (Ubuntu Cosmic)
2019-01-09 15:42:25 Eric Desrochers bug task added makedumpfile (Ubuntu Disco)
2019-01-09 15:42:30 Eric Desrochers bug task added makedumpfile (Ubuntu Xenial)
2019-01-09 15:56:55 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): status New Confirmed
2019-01-09 15:56:57 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): status New Confirmed
2019-01-09 15:56:58 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): status New Confirmed
2019-01-09 15:57:01 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): importance Undecided High
2019-01-09 15:57:03 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): importance Undecided High
2019-01-09 15:57:05 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): importance Undecided High
2019-01-09 15:57:07 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): assignee Guilherme G. Piccoli (gpiccoli)
2019-01-09 15:57:09 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): assignee Guilherme G. Piccoli (gpiccoli)
2019-01-09 15:57:10 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): assignee Guilherme G. Piccoli (gpiccoli)
2019-02-14 11:43:25 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): assignee Guilherme G. Piccoli (gpiccoli) Heitor R. Alves de Siqueira (halves)
2019-02-14 11:43:38 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): assignee Guilherme G. Piccoli (gpiccoli) Heitor R. Alves de Siqueira (halves)
2019-02-14 11:43:50 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): assignee Guilherme G. Piccoli (gpiccoli) Heitor R. Alves de Siqueira (halves)
2019-02-14 11:43:59 Guilherme G. Piccoli makedumpfile (Ubuntu Disco): assignee Guilherme G. Piccoli (gpiccoli) Heitor R. Alves de Siqueira (halves)
2019-02-14 16:45:05 Heitor Alves de Siqueira description Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test [...] kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios.
2019-02-14 16:45:27 Heitor Alves de Siqueira description [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test [...] kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios. [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test [...] kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios. [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.rst
2019-02-19 09:01:46 Eric Desrochers bug added subscriber STS Sponsors
2019-02-19 09:23:07 Heitor Alves de Siqueira attachment added debdiff for disco https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
2019-02-19 09:23:44 Heitor Alves de Siqueira attachment added debdiff for cosmic https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
2019-02-19 09:24:05 Heitor Alves de Siqueira attachment added debdiff for bionic https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
2019-02-19 09:24:25 Heitor Alves de Siqueira attachment added debdiff for xenial https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
2019-02-19 09:33:24 Heitor Alves de Siqueira description [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test [...] kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios. [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.rst [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test ... kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios. [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.rst
2019-02-19 12:24:01 Ubuntu Foundations Team Bug Bot tags sts patch sts
2019-02-19 12:24:10 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2019-02-19 14:54:32 Eric Desrochers makedumpfile (Ubuntu Disco): status Confirmed In Progress
2019-02-19 14:54:34 Eric Desrochers makedumpfile (Ubuntu Cosmic): status Confirmed In Progress
2019-02-19 14:54:36 Eric Desrochers makedumpfile (Ubuntu Bionic): status Confirmed In Progress
2019-02-19 14:54:39 Eric Desrochers makedumpfile (Ubuntu Xenial): status Confirmed In Progress
2019-02-20 09:05:19 Thadeu Lima de Souza Cascardo makedumpfile (Ubuntu Disco): status In Progress Opinion
2019-02-25 18:05:05 Heitor Alves de Siqueira attachment removed debdiff for disco https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
2019-02-25 18:05:19 Heitor Alves de Siqueira attachment removed debdiff for cosmic https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
2019-02-25 18:05:31 Heitor Alves de Siqueira attachment removed debdiff for bionic https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
2019-02-25 18:05:39 Heitor Alves de Siqueira attachment removed debdiff for xenial https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
2019-02-25 18:06:42 Heitor Alves de Siqueira summary Replace "nousb" option in kdump command-line for the newer "usbcore.nousb" Remove obsolete "nousb" option in kdump command-line for newer kernels
2019-02-25 18:11:46 Heitor Alves de Siqueira description [Impact] Crash kernels come up with the usb subsystem enabled, even when it should be disabled by default. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter: $ kdump-config test ... kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile and we're only adding a parameter on the crashkernel cmdline. According to kernel documentation [0], unknown parameters will be ignored if they contain a dot (usbcore.nousb), so this change should have no impact on v4.4 and earlier kernels. Nonetheless, the fix will be tested with autopkgtests and normal kdump use-case scenarios. [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.rst [Impact] Crash kernels include an obsolete "nousb" parameter by default, which can cause confusion since it's been deprecated in newer kernel versions. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line appears to be saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'nousb' parameter: $ kdump-config test ... kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is extremely low, since it doesn't need any changes in makedumpfile code and we're only removing an already ineffective parameter from the crashkernel cmdline. Nonetheless, patches will be tested with autopkgtests and normal kdump use-case scenarios.
2019-03-01 02:47:10 Eric Desrochers removed subscriber STS Sponsors
2019-03-01 02:47:13 Eric Desrochers bug added subscriber Eric Desrochers
2019-04-20 20:09:10 Simon Quigley removed subscriber Ubuntu Sponsors Team
2019-06-05 14:19:54 Heitor Alves de Siqueira tags patch sts
2019-06-19 12:19:06 Guilherme G. Piccoli tags seg
2019-07-04 14:15:20 Guilherme G. Piccoli nominated for series Ubuntu Eoan
2019-07-04 14:15:20 Guilherme G. Piccoli bug task added makedumpfile (Ubuntu Eoan)
2019-07-04 14:15:28 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): status In Progress Won't Fix
2019-07-04 14:15:34 Guilherme G. Piccoli makedumpfile (Ubuntu Disco): status Opinion Confirmed
2019-07-04 14:15:36 Guilherme G. Piccoli makedumpfile (Ubuntu Eoan): status Opinion Confirmed
2019-07-04 14:15:40 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): assignee Heitor Alves de Siqueira (halves) Guilherme G. Piccoli (gpiccoli)
2019-07-04 14:15:41 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): assignee Heitor Alves de Siqueira (halves) Guilherme G. Piccoli (gpiccoli)
2019-07-04 14:15:43 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): assignee Heitor Alves de Siqueira (halves) Guilherme G. Piccoli (gpiccoli)
2019-07-04 14:15:45 Guilherme G. Piccoli makedumpfile (Ubuntu Disco): assignee Heitor Alves de Siqueira (halves) Guilherme G. Piccoli (gpiccoli)
2019-07-04 14:15:47 Guilherme G. Piccoli makedumpfile (Ubuntu Eoan): assignee Heitor Alves de Siqueira (halves) Guilherme G. Piccoli (gpiccoli)
2019-07-04 19:40:45 Guilherme G. Piccoli description [Impact] Crash kernels include an obsolete "nousb" parameter by default, which can cause confusion since it's been deprecated in newer kernel versions. [Description] Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). We need to take this into account in kdump-tools, or else we may boot with USB in kdump even the command-line appears to be saying the opposite. This affects Xenial onwards, since the system may be running an HWE or other supported v4.5+ kernel. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'nousb' parameter: $ kdump-config test ... kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is extremely low, since it doesn't need any changes in makedumpfile code and we're only removing an already ineffective parameter from the crashkernel cmdline. Nonetheless, patches will be tested with autopkgtests and normal kdump use-case scenarios. [Impact] * Kdump command-line include an obsolete "nousb" parameter by default, which can cause a misimpression: users will think they are not booting with USB, but they are. * Since kernel v4.5, the correct parameter to disable USB subsystem initialization is "usbcore.nousb" always (instead of "nousb" in case the subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make "nousb" a clear module parameter"). * USB may be pretty essential in case for example kdump users need to decrypt a disk under LUKS, and there's only an USB keyboard connected to the system. Given the option is innocuous since Bionic, we should just drop it to prevent confusion. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'nousb' parameter: $ kdump-config test ... kexec command to be used:   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is extremely low, since the "nousb" parameter is not used since Bionic although is there. Any bugs we would have by changing this are still valid by not removing the option - the semantics with or without "nosub" is the same since from Bionic. NOTICE we won't change Xenial, it can use kernel 4.4 which indeed disables USB by taking the "nousb" parameter.
2019-07-04 21:28:33 Guilherme G. Piccoli makedumpfile (Ubuntu Cosmic): status In Progress Confirmed
2019-07-04 21:28:35 Guilherme G. Piccoli makedumpfile (Ubuntu Eoan): status Confirmed In Progress
2019-07-04 21:28:36 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): status In Progress Confirmed
2019-07-04 21:30:02 Guilherme G. Piccoli attachment added lp1800562_eoan.debdiff https://bugs.launchpad.net/ubuntu/bionic/+source/makedumpfile/+bug/1800562/+attachment/5275119/+files/lp1800562_eoan.debdiff
2019-10-19 03:12:59 Mathew Hodson makedumpfile (Ubuntu Cosmic): status Confirmed Won't Fix
2019-10-19 03:14:14 Mathew Hodson tags seg patch seg
2020-07-02 19:27:23 Steve Langasek makedumpfile (Ubuntu Disco): status Confirmed Won't Fix
2020-07-14 15:20:06 Guilherme G. Piccoli bug task deleted makedumpfile (Ubuntu Cosmic)
2020-07-14 15:20:11 Guilherme G. Piccoli bug task deleted makedumpfile (Ubuntu Disco)
2020-07-14 15:20:22 Guilherme G. Piccoli nominated for series Ubuntu Focal
2020-07-14 15:20:22 Guilherme G. Piccoli bug task added makedumpfile (Ubuntu Focal)
2020-07-14 15:20:22 Guilherme G. Piccoli nominated for series Ubuntu Groovy
2020-07-14 15:20:22 Guilherme G. Piccoli bug task added makedumpfile (Ubuntu Groovy)
2020-07-14 15:20:31 Guilherme G. Piccoli makedumpfile (Ubuntu Focal): status New Confirmed
2020-07-14 15:20:34 Guilherme G. Piccoli makedumpfile (Ubuntu Eoan): status In Progress Confirmed
2020-07-14 15:20:37 Guilherme G. Piccoli makedumpfile (Ubuntu Groovy): status In Progress Confirmed
2020-07-14 15:20:41 Guilherme G. Piccoli makedumpfile (Ubuntu Focal): importance Undecided Medium
2020-07-14 15:20:43 Guilherme G. Piccoli makedumpfile (Ubuntu Groovy): importance High Medium
2020-07-14 15:20:46 Guilherme G. Piccoli makedumpfile (Ubuntu Eoan): importance High Medium
2020-07-14 15:20:48 Guilherme G. Piccoli makedumpfile (Ubuntu Bionic): importance High Medium
2020-07-14 15:20:52 Guilherme G. Piccoli makedumpfile (Ubuntu Xenial): importance High Medium
2020-07-14 15:20:54 Guilherme G. Piccoli makedumpfile (Ubuntu Focal): assignee Guilherme G. Piccoli (gpiccoli)
2020-08-18 16:57:17 Brian Murray makedumpfile (Ubuntu Eoan): status Confirmed Won't Fix
2021-07-28 23:12:02 Brian Murray makedumpfile (Ubuntu Groovy): status Confirmed Won't Fix
2023-09-28 20:04:52 dann frazier bug task added kdump-tools (Ubuntu)
2023-09-28 20:05:26 dann frazier bug task deleted kdump-tools (Ubuntu)
2023-09-28 20:18:23 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors
2023-10-04 12:15:52 Graham Inggs tags patch seg seg
2023-10-04 12:15:59 Graham Inggs removed subscriber Ubuntu Sponsors