Ubuntu
aptdaemon package

aptd crashed with SIGSEGV in visit_decref()

Bug #929689 reported by Dale Beaudoin on 2012-02-09

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	aptdaemon (Ubuntu)	Won't Fix	Medium	Unassigned

Bug Description

I was searching for the file libc6 using synaptic package manager. I entered <libc6> using >edit>search -field-
and the above bug report was generated.

Synaptic has been having mutiple issues as reported by dino99 and confirmed by others. I am not sure if this is related.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: aptdaemon 0.43+bzr769-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Thu Feb 9 12:09:08 2012
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:

SegvAnalysis:
Segfault happened at: 0x812d40b: testb $0x40,0x55(%eax)
PC (0x0812d40b) ok
source "$0x40" ok
destination "0x55(%eax)" (0x00011b4e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: aptdaemon
StacktraceTop:
?? ()
?? ()
?? ()
PyGC_Collect ()
Py_Finalize ()
Title: aptd crashed with SIGSEGV in PyGC_Collect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

Dale Beaudoin (twocamels) wrote on 2012-02-09:

#1

AptConfig.txt Edit (5.5 KiB, text/plain; charset="utf-8")
AptTermLog.gz Edit (20.3 KiB, application/x-gzip)
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (508 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (498.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (13.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (740 bytes, text/plain; charset="utf-8")
Registers.txt Edit (466 bytes, text/plain; charset="utf-8")
SourcesList.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (417 bytes, text/plain; charset="utf-8")
SysLog.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (460 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-09:

#2

StacktraceTop:
visit_decref ()
dict_traverse ()
collect ()
PyGC_Collect ()
Py_Finalize ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-09: Stacktrace.txt

#3

Stacktrace.txt Edit (296 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-09: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (339 bytes, text/plain)

Changed in aptdaemon (Ubuntu):
importance:	Undecided → Medium
summary:	- aptd crashed with SIGSEGV in PyGC_Collect() + aptd crashed with SIGSEGV in visit_decref()
tags:	removed: need-i386-retrace

Revision history for this message

Sebastian Heinlein (glatzor) wrote on 2012-04-02:

#5

Is it possible to reproduce this error? If the error re-occurs please reopen the bug. With the provided information the bug cannot be resolved. So I will mark it as won't fix.

Changed in aptdaemon (Ubuntu):
status:	New → Won't Fix

Revision history for this message

Iain (iain-7) wrote on 2012-04-09:

#6

Can't reproduce = won't fix? Surely if you're getting the log files in and it's affecting multiple people.....

Revision history for this message

Sebastian Heinlein (glatzor) wrote on 2012-04-09:

#7

The bug cannot only not be reproduced but also the information of the stack trace isn't enough. So nobody will be able to locate the bug. The user also described the behavior of an application of another application (synaptic).

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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