ModemManager crashed with SIGSEGV in g_mutex_lock()

[rhhoek]

bug appeared apparently without user intervention

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Tue Oct 17 15:46:59 2017
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2017-08-15 (62 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815)
ProcCmdline: /usr/sbin/ModemManager
SegvAnalysis:
 Segfault happened at: 0x7f7b911a25b5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f7b911a25b5) ok
 source "%eax" ok
 destination "(%rdi)" (0x00400000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libqmi-glib.so.5
 qmi_device_close_async () at /usr/lib/x86_64-linux-gnu/libqmi-glib.so.5
 qmi_device_close () at /usr/lib/x86_64-linux-gnu/libqmi-glib.so.5
Title: ModemManager crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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 #1703595, 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.