systemd-journald crashed with SIGABRT in fsync()

Bug #1761323 reported by Jose Rosal
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
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/systemd-journald
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/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=0b9adc3a-8318-4a04-a408-4e68ff87d167 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: systemd
StacktraceTop:
 fsync (fd=21) at ../sysdeps/unix/sysv/linux/fsync.c:27
 ?? () from /lib/systemd/libsystemd-shared-237.so
 journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
 ?? () from /lib/systemd/libsystemd-shared-237.so
 journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
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.asset.tag: ATN12345678901234567
dmi.board.name: X751LJ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751LJ.706:bd12/07/2015:svnASUSTeKCOMPUTERINC.:pnX751LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X751LJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Jose Rosal (jsrosalg) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.