ModemManager crashed with SIGSEGV in g_closure_invoke()

Bug #1670178 reported by Aaahh Ahh
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
New
Undecided
Unassigned

Bug Description

modprobe mt7610u_sta

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: modemmanager 1.6.4-1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Sun Mar 5 14:19:19 2017
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2015-10-01 (521 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150930)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x55abb8b0fab7: repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x55abb8b0fab7) ok
 source "%es:(%rdi)" (0x55abb8ba23fa) ok
 destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to zesty on 2017-01-01 (63 days ago)
UserGroups:

Revision history for this message
Aaahh Ahh (woohoomoo2u) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.