mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mythbuntu |
Expired
|
Undecided
|
Unassigned |
Bug Description
Opening domestically recoded dvd
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.25.
ProcVersionSign
Uname: Linux 3.2.0-25-generic x86_64
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
.var.log.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
CrashCounter: 1
CrashDB: mythbuntu
Date: Thu Jun 21 17:40:54 2012
ExecutablePath: /usr/bin/
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f5a1e8a7325 <_ZNK14QFactory
PC (0x7f5a1e8a7325) ok
source "0x88(%r12)" (0x00000088) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
QFactoryLoader
?? () from /usr/lib/
?? () from /usr/lib/
QImageReader:
QImageReader:
Title: mythfrontend.real crashed with SIGSEGV in QFactoryLoader:
UpgradeStatus: Upgraded to precise on 2012-04-29 (53 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
I have been using Mythbuntu 12.04 for about 6 weeks. (I have been using various versions for the past 4 years).
I am an end-user, with some limited experience inusing a terminal.
My FE crashes in multiple situations. So I am not sure whether this bug (1016173) is the right one.
I usually don't report the following type because it happens every time I start my HTPC.
For some reason mysql does not start, so the BE & FE just sit there without displaying any menus. I use System Monitor to confirm this. When I manually start mysql, after a little while, the FE starts up. Some or all of the time, it has not started successfully, so it displays a crash notice, but then tries to restart the FE, usually successfully.
So, I don't knpow whether the crash report relates to the failure to start, because mysql is not available, or something else.
Wen Myth fails, I usually close things down & restart them.
Regards,l Garry.