mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()

Bug #370146 reported by Jaakan Shorter
226
This bug affects 12 people
Affects Status Importance Assigned to Milestone
MythTV
Invalid
Unknown
Mythbuntu
Won't Fix
Medium
Unassigned
mythtv (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: mythtv

Seems to be randomly crashing after I upgraded Ubuntu 8.10.

Description: Ubuntu 9.04
Release: 9.04

mythtv:
  Installed: 0.21.0+fixes19961-0ubuntu8
  Candidate: 0.21.0+fixes19961-0ubuntu8
  Version table:
 *** 0.21.0+fixes19961-0ubuntu8 0
        500 http://archive.ubuntu.com jaunty/multiverse Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/mythfilldatabase
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.21.0+fixes19961-0ubuntu8
ProcCmdline: /usr/bin/mythfilldatabase
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 MythContext::ClearSettingsCache ()
 MythContext::readyRead ()
 readyReadThread_iffound ()
 MythSocket::readyReadThread ()
Title: mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: audio cdrom dialout video

Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
MythContext::ClearSettingsCache (this=0x25a8560,
MythContext::readyRead (this=0x25a8560,
readyReadThread_iffound (sock=0x25e3e50)
MythSocket::readyReadThread () at mythsocket.cpp:908

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in mythtv (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in mythtv:
status: Unknown → New
Revision history for this message
Stefan Pappalardo (sjuk) wrote :

The same for me. I upgraded recently to jaunty too. But the same problem was in intrepid already there.

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

Unfortunately, upstream can't determine a source with the current backtraces. There is a remote chance that the second trace is filesystem related, so please try a fsck (and might as well throw a database clean in there) and if you can still reproduce then install the qt-debugging symbols before submitting a new backtrace.

Changed in mythbuntu:
status: New → Incomplete
Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :

Which Packages do I need to have installed to cover "qt-debugging symbols"?

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

Check https://wiki.ubuntu.com/DebuggingProgramCrash for info on getting debugging symbol packages.

Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to make Mythbuntu better. Unfortunately, mythtv developers upstream have stopped focusing on 0.21 based reports in preparation for a 0.22 release later this year. Is this bug still occurring for you? Could 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
Revision history for this message
MarcRandolph (mrand) wrote :

This same error has been reproduced in with MythTv 0.22 (see bug #428959).

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

Closing this one since 0.21 development tree is closed and this same error has been reproduced in with MythTv 0.22 (see bug #428959).

Changed in mythtv (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
MarcRandolph (mrand) wrote :

Actually, I meant Bug #428238

Changed in mythbuntu:
importance: Undecided → Medium
status: Confirmed → 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.