systemd-journald crashed with SIGABRT in __ftruncate64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
don't know how this happen
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu8
Uname: Linux 4.17.0-
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 20 20:20:40 2018
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2018-03-04 (47 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 0bda:57b3 Realtek Semiconductor Corp. Acer 640 × 480 laptop camera
Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-533
ProcCmdline: /lib/systemd/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__ftruncate64 (fd=22, length=8388608) at ../sysdeps/
journal_
?? () from /lib/systemd/
?? () from /lib/systemd/
sd_event_dispatch () from /lib/systemd/
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
2 overridden configuration files found.
Title: systemd-journald crashed with SIGABRT in __ftruncate64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/18/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.
dmi.board.name: Stego_AP
dmi.board.vendor: Acer
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.family: APL
dmi.product.name: Aspire ES1-533
dmi.product.
dmi.sys.vendor: Acer
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 #1765305, 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.