Hello Didier, or anyone else affected, Accepted apport into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu82.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Jammy) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-jammy -- 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/1780767 Title: Some GTK UI tests are flaky due to timeout Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Fix Committed Bug description: [Impact] The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py: GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py: GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py: GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py: GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py: GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. The short term workaround to increase the timeout increases the test execution time by five minutes. [Test Plan] Check that the autopkgtest succeed on all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1780767/+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
