totem is coredumping, ubuntu-bug on the crash file is failing

[Jonathan Kamens]

Totem is crashing on launch.

I see in /var/crash that the crash was reported, with crash id affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug on the crash file it reports this:

ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
    symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
    response = ui.choice("How would you describe the issue?", ["The totem interface is not working correctly", "No sound is being played", "Some audio files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'

So that's two different issues -- the crash and the fact that I can't report it using ubuntu-bug.

I'm hoping you can pull the crash from the ID above and maybe do something useful with it. :shrug:

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 15
   Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. I am looking at crash ID affaa5ef-11fd-11ed-a50a-fa163e55efd0 but it doesn't seem to have a stack trace (yet?). Only that totem crashed with signal 11.

Maybe wait until it happens again and then report a new bug. And if 'ubuntu-bug' fails then 'apport-cli' may work instead.

[Daniel van Vugt (vanvugt)]

The most common totem crashes in Ubuntu 22.04 are listed here:

https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=totem&period=week

[Jonathan Kamens (jik)]

Presumably it doesn't have a stack trace because it didn't upload successfully. I don't know how to fix that.

It's crashing reliably for me but it isn't producing a new crash each time in /var/crash, just the first one is there.

apport-cli isn't working either. I tell it to send the report and then it exits without doing anything:

jik@jik5:~$ apport-cli /var/crash/_usr_bin_totem.1000.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (27.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s
jik@jik5:~$

[Jonathan Kamens (jik)]

OK, I installed debug symbols and ran totem inside gdb, and this looks like the most common crash listed there, i.e., bug 1973570:

(gdb) where
#0 ___pthread_mutex_destroy (mutex=mutex@entry=0x0) at ./nptl/pthread_mutex_destroy.c:31
#1 0x00007ffff7e282a0 in g_rec_mutex_impl_free (mutex=0x0) at ../../../glib/gthread-posix.c:299
#2 g_rec_mutex_clear (rec_mutex=rec_mutex@entry=0x7fff980b33a8) at ../../../glib/gthread-posix.c:376
#3 0x00007ffff6d45f7c in gst_video_decoder_finalize (object=0x7fff980b3290 [GstVaapiDecode]) at ../gst-libs/gst/video/gstvideodecoder.c:943
#4 0x00007ffff7ee0dfd in g_object_unref (_object=<optimised out>) at ../../../gobject/gobject.c:3678
#5 g_object_unref (_object=0x7fff980b3290) at ../../../gobject/gobject.c:3553
#6 0x00007ffff6e5ccd3 in gst_object_unref (object=<optimised out>) at ../gst/gstobject.c:267
#7 0x00007ffff6e664c0 in gst_bin_remove_func (bin=0x555556591830 [GstVaapiDecodeBin], element=<optimised out>) at ../gst/gstbin.c:1815
#8 0x00007ffff6e6170b in gst_bin_remove (bin=bin@entry=0x555556591830 [GstVaapiDecodeBin], element=0x7fff980b3290 [GstVaapiDecode]) at ../gst/gstbin.c:1867
#9 0x00007ffff6e61e2b in gst_bin_dispose (object=0x555556591830 [GstVaapiDecodeBin]) at ../gst/gstbin.c:527
...

Having said that, we still have the problem that neither ubuntu-bug nor apport-cli are able to successfully report this crash. Should we convert this bug into that issue and leave the other ticket for the crash issue?

[Daniel van Vugt (vanvugt)]

Thanks for the stack trace. We can track it in bug 1973570 now...

[Brian Murray (brian-murray)]

There are currently some infrastructure issues with the crash retracers which are causing a backlog in the retracing system for the crashes. Given that Daniel could see the crash it was in fact successfully reported.