mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()

Bug #1016173 reported by J
38
This bug affects 7 people
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.0+fixes.20120427.58fd2a5-0ubuntu0mythbuntu3
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythcommflag.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
CrashCounter: 1
CrashDB: mythbuntu
Date: Thu Jun 21 17:40:54 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5a1e8a7325 <_ZNK14QFactoryLoader8instanceERK7QString+37>: mov 0x88(%r12),%rdx
 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::instance(QString const&) const () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QImageReader::read(QImage*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QImageReader::read() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()
UpgradeStatus: Upgraded to precise on 2012-04-29 (53 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video

Revision history for this message
J (jpheyes) wrote :
Revision history for this message
Garry Leach (garry-leach) wrote :

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.

Revision history for this message
Jim McEvoy (jemcevoy) wrote :

I had just run the update manger today 03-Jun-2013 which updated the kernel and several other packages, rebooted the system when the update completed, after the reboot to the new kernel I rebuilt the Ceton drivers (I have a Ceton Infini4 PCI card) for the new kernel and rebooted again. The frontend crashed as it was coming up after the second reboot. I had a HD recording scheduled to start while the system was being updated. The recording started a couple minutes late and the fronend restarted and worked also...

Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Expired
Revision history for this message
Garry Leach (garry-leach) wrote : Re: [Bug 1016173] Re: mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()

Hi Thomas,

Thanks for the courtesy note.

I am now on ver 2.0.27.3, so I expect that it is not a problem. I don'
actually know, because I have not used any "domestically recoded dvd"
for a long time.

I do have 2 frustrations, & as far as I can determine, these have not
been addressed:

1. I am using an SSD to run mythbuntu for my standalone frontend. It
starts mythfrontend before the network is connected, so myth switches
into the "new install mode".

I know how to manually get mythfrontend working, but my dear wife has
not been able to remember my instructions on the fairly rare occasion
that I am not available.

It seems that what I would need is a way to make a delay for the start
of mythfrontend (until after the network is connected). However, that
is not a competence which I have.

2. I have many songs, in MP3 format, copied from CDs into the music
folder identified to mythbackend. Although I can play these songs
externally to Myth, Myth says that it does not have the decoder for this
format. However, the page on http://www.mythtv.org/detail/mythmusic
indicates that MP3 files can be played.

What should I be doing to fix this?

You may think that I am a bit lazy about following this up formally.
However, I am nearly 77 years old now, & after the various changes that
have been made to the problem reporting system, I now get a bit lost...

Cheers, Garry.

On Sat, 2015-01-10 at 17:53 +0000, Thomas Mashos wrote:
> We really do appreciate you opening this ticket to help improve
> Mythbuntu, but it needs to be closed for a number of reasons. The
> biggest one is that upstream has moved on to a new version and believes
> this to be fixed. Could you please verify if this issue still exists in
> the latest version?
>
> Please do not let the closing of this ticket dissuade you from opening a
> new ticket if this (or any other) problem occurs with the newer
> versions.
>
> ** Changed in: mythbuntu
> Status: New => Expired
>

Revision history for this message
Thomas Mashos (tgm4883) wrote : Re: [Mythbuntu-bugs] [Bug 1016173] Re: mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()
Download full text (5.3 KiB)

For #1, you could add a "sleep 5" into /usr/bin/mythfrontend (probably
around line 17). That will cause it to wait an additional 5 seconds
before starting the frontend. There are more elegant solutions you
could do, but that would be the easiest.

For #2, is the backend and frontend on the same machine? Because
mythmusic doesn't use storage groups, so the files would have to be on
the frontend to be played back.

On Sat, Jan 10, 2015 at 11:55 PM, Garry Leach
<email address hidden> wrote:
> Hi Thomas,
>
> Thanks for the courtesy note.
>
> I am now on ver 2.0.27.3, so I expect that it is not a problem. I don'
> actually know, because I have not used any "domestically recoded dvd"
> for a long time.
>
> I do have 2 frustrations, & as far as I can determine, these have not
> been addressed:
>
> 1. I am using an SSD to run mythbuntu for my standalone frontend. It
> starts mythfrontend before the network is connected, so myth switches
> into the "new install mode".
>
> I know how to manually get mythfrontend working, but my dear wife has
> not been able to remember my instructions on the fairly rare occasion
> that I am not available.
>
> It seems that what I would need is a way to make a delay for the start
> of mythfrontend (until after the network is connected). However, that
> is not a competence which I have.
>
> 2. I have many songs, in MP3 format, copied from CDs into the music
> folder identified to mythbackend. Although I can play these songs
> externally to Myth, Myth says that it does not have the decoder for this
> format. However, the page on http://www.mythtv.org/detail/mythmusic
> indicates that MP3 files can be played.
>
> What should I be doing to fix this?
>
> You may think that I am a bit lazy about following this up formally.
> However, I am nearly 77 years old now, & after the various changes that
> have been made to the problem reporting system, I now get a bit lost...
>
> Cheers, Garry.
>
> On Sat, 2015-01-10 at 17:53 +0000, Thomas Mashos wrote:
>> We really do appreciate you opening this ticket to help improve
>> Mythbuntu, but it needs to be closed for a number of reasons. The
>> biggest one is that upstream has moved on to a new version and believes
>> this to be fixed. Could you please verify if this issue still exists in
>> the latest version?
>>
>> Please do not let the closing of this ticket dissuade you from opening a
>> new ticket if this (or any other) problem occurs with the newer
>> versions.
>>
>> ** Changed in: mythbuntu
>> Status: New => Expired
>>
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
> https://bugs.launchpad.net/bugs/1016173
>
> Title:
> mythfrontend.real crashed with SIGSEGV in QFactoryLoader::instance()
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> Expired
>
> Bug description:
> Opening domestically recoded dvd
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: mythtv-frontend 2:0.25.0+fixes.20120427.58fd2a5-0ubuntu0mythbuntu3
> ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
> Uname: Linux 3.2.0-25-generic x86_64
> .var.log.mythtv.mythavtest....

Read more...

Revision history for this message
Garry Leach (garry-leach) wrote :

Hi Thomas,

Thank you for this response.

I implemented the 5 seconds sleep & that worked fine, although with no
time to spare... I will keep watch on that & increase the time if it
does not always work. I wish that I had known it could be that easy &
well within my abilities...

I have 2 backend machines (each with 2 tuners & 2 recording HDDs) & 1
separate, specific Mythbuntu machine. I also have Myth on my desktop
Ubuntu machine, mainly if I need to check anything.

I don't run the backends 24/7; I have used the BIOS timer to start them
around 17:00 & a cron-tab to stop them around 01:00. We start the
frontend when we need it. I have tried several times to implement the
wake-up feature, but without success.

I stored the music on the slave BE. There were 13 directories created
(automatically?) under /mnt/mythTV3/mythtv/, including 1 for music, so
that seemed like the right place to put it. This HDD (directory) is
recorded in the default storage group, as it also includes TV
recordings.

The 1000 songs have been recorded into 36 folders, one for each
artist/group.

In addition, I have entered /mnt/mythTV3/mythtv/music/ into the field
"Directory to hold music" in the FE Setup->Media Settings->Music
Settings->General Settings.

So I can see the songs, but can't get them to play. Actually I just
noticed that I can't see them all; it seems to be stuck on one artist,
who has about 15 songs...

For playing the music, could there be a question of permissions, & if
so, who should that be?

Going back to your comment about the FE. If I was to copy these music
folders onto the FE HDD, & describe that location to music settings,
they should play?

I live in Melbourne, Australia. I have been retired for 12 year. I
have been using Ubuntu for 8 years & Mythbuntu for 5 or 6 years. For
the past 3 or 4 years, I have been doing 1 day/week volunteer work at a
not-for-profit computer recycling depot (Computerbank Victoria), where
we rebuild any re-usable computers for sale to needy people. All of
these computers have Ubuntu installed.

Thanks for any help.

Cheers, Garry.

On Sun, 2015-01-11 at 21:27 +0000, Thomas Mashos wrote:
> For #1, you could add a "sleep 5" into /usr/bin/mythfrontend (probably
> around line 17). That will cause it to wait an additional 5 seconds
> before starting the frontend. There are more elegant solutions you
> could do, but that would be the easiest.
>
> For #2, is the backend and frontend on the same machine? Because
> mythmusic doesn't use storage groups, so the files would have to be on
> the frontend to be played back.
>

Revision history for this message
Garry Leach (garry-leach) wrote :

Hi Thomas,

I just copied a few songs to my FE & changed the setting to point to
that directory (/home/garry/music/). However, the play music section
still shows the same music folder/files as before. This seems to be
quite weird, so I will need to dig a bit deeper.

I am tired now, & have a headache from too much work on the computer, so
it will have to wait until tomorrow.

Cheers, Garry.
>
> For #2, is the backend and frontend on the same machine? Because
> mythmusic doesn't use storage groups, so the files would have to be on
> the frontend to be played back.

Revision history for this message
Garry Leach (garry-leach) wrote :

Hi Thomas,

You can disregard my comments.

The directory that I copied the songs to is /home/garry/Music/, so the
FE was not finding them. Oddly, the folder on the BE was with a lower
case "m".

Songs do play now, once I changed the spelling.

Cheers, Garry.

On Mon, 2015-01-12 at 18:46 +1100, Garry Leach wrote:
> Hi Thomas,
>
> I just copied a few songs to my FE & changed the setting to point to
> that directory (/home/garry/music/). However, the play music section
> still shows the same music folder/files as before. This seems to be
> quite weird, so I will need to dig a bit deeper.
>
> I am tired now, & have a headache from too much work on the computer, so
> it will have to wait until tomorrow.
>
> Cheers, Garry.
> >
> > For #2, is the backend and frontend on the same machine? Because
> > mythmusic doesn't use storage groups, so the files would have to be on
> > the frontend to be played back.
>

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.