ModemManager crashed with SIGSEGV

[fritz276]

Dont know.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: modemmanager 1.6.8-2
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 11 19:02:30 2018
ExecutablePath: /usr/sbin/ModemManager
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x55d771dd4659: repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x55d771dd4659) ok
 source "%es:(%rdi)" (0x55d771e68b28) ok
 destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ()
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ModemManager crashed with SIGSEGV
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 #1725164, 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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[INIZAN yannick (inizan-yannick)]

1725164 bug page doesn't exist anymore

[AzureRaptor (xrg-ubuntunineteen-10-spamviking)]

Just got this after rebooting. No idea what's going on here, I have no modems attached to this machine. I don't believe it is the same as the other bug, as the routine listed as crashing was neither g_closure_invoke() nor the one in the other bug. I have no idea what it actually _was_; I would have expected that to be attached with my own bug report but it wasn't. :/