After upgrade of Nvidia 304 drivers, mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags()

[Stephen Worthington]

The Nvidia 304 drivers were updated by an "apt update && apt upgrade" to 304.132-0ubuntu0.16.04.2. On the next reboot, mythfrontend crashed each time it was started. The mythfrontend.log file always shows the same messages - see the attached mythfrontend.log file.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: mythtv-frontend 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3 [origin: LP-PPA-mythbuntu-0.28]
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: tbs5922fe nvidia
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythfilldatabase.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: mythbuntu
CurrentDesktop: XFCE
Date: Sat Nov 5 00:30:56 2016
ExecutablePath: /usr/bin/mythfrontend.real
InstallationDate: Installed on 2012-08-25 (1531 days ago)
InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Release amd64 (20120425)
Installed_mythtv_dbg: 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f33652b2f29 <_ZN9QGLFormat18openGLVersionFlagsEv+313>: mov (%rax),%rax
 PC (0x7f33652b2f29) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 QGLFormat::openGLVersionFlags() () from /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5
 MythRenderOpenGL::Create (painter=..., device=0x0) at mythrender_opengl.cpp:114
 MythMainWindow::Init (this=0x19e8210, forcedpainter=...) at mythmainwindow.cpp:1160
 main (argc=3, argv=0x7ffd29d3e418) at main.cpp:1886
Title: mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags()
UpgradeStatus: Upgraded to xenial on 2016-10-08 (26 days ago)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo syslog video

[Stephen Worthington (stephen-jsw)]

I have now reverted to the previous Nvidia driver package version, Nvidia-304.131 and mythfrontend is starting up normally.

[Todd Brady (tcb2)]

After the 304.132 update, my mythfrontend started but seg faulted when a video was played with VPDAU or OpenGL. (Slim settings worked fine, but playback is choppy on my machine.) I have an old NVIDIA ION GPU. I upgraded to the 340.98 driver, and all appears to be working now, tho that may not be an option for all NVIDIA GPUs.

[Oliver Gerlich (ogerlich)]

This might be a problem with the Nvidia 304.132 driver, according https://devtalk.nvidia.com/default/topic/974456/f24-permission-problems-/?offset=2 . Apparently Direct Rendering and VDPAU playback only works for the root user when using that driver version.

The problem is also being reported at http://unix.stackexchange.com/q/321185/49753 and many other places. Apparently the only solution at the moment is to downgrade to the previous driver version (304.131).

[Mystica555 (mystica)]

Is anyone in "Stable" going to revert to the older, working, version?
Were there specific security fixes in this newer version you are attempting to keep track of?

When "long term stable" becomes "crashy" someone may need to rethink the use of the word "stable" - "Constant ABI" may be the preferable term.

[Thomas Mashos (tgm4883)]

Mystica555

It's worth nothing that LTS doesn't stand for "Long Term Stable" as you seem to think, but instead "Long Term Support". Further, I'm unsure where the restricted repository stands in terms of support as it's my understanding that main is the only repository that is supported by Canonical.

Also, closing the Mythbuntu task as it's no longer being developed.

[Thomas Mashos (tgm4883)]

Closing this task as it's no longer developed.

[Brian Murray (brian-murray)]

The retracer discovered that the core dump was truncated when trying to retrace this crash, from the retracer log file:

ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is truncated: expected core file size >= 2306977792, found: 2147479552.