Leaving this as non-duplicate
For the ’Incorrect padding’ issue, Bug #1012358. (Leaving this as non-duplicate, since the reporter has other ’damaged’ errors besides that one.)
Avainsanana Apport
A 100% reliable recipe for reproducing this in 12.04
I currently have a 100% reliable recipe for reproducing this in 12.04: trying to restore a saved session of Trusty crashes VirtualBox 4.3.2 (from Oracle), after which Apport’s ”TypeError(Error(’Incorrect padding’,),)” pops up. (The recipe works also after removing crash files from /var/crash.)
Seems to be just U2D which I was testing earlier today
Ah, it seems to be just U2D which I was testing earlier today. I too can file all the bugs I want against ’unity’, but if I try `ubuntu-bug unity-2d` all I get is the ”third party package” error. Reproduced this also in a clean VM to be sure.
The two dialogs are very, very inconsistent
- Combined screenshot of the ”System program problem detected” and ”Application problem” dialogs (50.6 KiB, image/png)
The two dialogs are very, very inconsistent: the dialog icon they use (DIALOG_QUESTION in one, the DIALOG_ERROR in the other), the dialog window title (”Application problem” vs. none), the dialog title and explanation style (brief vs. verbose), the ignore option missing from one… It’s almost as if the engineers behind the two dialogs have intentionally tried to make them as different from one another as possible. (No offence intended, I just think it’s funny although it is a genuine accessibility problem as well.) Also, one dialog seems to be minimizable whereas the other is not — though this doesn’t appear in Blair’s screenshot; it may be something introduced in Precise which the system my screenshot is from is running.
Can also be triggered by closing the dialog with mouse using the (x) button.
Can also be triggered by closing the dialog with mouse using the (x) button.
Apport retracing service: typo in ”Crash report cannot be processed” comment (”an useful”)
I got this comment from the bot in a bug report (bug #907668):
”Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:”
And so on.
Instead of ”an useful” it should say ”a useful”.