mythfilldatabase crashed with SIGSEGV in QMutex::lock()

Bug #183683 reported by darthanubis
28
Affects Status Importance Assigned to Milestone
MythTV
Won't Fix
Unknown
mythtv (Ubuntu)
Won't Fix
Undecided
David Morris

Bug Description

Binary package hint: mythtv

Have no idea. Came home, and there it was, bug.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Jan 16 20:41:04 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/mythfilldatabase
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.20.2+fixes15096-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/bin/mythfilldatabase
ProcCwd: /
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 QMutex::lock () from /usr/lib/libqt-mt.so.3
 MythContext::ClearSettingsCache ()
 MythContext::readyRead ()
 MythSocket::readyReadThread ()
Title: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
Uname: Linux amd 2.6.24-3-server #1 SMP Thu Jan 3 23:20:57 UTC 2008 x86_64 GNU/Linux
UserGroups: audio cdrom dialout video

Revision history for this message
darthanubis (darthanubis) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
QMutex::lock (this=0x6931b8) at tools/qmutex_unix.cpp:464
MythContext::ClearSettingsCache (this=0x690ae0, myKey=@0x40803c70, newVal=@0x40803c60)
MythContext::readyRead (this=0x690ae0, sock=<value optimized out>) at mythcontext.cpp:2471
MythSocket::readyReadThread () at mythsocket.cpp:778

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in mythtv:
assignee: nobody → dave-greenacre
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Won't Fix
Changed in mythtv:
status: New → Won't Fix
Revision history for this message
Scott Wegner (swegner) wrote :

I got an Apport error message with this error after upgrading to Hardy alpha. I'm running on x64 machine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.