mythfrontend.real crashed with SIGSEGV in sws_scale()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mythtv (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mythtv
I started watching live TV. All commands stopped working and after some minutes Mythtv crashed.
Environment: Asus M3N78-EM motherboard, 4GB RAM, AMD Phenom X810, Technisat Cablestar 2 HD DVB-C card
Ubuntu karmic (development branch), Release: 9.10
mythtv-frontend:
Installed: 0.22.0~
Candidate: 0.22.0~
Version table:
*** 0.22.0~
500 http://
100 /var/lib/
ProblemType: Crash
Architecture: amd64
CheckboxSubmission: 1d1b2ce607b82c4
CheckboxSystem: edda5d4f616ca79
CrashCounter: 1
Date: Fri Oct 9 21:34:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: mythtv-frontend 0.22.0~
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fe21999835b: mov %r8d,(%rsi,%rax,8)
PC (0x7fe21999835b) ok
source "%r8d" ok
destination "(%rsi,%rax,8)" (0x7fe1ed98cc00) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
?? () from /usr/lib/
sws_scale () from /usr/lib/
myth_sws_
VideoOutputXv:
VideoOutputXv:
Title: mythfrontend.real crashed with SIGSEGV in sws_scale()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2547): Eel-CRITICAL **: eel_preferences
(gnome-
Howdy, and thank you very much for helping to improve Mythbuntu by opening this ticket. Mostly due to a problem with the Ubuntu build process, these reports are currently not helpful to the developers since they have "No symbol table info available." in the stack trace. Since we would need a new bug opened anyway when that issue is resolved, I am closing this bug. Please do not let this action dissuade you from opening more tickets in the future. We hope this crash reporting issue will be fixed soon (perhaps next week).