mythfrontend.real crashed with SIGSEGV in QApplication::notify()

Bug #385686 reported by Stefan Pappalardo
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Invalid
Undecided
Unassigned
mythtv (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: mythtv

Description: Ubuntu 9.04
Release: 9.04
mythtv-frontend:
  Installiert: 0.21.0+fixes19961-0ubuntu8
  Kandidat: 0.21.0+fixes19961-0ubuntu8
  Versions-Tabelle:
 *** 0.21.0+fixes19961-0ubuntu8 0
        500 http://de.archive.ubuntu.com jaunty/multiverse Packages
        100 /var/lib/dpkg/status

In the moment switching from one channel to another livetv freezes and don't react to the remote-control anymore. After a few seconds the mythtv-frontend crashes.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/mythfrontend.real
NonfreeKernelModules: nvidia
Package: mythtv-frontend 0.21.0+fixes19961-0ubuntu8 [modified: usr/share/mythtv/main_settings.xml usr/share/mythtv/util_menu.xml]
ProcCmdline: /usr/bin/mythfrontend.real --logfile /var/log/mythtv/mythfrontend.log
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 QApplication::notify () from /usr/lib/libqt-mt.so.3
 QEventLoop::activateTimers ()
 QEventLoop::processEvents ()
 QEventLoop::processEvents ()
 TV::StartTV (tvrec=0x0, startInGuide=false,
Title: mythfrontend.real crashed with SIGSEGV in QApplication::notify()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv plugdev video

Revision history for this message
Stefan Pappalardo (sjuk) wrote :
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu! The mythtv developers upstream have stopped focusing on 0.21 based reports in preparation for a 0.22 release later this year. If you are able and do not mind trying out an alpha version of software, can you please try to see if this bug is reproducible on 0.22? If it is, we can try to forward this bug upstream to get the right eyes focused on it.

We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at http://mythbuntu.org/auto-builds to enable them.

WARNING: If you intend to revert back to 0.21 after testing, you will need to back up your database before upgrading.

    Thanks!

Changed in mythtv (Ubuntu):
status: New → Incomplete
Changed in mythbuntu:
status: New → Invalid
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, 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 the MythTV developers have turned their efforts to the next version (0.22) and beyond and are no longer fixing bugs on 0.21.

The Mythbuntu team has builds of MythTV 0.22 available on a PPA if you are interested in upgrading. Please follow the directions at
http://mythbuntu.org/auto-builds to enable them. Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with 0.22.

WARNING: If you need to have the ability to revert back to 0.21, you will need to back up your database before upgrading since a 0.22
database can not be downgraded.

   Thanks!

Changed in mythtv (Ubuntu):
status: Incomplete → 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.