fwupd crashed with SIGSEGV in _int_malloc()

Bug #1664874 reported by Nazar Gerasymchuk
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
New
Undecided
Unassigned

Bug Description

This problem happens on each login.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: fwupd 0.8.0-2
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 14 23:38:54 2017
ExecutablePath: /usr/lib/fwupd/fwupd
ExecutableTimestamp: 1486749498
InstallationDate: Installed on 2017-01-08 (37 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
ProcCmdline: /usr/lib/fwupd/fwupd
ProcCwd: /
SegvAnalysis:
 Segfault happened at: 0x7f43ab6a7c8d <_int_malloc+109>: mov 0x10(%r14),%rdx
 PC (0x7f43ab6a7c8d) ok
 source "0x10(%r14)" (0x55d900000010) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: fwupd
StacktraceTop:
 _int_malloc (av=av@entry=0x7f43ab9e5b00 <main_arena>, bytes=bytes@entry=72) at malloc.c:3413
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3271
 g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_closure_new_simple () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_cclosure_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: fwupd crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Nazar Gerasymchuk (troyan3) 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 #1663548, 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.

Other bug subscribers

Remote bug watches

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