I would like to (somehow) request the journal files from the affected
systems to see if this crash is due to corrupt journal files, and
therefore is reproducible and should be fixed upstream (to become even
more resilient to corrupted journal files).
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668802
Title:
/lib/systemd/systemd-
journald:6:journal_file_entry_array_n_items:link_entry_into_array:journal_file_link_entry:journal_file_append_entry_internal:journal_file_append_entry
Status in systemd package in Ubuntu:
Incomplete
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
systemd. This problem was most recently seen with package version
231-9ubuntu2, the problem page at
https://errors.ubuntu.com/problem/5d26a3a04bae890ad487f4cdead3465032fa8828
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at
http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668802/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
