Hello Brian, or anyone else affected, Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.1 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apport (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: In Progress Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Committed Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR:<stdin>:2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 <error: Cannot access memory at address 0x4f6dbdc0> This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
