aptd crashed with SIGSEGV in debListParser::LoadReleaseInfo()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| aptdaemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This error occurs after the Unity Desktop starts, if happens without any user interaction.
Ubuntu version:
Description: Ubuntu precise (development branch)
Release: 12.04
Aptdaemon version:
aptdaemon:
Installed: 0.43+bzr784-
Candidate: 0.43+bzr784-
Version table:
*** 0.43+bzr784-
500 http://
100 /var/lib/
What I'd expect to happen: The desktop should load without this error message
What happened instead: This error message occurred after the desktop loaded, but didn't appear to cause any other problems and no functionality appears to have been lost.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: aptdaemon 0.43+bzr784-
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Tue Mar 27 06:50:02 2012
DesktopFile: /usr/share/
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/sbin/aptd
ProcEnviron:
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: aptdaemon
Title: aptd crashed with SIGSEGV in debListParser:
UpgradeStatus: Upgraded to precise on 2012-02-04 (56 days ago)
UserGroups:
| Sweevo (mark-mark-stevenson) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #854090, 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.