systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Bug #1761770 reported by David Oser
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

Applying copy-paste action of documents (from host computer running Budgie-Ubuntu 17.10 to usb full installation running Budgie-Ubuntu 18.04 kernal 4.15.0-15) no apparent problem noted apart from system problem message

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 6 15:25:33 2018
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2018-03-12 (25 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
MachineType: TOSHIBA SATELLITE L830
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=2dc06f87-aa49-4d7c-b9d7-6b89f9320fc3 ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __GI___pthread_timedjoin_ex (threadid=140719257347840, thread_return=0x0, abstime=0x0, block=<optimised out>) at pthread_join_common.c:89
 ?? () from /lib/systemd/libsystemd-shared-237.so
 ?? () 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
Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.40:bd01/08/2013:svnTOSHIBA:pnSATELLITEL830:pvrPSKF2E-00K00FEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE L830
dmi.product.version: PSKF2E-00K00FEN
dmi.sys.vendor: TOSHIBA

Revision history for this message
David Oser (oserdavid) 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 #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.

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.