gnome-mpv crashed with SIGSEGV in g_object_unref()

[Paul White]

Testing Ubuntu MATE in a live environment - ISO 20190909

Crashed when trying to close application.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-mpv 0.16-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CasperVersion: 1.415
CurrentDesktop: MATE
Date: Mon Sep 9 13:48:23 2019
ExecutablePath: /usr/bin/gnome-mpv
LiveMediaBuild: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcCmdline: /usr/bin/gnome-mpv --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en
 LANG=C.UTF-8
SegvAnalysis:
 Segfault happened at: 0x55d92b55fad0: add $0x0,%eax
 PC (0x55d92b55fad0) in non-executable VMA region: 0x55d92b506000-0x55d92be04000 rw-p [heap]
 source "$0x0" ok
 destination "%eax" ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: gnome-mpv
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-mpv crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceSource:
 #0 0x000055d92b55fad0 in ?? ()
 #1 0x00007ff45319f3dc in ?? ()
 #2 0x000055d92b5541a0 in ?? ()
 #3 0x00007ff45319e7ef in ?? ()
 #4 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1843270

[Paul White (paulw2u)]

I haven't used Ubuntu MATE since shortly after creating this bug report. Closing as "Invalid" as never confirmed by another user and eoan is now EOL. If anyone does experience this issue on a currently supported release they should create their own bug report so that has their crash data is attached to the report.