ModemManager crashed with SIGSEGV in g_mutex_lock()

[Biswajit biswas]

Ubuntu bug encounter when system booting time

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: modemmanager 1.6.8-2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Fri Mar 30 03:00:14 2018
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2018-03-26 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f9a03effcd5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f9a03effcd5) ok
 source "%eax" ok
 destination "(%rdi)" (0x7720746e65696c63) 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: Upgraded to bionic on 2018-03-26 (3 days ago)
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.