[Bug 2130649] Re: [SRU] whoopsie drops the ShellJournal field
Timo Aaltonen
2130649 at bugs.launchpad.net
Sat Nov 29 22:39:59 UTC 2025
Hello Skia, or anyone else affected,
Accepted whoopsie into plucky-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/whoopsie/0.2.79ubuntu0.25.04.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, what testing has been
performed on the package and change the tag from verification-needed-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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.
** Changed in: whoopsie (Ubuntu Plucky)
Status: New => Fix Committed
** Tags added: verification-needed-plucky
** Changed in: whoopsie (Ubuntu Noble)
Status: New => Fix Committed
** Tags added: verification-needed-noble
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/2130649
Title:
[SRU] whoopsie drops the ShellJournal field
Status in Whoopsie:
Confirmed
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Noble:
Fix Committed
Status in whoopsie source package in Plucky:
Fix Committed
Status in whoopsie source package in Questing:
Fix Committed
Status in whoopsie source package in Resolute:
Fix Released
Bug description:
[ Impact ]
This bug revolves around the error reporting story in Ubuntu, which is what's
behind https://errors.ubuntu.com .
GNOME is generating error reports that include a `ShellJournal` field [1], but
`whoopsie` (the service uploading the report) doesn't allow it.
That means the error reporting story for GNOME crashes isn't great, and slows
down the fixing of bugs in this particular situation.
More generally, the proposed fix would add the current `ShellJournal` field,
because it's the name currently in use in GNOME, but also adds a more generic
`JournalAll` field, that only has a better naming, in the goal of deprecating
the `ShellJournal` field when GNOME is updated.
`JournalAll` would in effect allow any other application to include generic
`journalctl` output.
[ Test Plan ]
To perform this test plan, one needs to be part of the `error-tracker-
access` LP group.
* Put the two crash files attached to this bug in an empty folder (see their description for details).
* From that folder, run the following to make sure both crashes would be candidate for upload:
touch _usr_libexec_gnome-shell-calendar-server.1000.upload _usr_libexec_gnome-shell-calendar-server_smaller_fields.1000.upload
* Then, still from that folder, run the `whoopsie` under test with the following:
CRASH_DB_URL=https://daisy.ubuntu.com APPORT_REPORT_DIR=$(pwd) CRASH_DB_IDENTIFIER=bug-2130649-verification-$(lsb_release -cs) whoopsie --no-polling -f
This should report two OOPSes being reported with a line like the following:
[13:24:52] Reported OOPS ID bd7ad35e-c9f9-11f0-a191-fa163e171f02
Gather the two UUIDs and go to each OOPS page (https://errors.ubuntu.com/oops/<uuid>).
With a non-fixed `whoopsie`, only `JournalError` will appear on the non "smaller_fields" crash report, whereas all three fields will be there with a fixed `whoopsie`.
With the "smaller_fields" crash, all three fields should always be there.
[ Where problems could occur ]
* `whoopsie` is a C application doing networking and parsing. Many things could
go wrong, but the patch only adds two lines to an allow-list, so hopefully if
it's working today, it shouldn't break too much.
* `whoopsie` isn't directly useful to an Ubuntu system, and is actually not
enabled by default on Ubuntu Server. It's only triggered when some change
happen in `/var/crash` (like file creation). Hopefully if it's broken, the user
impact is very limited, and only Ubuntu development (crash reporting) would see
the effects.
[ Other Info ]
This was first discussed on Matrix [2], as well as in person with the
Desktop team.
[1]: https://salsa.debian.org/gnome-team/gnome-shell/-/blob/ubuntu/latest/debian/source_gnome-shell.py?ref_type=heads#L42
[2]: https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$aZlRcLJiPXDNk_sWwfkDTtcKZrJ3L4iUaMZ_HvK1WdI?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/2130649/+subscriptions
More information about the foundations-bugs
mailing list