systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I do not know what happened. When I booted system this message popped up.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu6
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Tue Apr 3 19:21:14 2018
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2018-03-12 (22 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__GI__
?? () from /lib/systemd/
?? () from /lib/systemd/
journal_
?? () from /lib/systemd/
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
2 overridden configuration files found.
Title: systemd-journald crashed with SIGABRT in __GI___
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekG
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754214, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.