aptd crashed with SIGSEGV in __GI___libc_free()

Bug #1299426 reported by Mihail
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptdaemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Bug appears immediately after logging in, without any application runs.

ProblemType: Crash
DistroRelease: 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: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
Date: Fri Mar 28 14:01:32 2014
ExecutablePath: /usr/sbin/aptd
InstallationDate: Installed on 2014-03-27 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/sbin/aptd
ProcEnviron: LANG=C.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb766f7c6 <__GI___libc_free+38>: mov -0x4(%ecx),%ecx
 PC (0xb766f7c6) ok
 source "-0x4(%ecx)" (0x00009928) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
 __GI___libc_free (mem=0x992c) 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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Mihail (mihail-rozshko) 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 #1299256, 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-i386-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.