update-manager crashed with SIGSEGV in debListParser::LoadReleaseInfo()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
update-manager crashed when clicking on a red warning sign in the top that told me, that some sources could not be fetched
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.185
ProcVersionSign
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Thu Mar 21 18:59:47 2013
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f0378fe38c2 <_ZN13debListPa
PC (0x7f0378fe38c2) ok
source "%r12d" ok
destination "0xc(%rax)" (0x7f03753819ec) in non-writable VMA region: 0x7f0374022000-
Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: update-manager
StacktraceTop:
debListParser:
debPackagesInd
?? () from /usr/lib/
pkgCacheGenera
pkgCacheFile:
Title: update-manager crashed with SIGSEGV in debListParser:
UpgradeStatus: Upgraded to raring on 2013-03-11 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
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 #957231, 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.