mythlcdserver crashed with SIGSEGV in QMetaObject::activate()

[Aaron]

This happens randomly.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.25.0+fixes.20120525.eb1d4a7-0ubuntu0mythbuntu4 [origin: LP-PPA-mythbuntu-0.25]
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CrashDB: mythbuntu
Date: Sun May 27 07:52:03 2012
ExecutablePath: /usr/bin/mythlcdserver
InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythlcdserver --verbose general --loglevel info --syslog local7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x804bef6: lock incl (%eax)
 PC (0x0804bef6) ok
 source "(%eax)" (0x000f4240) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QTimer::timeout() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: mythlcdserver crashed with SIGSEGV in QMetaObject::activate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo video

[stew (st-witt)]

well - randomly....

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.