update-manager crashed with SIGSEGV in PyEval_EvalFrameEx()

[Brian Murray]

I was trying to recreate bug 938116 and encountered this bug.

Test case:
1) expand details in update-manager package list
2) change your mirror in settings
3) apply
4) watch update-manager crash

Interestingly, the crash will be unreportable because, I believe, the package cache is updating and apt-cache policy for update-manager shows:

update-manager:
  Installed: 1:0.156.7
  Candidate: 1:0.156.7
  Version table:
 *** 1:0.156.7 0
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
CheckboxSubmission: fee5e196cb921cbd36888f428b38b488
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
Date: Wed Mar 7 12:13:04 2012
ExecutablePath: /usr/bin/update-manager
ExecutableTimestamp: 1330935159
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager
ProcCwd: /home/theman
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f1f28bd321b: cmpw $0x202,0x26(%rax)
 PC (0x7f1f28bd321b) ok
 source "$0x202" ok
 destination "0x26(%rax)" (0x031d6fe6) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 function_call ()
 PyObject_Call ()
Title: update-manager crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: Upgraded to precise on 2012-02-21 (14 days ago)
UserGroups: adm admin audio cdrom dialout dip family floppy fuse libvirtd lpadmin plugdev pulse pulse-access sambashare sbuild scanner video

[Apport retracing service (apport)]

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 #947837, 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.