totem crashed with SIGSEGV

[Theo Papageorgiou]

Repeated issue with Totem not playing video (audio tracks still audible) whilst using Nvidia proprietary drivers under Ubuntu 17.10. X.Org Nouveau drivers appear to work properly. Crash occurred after switching back to latest Nvidia drivers for testing purposes.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libgstreamer1.0-0 1.12.3-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 18:36:32 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-08-03 (82 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f1d66284b59: mov (%rsi),%rsi
 PC (0x7f1d66284b59) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gstreamer1.0
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_renderer_connect () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
Title: totem crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1681210, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.