[Bug 1993025] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()

[Benjamin Drung]

You can open the .crash file from /var/crash with a text editor. Then
you can cut and paste the parts you want. If you don't want to submit
the core dump, you can use apport-retrace to retrace the dump locally.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1993025

Title:
  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Directly after a resume from suspend on Ubuntu 22.04 LTS I got an
  crash report with the message

  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

  I'm too concerned about the private information included in, for
  example, the coredump, to submit so I'm making this separate bug
  report. I have preserved the bug file in case it turns out to be
  important.

  ProblemType: Crash
  Architecture: amd64
  Date: Sat Oct 15 09:11:42 2022
  DistroRelease: Ubuntu 22.04
  ExecutablePath: /usr/lib/systemd/systemd-journald
  ExecutableTimestamp: 1662749236
  ProcCmdline: /lib/systemd/systemd-journald
  ProcCwd: /
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1993025/+subscriptions