Hello Benjamin, or anyone else affected, Accepted apport into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3.3 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. -- 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/2073933 Title: tests/integration/test_signal_crashes.py::T::test_core_dump_packaged fails on armhf Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Noble: Fix Committed Bug description: [ Impact ] The Apport 2.29.0 test case `tests/integration/test_signal_crashes.py::T::test_core_dump_packaged` can fail on armhf: ``` 394s =================================== FAILURES =================================== 394s __________________________ T.test_core_dump_packaged ___________________________ 394s 394s self = <tests.integration.test_signal_crashes.T testMethod=test_core_dump_packaged> 394s 394s def test_core_dump_packaged(self): 394s """Packaged executables create core dumps on proper ulimits.""" 394s # for SEGV and ABRT we expect reports and core files 394s for sig in (signal.SIGSEGV, signal.SIGABRT): 394s for kb, exp_file in core_ulimit_table: 394s resource.setrlimit(resource.RLIMIT_CORE, (kb, -1)) 394s self.do_crash( 394s expect_corefile=exp_file, 394s expect_corefile_owner=os.geteuid(), 394s sig=sig, 394s ) 394s > self.check_report_coredump(self.test_report) 394s 394s /tmp/autopkgtest.GVBNRi/autopkgtest_tmp/tests/integration/test_signal_crashes.py:426: 394s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 394s /tmp/autopkgtest.GVBNRi/autopkgtest_tmp/tests/integration/test_signal_crashes.py:1216: in check_report_coredump 394s self.assertIn("\n#2", r.get("Stacktrace")) 394s E AssertionError: '\n#2' not found in '#0 0xf7fe2734 in ?? ()\nNo symbol table info available.\n#1 0xf7fef000 in ?? ()\nNo symbol table info available.\nBacktrace stopped: previous frame identical to this frame (corrupt stack?)' ``` Full log: https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/armhf/a/apport/20240618_034715_7581f@/log.gz [ Test Plan ] Check that the fixed Apport does not have failing unit-and- integration-tests autopkgtests on all archs. [ Where problems could occur ] The fix only touches test code. It could only affect the test results, but not code installed on the users machines. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2073933/+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
