aptd crashed with SIGSEGV in __GI___libc_free()

Bug #1299256 reported by Marin Treselj
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Errors Bucket:
https://errors.ubuntu.com/bucket/?id=/usr/sbin/aptd%3A11%3A__GI___libc_free%3Ag_free%3Ag_callable_info_free_closure%3A_pygi_invoke_closure_free%3A_pygi_destroy_notify_callback_closure

Multiple crashes with package-related apps when starting Ubuntu (14.04, after update from 13.10)

ProblemType: CrashDistroRelease: Ubuntu 14.04
Package: aptdaemon 1.1.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
Date: Fri Mar 28 07:41:58 2014
ExecutablePath: /usr/sbin/aptd
InstallationDate: Installed on 2012-08-11 (594 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/sbin/aptd
ProcEnviron: LANG=C.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb75cf7c6 <__GI___libc_free+38>: mov -0x4(%ecx),%ecx
 PC (0xb75cf7c6) ok
 source "-0x4(%ecx)" (0x0000bc84) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: aptdaemon
StacktraceTop:
 __GI___libc_free (mem=0xbc88) at malloc.c:2929
 g_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_callable_info_free_closure () from /usr/lib/libgirepository-1.0.so.1
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-34m-i386-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-34m-i386-linux-gnu.so
Title: aptd crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: Upgraded to trusty on 2014-03-26 (2 days ago)
UserGroups:

Revision history for this message
Marin Treselj (phyzik) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___libc_free (mem=0xbc88) at malloc.c:2929
 g_free (mem=0xbc88) at /build/buildd/glib2.0-2.40.0/./glib/gmem.c:190
 g_callable_info_free_closure (callable_info=0xa5e8a60, closure=0xb701f0d0) at girepository/girffi.c:426
 _pygi_invoke_closure_free (data=0xa5f0150) at ../../gi/pygi-closure.c:638
 _pygi_destroy_notify_callback_closure (cif=0xa525b8c, result=0xbf87d060, args=0xbf87d000, data=0x0) at ../../gi/pygi-closure.c:703

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in aptdaemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Marin Treselj (phyzik) wrote :

These bugs are probably related:
#1299254, #1299256, #1299257

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in aptdaemon (Ubuntu):
status: New → Confirmed
information type: Private → Public
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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