mythfrontend.real crashed with SIGSEGV in operator!=()

Bug #998348 reported by JanCeuleers
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

Crash while attempting to change channels in livetv

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: mythtv-frontend 2:0.24.2+fixes.20120409.e9a0ecb-0ubuntu0mythbuntu3
ProcVersionSignature: Ubuntu 2.6.38-15.59-generic 2.6.38.8
Uname: Linux 2.6.38-15-generic x86_64
Architecture: amd64
CrashCounter: 1
CrashDB: mythbuntu
Date: Sat May 12 09:11:26 2012
ExecutablePath: /usr/bin/mythfrontend.real
Installed_mythtv_dbg: 2:0.24.2+fixes.20120409.e9a0ecb-0ubuntu0mythbuntu3
ProcCmdline: /usr/bin/mythfrontend.real --logfile /var/log/mythtv/mythfrontend.log
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f850cd6f949 <QReadWriteLock::lockForRead()+265>: mov 0x10(%rax),%eax
 PC (0x7f850cd6f949) ok
 source "0x10(%rax)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 operator!= (this=0x1426358) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:75
 detach (this=0x1426358) at ../../include/QtCore/../../src/corelib/tools/qhash.h:299
 find (this=0x1426358) at ../../include/QtCore/../../src/corelib/tools/qhash.h:865
 QReadWriteLock::lockForRead (this=0x1426358) at thread/qreadwritelock.cpp:155
 TV::GetPlayerReadLock (this=0x1426140, which=-1, file=0x5e3d5b "guidegrid.cpp", location=1482) at tv_play.cpp:11902
Title: mythfrontend.real crashed with SIGSEGV in operator!=()
UpgradeStatus: Upgraded to natty on 2012-03-18 (54 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin mythtv plugdev sambashare

Revision history for this message
JanCeuleers (jan-ceuleers) 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 has moved on to a new version and believes this to be fixed. 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 → Expired
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.