[Bug 1571145] Re: After update-manager -d crash apport reports report is damaged 'incorrect padding'

Daniel Curran-Dickinson 1571145 at bugs.launchpad.net
Tue May 3 16:19:43 UTC 2016

Unfortunately, I've since reinstalled that vm after having found a
workaround to get xenial installed only to discover that in a kvm vm
with qxl/spice compiz chews up huge amounts of cpu (I've reported a bug
in launchpad about that) and consequently reinstalled the vm, so I no
longer have the .crash (and didn't know about it before to include it,
and apport wasn't working, obviously).



On 16-05-03 10:38 AM, Brian Murray wrote:
> Could you add the .crash file to the bug report so we can see what went
> awry?
> ** Changed in: apport (Ubuntu)
>        Status: New => Incomplete

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.

  After update-manager -d crash apport reports report is damaged
  'incorrect padding'

Status in apport package in Ubuntu:

Bug description:
  After attempt to update to Xenia Xerial Final Beta via update-manager
  -d and getting a crash report (something about SUDO_UID), and
  attempting to support a crash report apport complains that the report
  is damaged due to inccorrect padding.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.19
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 16 01:41:14 2016
  InstallationDate: Installed on 2016-03-11 (35 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2016-04-16 (0 days ago)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list