mythbackend crashed with SIGSEGV in QString::QString()

Bug #324311 reported by Aiden83
6
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mythtv

While using the mythtv-frontend, the front-end froze and the crash was detected by apport.

I have not been able to watch tv yet with the front-end, I am still configuring.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/mythbackend
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.21.0+fixes18722-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/mythbackend.pid
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 QString::QString () from /usr/lib/libqt-mt.so.3
 TVRec::StartRecording ()
 ?? ()
 ?? ()
 ?? ()
Title: mythbackend crashed with SIGSEGV in QString::QString()
Uname: Linux 2.6.27-11-generic x86_64
UserGroups: audio cdrom dialout video

Tags: apport-crash
Revision history for this message
Aiden83 (aidendeem) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:TVRec::StartRecording (this=0x11f2b80,
EncoderLink::StartRecording (this=0x1212620,
Scheduler::RunScheduler (this=0x121f8e0)
Scheduler::SchedulerThread (param=0x121f8e0)
start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in mythtv:
importance: Undecided → Medium
visibility: private → public
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu by reporting this issue. I am closing this ticket for a combination of reasons:

1. It is missing symbol information needed to help debug the issue
2. There are no other reports of this issue
3. This ticket is quite old and the mythtv developers upstream have stopped focusing on 0.21 based reports
4. This would need to be reproduced on 0.22 with a new stack trace

If you can reproduce this on 0.22, please attach traces to a new ticket and 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 again!

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