(Set it to medium as the thoery is that it's only happening with older, staggering, crashes)
** Branch linked: lp:~didrocks/apport/handle-older-reports ** Description changed: + [Impact] + + * The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee + * The theory is that those crashes are trigger by reports generated (but not send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, and thus, the new apport, when reporting, is crashing. + * We now ignore if the key isn't present and just consider the answer as "false", which is a no-op. + + [Test Case] + + * Install apport 2.20.9-0ubuntu7.1 + * Generate a crash but don't report it. + * Upgrade to apport apport 2.20.9-0ubuntu7.3 + * Report this crash. + -> No apport crash should be triggered + + [Regression Potential] + * We are doing a python2 compatible try/except to ignore the KeyError which was the regression. It doesn't seem it can trigger other regressions. + + ------- + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Description changed: [Impact] - - * The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee - * The theory is that those crashes are trigger by reports generated (but not send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, and thus, the new apport, when reporting, is crashing. - * We now ignore if the key isn't present and just consider the answer as "false", which is a no-op. + * The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee + * The theory is that those crashes are trigger by reports generated (but not send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, and thus, the new apport, when reporting, is crashing. + * We now ignore if the key isn't present and just consider the answer as "false", which is a no-op. [Test Case] + * Install apport 2.20.9-0ubuntu7.1 + * Generate a crash but don't report it. + * Upgrade to apport apport 2.20.9-0ubuntu7.3 + * Report this crash. + -> No apport crash should be triggered - * Install apport 2.20.9-0ubuntu7.1 - * Generate a crash but don't report it. - * Upgrade to apport apport 2.20.9-0ubuntu7.3 - * Report this crash. - -> No apport crash should be triggered - - [Regression Potential] - * We are doing a python2 compatible try/except to ignore the KeyError which was the regression. It doesn't seem it can trigger other regressions. + [Regression Potential] + * We are doing a python2 compatible try/except to ignore the KeyError which was the regression. It doesn't seem it can trigger other regressions. ------- The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Importance: High => Medium ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1791324 Title: /usr/share/apport/apport-gtk:KeyError:/usr/share/apport/apport- gtk@598:run_argv:run_crashes:run_crash Status in apport package in Ubuntu: New Status in apport source package in Bionic: New Bug description: [Impact] * The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee * The theory is that those crashes are trigger by reports generated (but not send) pre apport 2.20.9-0ubuntu7.3. They don't hafe thus the "remember" key, and thus, the new apport, when reporting, is crashing. * We now ignore if the key isn't present and just consider the answer as "false", which is a no-op. [Test Case] * Install apport 2.20.9-0ubuntu7.1 * Generate a crash but don't report it. * Upgrade to apport apport 2.20.9-0ubuntu7.3 * Report this crash. -> No apport crash should be triggered [Regression Potential] * We are doing a python2 compatible try/except to ignore the KeyError which was the regression. It doesn't seem it can trigger other regressions. ------- The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/64f362ed27e5f6069d78b02c2cbca5c09fcc19ee contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
