mythfrontend.real crashed with SIGSEGV in QCoreApplication::postEvent()

Bug #718166 reported by MarcRandolph
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
MythTV
Unknown
Unknown
Mythbuntu
Fix Released
Medium
Unassigned

Bug Description

Just trying to exit the frontend after being unsuccessful at tuning to any recorders.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythtv-frontend 2:0.24.0+fixes.20110212.0ddc3f2-0ubuntu0mythbuntu1
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
CrashDB: mythbuntu
Date: Sun Feb 13 07:20:32 2011
ExecutablePath: /usr/bin/mythfrontend.real
Installed_mythtv_dbg: 2:0.24.0+fixes.20110212.0ddc3f2-0ubuntu0mythbuntu1
ProcCmdline: /usr/bin/mythfrontend.real --logfile /var/log/mythtv/mythfrontend.log
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x75e761b <_ZN16QCoreApplication9postEventEP7QObjectP6QEventi+43>: mov 0x24(%eax),%esi
 PC (0x075e761b) ok
 source "0x24(%eax)" (0x00000024) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 QCoreApplication::postEvent(QObject*, QEvent*, int) ()
 QCoreApplication::postEvent(QObject*, QEvent*) ()
 MythObservable::dispatch (this=0x86e8fa0, event=...)
 MythCoreContext::dispatch (this=0x86e8fa0, event=...)
 MythCoreContext::readyRead (this=0x86e8fa0, sock=0x8768d80)
Title: mythfrontend.real crashed with SIGSEGV in QCoreApplication::postEvent()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video

Revision history for this message
MarcRandolph (mrand) wrote :
MarcRandolph (mrand)
tags: removed: need-i386-retrace
visibility: private → public
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Unknown
MarcRandolph (mrand)
Changed in mythbuntu:
importance: Undecided → Medium
status: New → Triaged
Changed in mythtv:
status: Unknown → Confirmed
Changed in mythtv:
status: Confirmed → Unknown
Revision history for this message
MarcRandolph (mrand) wrote :

Looks like this will finally be fixed when 0.25 gets released someday.

Changed in mythbuntu:
status: Triaged → Fix Committed
Revision history for this message
Thomas Mashos (tgm4883) wrote :

Marking as Fix Released since we provide newer builds in our PPA and this has been marked fix committed for awhile now.

Changed in mythbuntu:
status: Fix Committed → Fix Released
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.