** Changed in: glib2.0 (Ubuntu)
Assignee: nassim (moujane) => (unassigned)
--
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
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => nassim (moujane)
--
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
This bug was fixed in the package apport - 2.20.3-0ubuntu8.3
---
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium
* Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
*
This bug was fixed in the package apport - 2.20.4-0ubuntu4.1
---
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium
* Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
* Resolve autopkgtest
Verification for yakkety:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz
Verification for zesty:
Hello Brian, or anyone else affected,
Accepted apport into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
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
** Description changed:
+ [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
** Changed in: apport (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: apport (Ubuntu Yakkety)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Zesty)
Status: New => In Progress
** Changed in: apport (Ubuntu Zesty)
Assignee:
** Also affects: glib2.0 (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Zesty)
I tested the yakkety core file and binary with a xenial version of gdb
and didn't still received the cannot access memory error, so I don't
think its a gdb bug.
** Package changed: gdb (Ubuntu) => glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
11 matches
Mail list logo