mythfrontend.real crashed with SIGSEGV in QMutex::lock()

Bug #962981 reported by jcarlosmiguel@hotmail.com
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MythTV
Unknown
Unknown
mythtv (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Installing new version

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.25.0~master.20120316.53761e2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Fri Mar 23 10:24:14 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120321)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
Title: mythfrontend.real crashed with SIGSEGV in QMutex::lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo video

Revision history for this message
jcarlosmiguel@hotmail.com (jcarlosmiguel) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMutex::lock (this=0x48000022b10d8d90) at thread/qmutex.cpp:150
 QCoreApplication::postEvent (receiver=0x16aad10, event=0x7ffa78016140, priority=0) at kernel/qcoreapplication.cpp:1281
 MythObservable::dispatch (this=0x167d340, event=...) at mythobservable.cpp:86
 MythCoreContext::dispatch (this=0x167d340, event=...) at mythcorecontext.cpp:1191
 Reconnect::run (this=<optimized out>) at backendconnectionmanager.cpp:30

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mythtv (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for taking the time to help improve Mythbuntu by opening this ticket. I've forwarded the important information to the MythTV developers - we'll see what they come up with!

visibility: private → public
Changed in mythtv (Ubuntu):
importance: Medium → High
status: New → Triaged
Revision history for this message
MarcRandolph (mrand) wrote :

jcarlosmiguel, can you describe what you might have been doing when this crash was generated? Was it when the frontend first fired up? Were you moving around the menus? Opening a screen (recordings? videos? schedules?)? Or maybe starting up a video or recording for playback? The log doesn't seem to indicate anything.

Thank you!

Revision history for this message
Stuart Morgan (MythTV) (gbee) wrote :

This was fixed 10 days ago in MythTV's master branch.

Revision history for this message
MarcRandolph (mrand) wrote :

Should be fixed in final 12.04 release. If you want to pick it up sooner, you can enable the mythbuntu-repos (which I highly recommend doing anyway).

Changed in mythtv (Ubuntu):
milestone: none → ubuntu-12.04
status: Triaged → Fix Released
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.