touch-packages team mailing list archive

[Colin Watson <cjwatson@xxxxxxxxxxxxx>]

Only i386 builds were affected, but that included all Architecture: all
builds.  Peculiar.  My best speculation is that perhaps a change in
precise-updates was enough to perturb away the apt bug, but then that
allowed the PPA to also change so that now even a combination of
precise-updates at the time of the breakage plus the current state of
the PPA isn't enough to reproduce the problem.  That sort of thing is,
unfortunately, quite usual for this kind of subtle apt bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/957231

Title:
  update-manager crashed with SIGSEGV in
  debListParser::LoadReleaseInfo()

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Committed
Status in apt source package in Saucy:
  Won't Fix
Status in apt source package in Trusty:
  Fix Released
Status in update-manager source package in Trusty:
  Invalid

Bug description:
  just would not complete the update

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.8
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 16 17:46:18 2012
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   com.ubuntu.update-manager first-run false
   com.ubuntu.update-manager launch-time 1331920010
   com.ubuntu.update-manager show-details true
   com.ubuntu.update-manager window-height 932
   com.ubuntu.update-manager window-width 731
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/update-manager
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f4c9838a019 <_ZN13debListParser15LoadReleaseInfoERN8pkgCache15PkgFileIteratorER6FileFdSs+1561>:	mov    %eax,0x14(%rbx)
   PC (0x7f4c9838a019) ok
   source "%eax" ok
   destination "0x14(%rbx)" (0x7f4c7bfea5c4) not located in a known VMA region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: update-manager
  StacktraceTop:
   debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   debPackagesIndex::Merge(pkgCacheGenerator&, OpProgress*) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
  Title: update-manager crashed with SIGSEGV in debListParser::LoadReleaseInfo()
  UpgradeStatus: Upgraded to precise on 2012-03-07 (8 days ago)
  UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom clamav colord couchdb crontab daemon dialout dip disk fax floppy fuse games gdm gnats kmem libuuid lightdm list lp lpadmin mail man messagebus mlocate netdev news ntp operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp vboxusers video voice whoopsie www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/957231/+subscriptions