mythfrontend crashes on WatchTV

[alzyee]

When I click on Watch TV mythfrontend quits and a popup in the top right of the screen says there was a segmentation fault error code 139 and restarts mythfrontend.

This was not the case after a clean install of Mythbuntu 11.10 before updating (after installing drivers for capture card described below) it would display tv without any sound.

I am using a Hauppauge WinTV-HVR-950 as the capture card. I followed the instruction near the bottom of http://www.linuxtv.org/wiki/index.ph..._WinTV-HVR-950 . I used the file from here for the pl script http://www.kernel.org/doc/Documentat...ract_xc3028.pl
I was not able to get sox -r 48000 -w -c 2 -t ossdsp /dev/dsp1 -t ossdsp /dev/dsp command to work but the rest of it was okay

For ref. similar explanation at
http://ubuntuforums.org/showthread.php?t=1954841

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: mythtv-frontend 2:0.25.0+fixes.20120410.1f5962a-0ubuntu0mythbuntu3
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelModules: nvidia
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythcommflag.log:

.var.log.mythtv.mythfilldatabase.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythmetadatalookup.log:

.var.log.mythtv.mythpreviewgen.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythtv.setup.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashDB: mythbuntu
Date: Wed Apr 11 22:03:34 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_mythtv_dbg: 2:0.25.0+fixes.20120410.1f5962a-0ubuntu0mythbuntu3
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2daa33a3f3 <DecoderBase::PosMapFromEnc()+307>: mov -0x18(%rcx),%r12
 PC (0x7f2daa33a3f3) ok
 source "-0x18(%rcx)" (0xffffffffffffffe8) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 DecoderBase::PosMapFromEnc (this=0x2091cf0) at decoderbase.cpp:245
 DecoderBase::SyncPositionMap (this=0x2091cf0) at decoderbase.cpp:322
 NuppelDecoder::OpenFile (this=0x2091cf0, rbuffer=<optimized out>, novideo=<optimized out>, testbuf=<optimized out>) at nuppeldecoder.cpp:623
 MythPlayer::OpenFile (this=0x1c249f0, retries=<optimized out>) at mythplayer.cpp:964
 MythPlayer::JumpToProgram (this=0x1c249f0) at mythplayer.cpp:2620
Title: mythfrontend.real crashed with SIGSEGV in DecoderBase::PosMapFromEnc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
XsessionErrors:
 (update-manager:1814): Gtk-WARNING **: Attempting to add a widget with type aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin subclass a GtkWindow can only contain one widget at a time; it already contains a widget of type GtkVBox
 (update-manager:1814): Gtk-WARNING **: Attempting to add a widget with type aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin subclass a GtkWindow can only contain one widget at a time; it already contains a widget of type GtkVBox

[MarcRandolph (mrand)]

Howdy, and thank you for helping to improve Mythbuntu by opening this ticket. I've forwarded the details to the developers - we'll see if they can find anything!

[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/979509

[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.