totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from _cogl_driver_update_features() from _cogl_winsys_context_init()

[preethi]

ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

result of the [Totem does not play MOV file with x264 encoding ]
Bug # - 1810022

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu6.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Jan 8 04:41:26 2019
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/totem
ExecutableTimestamp: 1542122228
InstallationDate: Installed on 2018-11-12 (56 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
JournalErrors:
 Hint: You are currently not seeing messages from other users and the system.
       Users in groups 'adm', 'systemd-journal' can see all messages.
       Pass -q to turn off this notice.
 -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 IST. --
 -- No entries --
LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory
ProcCmdline: totem DJI_0001.MOV
ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: totem
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_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: totem crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 _cogl_context_get_gl_extensions (context=context@entry=0x55a1f7e08d90) at cogl-context.c:700
 _cogl_driver_update_features (context=0x55a1f7e08d90, error=<optimized out>) at driver/gl/gles/cogl-driver-gles.c:260
 _cogl_winsys_context_init (context=0x55a1f7e08d90, error=<optimized out>) at winsys/cogl-winsys-stub.c:110
 cogl_context_new (display=0x55a1f7db2590, error=error@entry=0x7ffe2012cb20) at cogl-context.c:237

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 _cogl_context_get_gl_extensions (context=context@entry=0x55a1f7e08d90) at cogl-context.c:700
 _cogl_driver_update_features (context=0x55a1f7e08d90, error=<optimized out>) at driver/gl/gles/cogl-driver-gles.c:260
 _cogl_winsys_context_init (context=0x55a1f7e08d90, error=<optimized out>) at winsys/cogl-winsys-stub.c:110
 cogl_context_new (display=0x55a1f7db2590, error=error@entry=0x7ffe2012cb20) at cogl-context.c:237

[Daniel van Vugt (vanvugt)]

I'm not yet convinced this is the same as bug 1730241.

The stack trace is different, and the above Xorg logs shows there is Nvidia hardware:

[ 57.822] (II) NVIDIA(0): NVIDIA GPU GeForce 210 (GT218) at PCI:3:0:0 (GPU-0)
[ 57.822] (--) NVIDIA(0): Memory: 524288 kBytes

[preethi (preethi1433)]

PFA the lspci -k output.

Should NVIDIA driver be uninstalled?

We located this problem when trying to load these .MOV videos in MATLAB and GStreamer threw error regarding missing codecs. To cross-verify, we tried playing it in mkv and vlc (which worked), but totem failed.

P.S. Apologise for the delay. Was traveling to a conference.

[Daniel van Vugt (vanvugt)]

Thanks. That confirms you have Nvidia hardware and the Nvidia driver:

03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
 Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210]
 Kernel driver in use: nvidia
 Kernel modules: nvidiafb, nouveau, nvidia

Although the nature of the crash (comment #5) makes me think this is either an Nvidia driver bug (or faulty installation), or a cogl bug.

[Daniel van Vugt (vanvugt)]

Please try reinstalling the Nvidia driver:

  sudo apt install --reinstall nvidia-340

then reboot and tell us if the problem persists.

[preethi (preethi1433)]

Thank you Daniel!

Reinstalling the nvidia-340 driver resolved the issue.

It was causing us a significant delay in our work. Thank you for helping in resolution.