mythfrontend.real crashed with SIGSEGV

Bug #859182 reported by Josh Rosenberg
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mythbuntu
Won't Fix
Undecided
Unassigned

Bug Description

Locked up and then crashed when trying to switch from a recorded show (which was still recording at the time) to live TV.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythtv-frontend 2:0.24.1+fixes.20110921.e16613a-0ubuntu0mythbuntu1
ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashDB: mythbuntu
Date: Sun Sep 25 16:24:04 2011
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Installed_mythtv_dbg: 2:0.24.1+fixes.20110921.e16613a-0ubuntu0mythbuntu1
ProcCmdline: /usr/bin/mythfrontend.real
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xaa500e21: add %al,(%eax)
 PC (0xaa500e21) in non-executable VMA region: 0xaa500000-0xaa5dd000 rw-p None
 source "%al" ok
 destination "(%eax)" (0x09c608df) not located in a known VMA region (needed writable region)!
SegvReason:
 executing writable VMA None
 writing unknown VMA
Signal: 11
SourcePackage: mythtv
Stacktrace:
 #0 0xaa500e21 in ?? ()
 No symbol table info available.
 #1 0xa8653130 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: mythfrontend.real crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
XsessionErrors: (polkit-gnome-authentication-agent-1:1823): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Josh Rosenberg (7-launchpad-desh-info) wrote :
visibility: private → public
Revision history for this message
Thomas Mashos (tgm4883) wrote :

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 believes this to be fixed in the latest version. 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.

Changed in mythbuntu:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.