== System information ==
Ubuntu 23.10, up to date before today’s updates.
== Steps to reproduce (WIP) ==
0. have a group of packages that are kept back from updating, plus some that aren’t (screenshot demonstration attached) below
1. open update-manager
2. (try to) open the kept group, click on their (unchecked) checkboxes
3. do the same for some of the other, non-kept packages
4. repeat 2.-3. for a while
== What happens ==
Update-manager becomes unresponsive, then eventually segfaults:
update-manager[3292]: segfault at 30 ip 00007fc0718b4c41 sp 00007ffc2cca6a68 error 4 in libgobject-2.0.so.0.7800.0[7fc071889000+34000] likely on CPU 4 (core 0, socket 0)
== Other info ==
I’ve marked the steps above WIP because these are the conditions under which I found this today, but I haven’t yet tried narrowing them down, because of course I have little control over which updates are available. (For instance, the kept packages might just be a red herring.)
I initially tried to report the crash file with ubuntu-bug, but despite asking preliminary questions, in the end it never opened a browser to complete the report. I’ll try apport-collect next, but if that fails too, I’ll just attach the crash file here manually.
For the ’Incorrect padding’ issue, Bug #1012358. (Leaving this as non-duplicate, since the reporter has other ’damaged’ errors besides that one.)
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.)
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: 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.
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”.
