[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2020-04-08 Thread Sebastien Bacher
** Changed in: glib2.0 (Ubuntu) Assignee: nassim (moujane) => (unassigned) -- 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/1689344 Title: print of __glib_assert_msg

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2020-04-08 Thread nassim
** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => nassim (moujane) -- 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/1689344 Title: print of __glib_assert_msg

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-22 Thread Launchpad Bug Tracker
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) *

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-22 Thread Launchpad Bug Tracker
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

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-15 Thread Brian Murray
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:

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-12 Thread Łukasz Zemczak
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

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-12 Thread Łukasz Zemczak
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

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-12 Thread Brian Murray
** 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

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-10 Thread Brian Murray
** 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:

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-10 Thread Brian Murray
** 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)

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-09 Thread Brian Murray
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 Ubuntu Touch

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.4-0ubuntu6 --- apport (2.20.4-0ubuntu6) artful; 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) *

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-08 Thread Brian Murray
This was not failing in the autopkgtest for yakkety but does now in a chroot. (yakkety-amd64)root@impulse:/home/bdmurray/source-trees/apport/glib-assert-test# ./glib-assert.sh ** ERROR::2:main: assertion failed (1 < 0): (1 < 0) Aborted (core dumped) warning: core file may not match specified

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-08 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/artful/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-08 Thread Brian Murray
It's also worth noting that running strings on the core file does reveal the contents of the assertion message. $ strings core CORE main: assertion 1 < 0): (1 < 0) sertion failed ( LINUX main: assertion 1 < 0): (1 < 0) -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

2017-05-08 Thread Brian Murray
There is another apport test, "test_add_gdb_info_abort_libnih", which was disabled for similar reasons - e.g. "Cannot access memory". https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1580601 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,