mythfrontend crashes on WatchTV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MythTV |
New
|
Unknown
|
|||
Mythbuntu |
Expired
|
High
|
Unassigned |
Bug Description
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://
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://
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: mythtv-frontend 2:0.25.
ProcVersionSign
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelMo
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashDB: mythbuntu
Date: Wed Apr 11 22:03:34 2012
ExecutablePath: /usr/bin/
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f2daa33a3f3 <DecoderBase:
PC (0x7f2daa33a3f3) ok
source "-0x18(%rcx)" (0xffffffffffff
destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
DecoderBase:
DecoderBase:
NuppelDecoder:
MythPlayer:
MythPlayer:
Title: mythfrontend.real crashed with SIGSEGV in DecoderBase:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
XsessionErrors:
(update-
(update-
Changed in mythtv: | |
status: | Unknown → New |
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!