This bug was fixed in the package apport - 2.23.1-0ubuntu3.1
---
apport (2.23.1-0ubuntu3.1) kinetic; urgency=medium
* Declare python3-apport breaking older apport/apport-gtk/apport-kde
(LP: #1997759)
* Catch malformed problem report (LP: #1996040)
* Catch ValueError: not
I verified the test results and am satisfied that they show the executed
planned test case, and that the results are correct.
The package built correctly in all architectures and Ubuntu releases it
was meant for.
There are no DEP8 regressions.
There is no SRU freeze ongoing at the moment.
Verified:
```
$ printf 'AB\xfc:CD\n' > malformed.crash
$ apport-unpack malformed.crash unpack
ERROR: Malformed problem report: 'ascii' codec can't decode byte 0xfc in
position 2: ordinal not in range(128). Is this a proper .crash text file?
```
** Tags removed: verification-needed
Hello Mingun, or anyone else affected,
Accepted apport into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.23.1-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This happened in that way as I've originally posted: after some actions
in the GitKraken client it starts continually crashed, core files are
appeared in the /var/lib/apport/coredump. Because this file was created
inside apport folder, i thought it was in apports .crash file format and
it should
I have not enough data to answer that question. Feeding a core dump into
apport-unpack can let it crash (user error). I don't know if *all* of
those crashes were caused by users feeding a crash file into apport-
unpack. The crash reports on errors.ubuntu.com do not contain the input
file and I
I'd like to understand better exactly how it happened that the user got
this crash. Is it a matter of a corrupted .crash file on input, or is
it that the user tried to feed in a file that was not intended to be
input for apport-unpack? I see that the command line that triggered
this appears to
This bug was fixed in the package apport - 2.26.0-0ubuntu2
---
apport (2.26.0-0ubuntu2) lunar; urgency=medium
* fix: Mock query to Github in integration test
-- Benjamin Drung Fri, 24 Feb 2023 16:17:43 +0100
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Released
** Changed in: apport
Status: Fix Committed => Fix Released
--
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/1996040
Title:
apport-unpack cannot load gitkraken crash
https://github.com/canonical/apport/pull/52 and
https://github.com/canonical/apport/pull/53 got merged into main.
** Changed in: apport
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Let's reopen this bug report again.
** Changed in: apport (Ubuntu)
Status: Fix Released => Triaged
** Changed in: apport
Milestone: 2.24.0 => 2.25.0
** Changed in: apport
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Upstream merge request to fix that case:
https://github.com/canonical/apport/pull/52
--
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/1996040
Title:
apport-unpack cannot
If the intent was to have apport-unpack deal with any invalid crash file, then
it's not complete. This still happens now:
ubuntu@k-apport:~$ apport-unpack /bin/ls unpack
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 174, in load
(key,
This bug was fixed in the package apport - 2.24.0-0ubuntu1
---
apport (2.24.0-0ubuntu1) lunar; urgency=medium
* New upstream bug-fix release.
- Catch malformed problem reports (LP: #1996040)
- Catch ValueError: not enough values to unpack (LP: #1995100)
- Catch
** Description changed:
+ Impact
+ ==
+
+ apport-unpack and whoopsie-upload-all can crash when fed with a
+ malformed problem report. They should print a proper error message
+ instead of crashing.
+
+ Test Plan
+ =
+
+ 1. Create malformed report:
+ ```
+ printf 'AB\xfc:CD\n' >
** Changed in: apport
Status: Fix Committed => Fix Released
--
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/1996040
Title:
apport-unpack cannot load gitkraken crash
The fix got merged to main:
https://github.com/canonical/apport/commit/4dbc5f9d16f0d652a360e3ca4827c69954b61241
** Changed in: apport
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Upstream merge request: https://github.com/canonical/apport/pull/24
** Changed in: apport (Ubuntu)
Status: Triaged => In Progress
** Changed in: apport
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.24.0
** Changed in: apport
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Status: New =>
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
apport-unpack is designed for unpackaging .crash files (in /var/crash).
You specified a core file which contains only binary data and is
expected to fail. apport-unpack should print an error message in this
case.
20 matches
Mail list logo
