mythfrontend.real crashed with SIGSEGV in QString()

Bug #636499 reported by Josh Rosenberg
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
MythTV
Fix Released
Unknown
Mythbuntu
Fix Released
Medium
Unassigned

Bug Description

Crash when trying to record a power search. 0.23.1.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythtv-frontend 0.23.1+fixes26231-0ubuntu0+mythbuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashDB: mythbuntu
Date: Sun Sep 12 12:57:58 2010
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Installed_mythplugins-dbg: 0.23.1+fixes26231-0ubuntu0+mythbuntu2
Installed_mythtv-dbg: 0.23.1+fixes26231-0ubuntu0+mythbuntu2
ProcCmdline: /usr/bin/mythfrontend.real --logfile /var/log/mythtv/mythfrontend.log
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8085209 <QString+7>: mov (%eax),%edx
 PC (0x08085209) ok
 source "(%eax)" (0x000000fc) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 QString (this=0xbf9e4e98, other=...)
 MythUITextEdit::GetText (this=0x0)
 PowerSearchPopup::recordClicked (this=0xaa7a0128)
 PowerSearchPopup::qt_metacall (this=0xaa7a0128,
 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
Title: mythfrontend.real crashed with SIGSEGV in QString()
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
XsessionErrors: (polkit-gnome-authentication-agent-1:1543): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Josh Rosenberg (7-launchpad-desh-info) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Thanks for the bug report. All the needed details are here, so I've forwarded this bug upstream.

Changed in mythbuntu:
status: New → Triaged
Changed in mythbuntu:
importance: Undecided → Medium
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Fix Released
Revision history for this message
Mario Limonciello (superm1) wrote :

As this is now fixed in an upstream build that should be included with autobuilds, i'm going to close this bug. Upstream committed it to trunk, so if you'd like to see it in -fixes, you can discuss with them backporting it.

Changed in mythbuntu:
status: Triaged → Fix Released
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.