Problem report is damaged, 'incorrect padding'

Bug #1012358 reported by Pieter
64
This bug affects 14 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

$ uname -a
Linux t420 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Virtual Machine manager
- Open win7 vm
- When i try and open the display after win booted up to gui, something crashes. And VM dies.
- Same happens if i close Gui vnc window and try and open later.

I get dialogue asking if i want to report the problem, I answer yes, and provide root credentials.

After a little while i get a dialogue.

[x] Invalid problem report
(-) This problem report is damaged and cannot be processed.
TypeError(Error('incorrect padding',),)
https://launchpadlibrarian.net/122356767/1012358-incorrect-padding.png

See also bug 999264, "IOError(13, 'Permission denied')".

Tags: quantal
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

I'm getting the same apport error message, on an up-to-date install of Quantal (amd64; BIOS version on a MacBook Pro 5,3). It happens immediately after login (which currently regularly triggers a bunch of errors that are caught by apport). Despite the message, apport opens a new browser tab to let me file the bug.

tags: added: quantal
Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This archive contains 11 crash reports from today. Two of them triggered the "TypeError(Error('incorrect padding',),)" error. Unfortunately, I couldn't tell which two.

description: updated
Revision history for this message
Michael Heuberger (michael.heuberger) wrote :

I confirm, these dialogues are a nuisance, see:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1080299

gad man (gadman)
summary: - This problem report is damaged and cannot be processed.
+ blueman applet crashed with DBusException in call_blocking():
+ org.openobex.Error.InvalidArguments: Invalid path
Revision history for this message
Man (aldpn) wrote : Re: blueman applet crashed with DBusException in call_blocking(): org.openobex.Error.InvalidArguments: Invalid path

I get multiple error on boot :

This problem report is damaged and cannot be processed.

Error('Incorrect padding',)

It is reayly annoying !! Multiple error windows pop ups every time on boot !!

Jani Uusitalo (uusijani)
summary: - blueman applet crashed with DBusException in call_blocking():
- org.openobex.Error.InvalidArguments: Invalid path
+ Problem report is damaged, 'incorrect padding'
Revision history for this message
olksy (noface) wrote :

This helped get rid of the message by vanishing broken files from apport dir -

sudo rm -v /var/crash/*

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.