Done, although the test plan is still a little vague requiring you to wait some time _after_ the update is released to verify. An alternate test plan would involve intentionally crashing something on the local machine.
And sorry for the delay, I was on vacation. ** Description changed: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] + 1. Find a recent crash report from a relevant Ubuntu release on + https://errors.ubuntu.com/ If you're looking at + https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a + relevant instance from the Occurrences list. + + 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ + look at the Date and JournalErrors fields. + + 3. Verify that Date falls within the time range of the JournalErrors + entries. + [Where problems could occur] - Worst case - In any part of the bug reporting/collection procedure, + Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] ** No longer affects: errors ** Description changed: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ - look at the Date and JournalErrors fields. + look at Dependencies and verify that apport is a recent enough version + to contain the proposed fix. - 3. Verify that Date falls within the time range of the JournalErrors - entries. + 3. Expand the JournalErrors field and verify the Date field above it + falls within the time range of the JournalErrors entries. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Incomplete Bug description: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ look at Dependencies and verify that apport is a recent enough version to contain the proposed fix. 3. Expand the JournalErrors field and verify the Date field above it falls within the time range of the JournalErrors entries. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
