systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
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
ProcVersionSign
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/
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/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: systemd
StacktraceTop:
__GI__
?? () from /lib/systemd/
?? () from /lib/systemd/
journal_
?? () from /lib/systemd/
Title: systemd-journald crashed with SIGABRT in __GI___
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.
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.family: Type1Family
dmi.product.name: SATELLITE L830
dmi.product.
dmi.sys.vendor: TOSHIBA
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.