udisksd crashed with SIGSEGV in g_mutex_lock()

[Gordon McIntosh]

This occurs when starting 18.04Lts

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CustomUdevRuleFiles: 70-snap.core.rules
Date: Wed Mar 7 23:09:34 2018
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationDate: Installed on 2018-01-12 (54 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171205)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcCmdline: /usr/lib/udisks2/udisksd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic root=UUID=93363653-4e96-45dc-973d-7189bcd83d82 ro recovery nomodeset
SegvAnalysis:
 Segfault happened at: 0x7f21769c4be5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f21769c4be5) ok
 source "%eax" ok
 destination "(%rdi)" (0x75736f6e2c777220) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 main ()
Title: udisksd crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A48F1020
dmi.board.name: H67M-S/H67M-V/H67
dmi.board.vendor: Foxconn
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA48F1020:bd02/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH67M-S/H67M-V/H67:rvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Apport retracing service (apport)]

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 #1707451, 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.