systemd-journald crashed with SIGABRT in fsync()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no additional information
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: Wed Apr 4 22:40:44 2018
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2017-06-04 (304 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0fce:01e5 Sony Ericsson Mobile Communications AB
Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X751LJ
ProcCmdline: /lib/systemd/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
fsync (fd=21) at ../sysdeps/
?? () from /lib/systemd/
journal_
?? () from /lib/systemd/
journal_
Title: systemd-journald crashed with SIGABRT in fsync()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/07/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X751LJ.706
dmi.board.
dmi.board.name: X751LJ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: X
dmi.product.name: X751LJ
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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 #1750855, 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.