Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Mythfrontend seg faults

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


lists at murrell

Sep 3, 2009, 10:01 AM

Post #1 of 6 (815 views)
Permalink
Mythfrontend seg faults

Hello.

I have been running Mythbuntu 9.04 for a couple months now, and decided to enable the "weekly builds" repo. After I ran a "dist-upgrade" and installed all the updated packages, I cannot start my frontend. It initially starts up but then crashes. A look at the log indicates that it ends with a segmentation fault. Here is the entry from the "mythfrontend.log" file:

--- START ---
Starting mythfrontend.real..
2009-09-03 09:52:47.587 mythfrontend version: trunk [21644] www.mythtv.org
2009-09-03 09:52:47.588 Using runtime prefix = /usr
2009-09-03 09:52:47.588 Using configuration directory = /home/sysadmin/.mythtv
2009-09-03 09:52:48.285 Empty LocalHostName.
2009-09-03 09:52:48.286 Using localhost value of mythbe01
2009-09-03 09:52:48.297 New DB connection, total: 1
2009-09-03 09:52:48.306 Connected to database 'mythconverg' at host: localhost
2009-09-03 09:52:48.308 Closing DB connection named 'DBManager0'
2009-09-03 09:52:48.324 ScreenSaverX11Private: Gnome screen saver support enabled
2009-09-03 09:52:48.326 DPMS is active.
2009-09-03 09:52:48.329 Primary screen: 0.
2009-09-03 09:52:48.330 Connected to database 'mythconverg' at host: localhost
2009-09-03 09:52:48.332 Using screen 0, 1024x768 at 0,0
2009-09-03 09:52:48.359 MythUI Image Cache size set to 20971520 bytes
2009-09-03 09:52:48.361 Enabled verbose msgs: important general
2009-09-03 09:52:48.488 The theme (defaultmenu) is missing a themeinfo.xml file
2009-09-03 09:52:49.082 The theme (defaultmenu) is missing a themeinfo.xml file
2009-09-03 09:52:49.266 Desktop video mode: 1024x768 75.03 Hz
2009-09-03 09:52:49.420 Primary screen: 0.
2009-09-03 09:52:49.421 Using screen 0, 1024x768 at 0,0
2009-09-03 09:52:49.422 Using theme base resolution of 800x600
2009-09-03 09:52:49.430 LIRC: Successfully initialized '/dev/lircd' using '/home/sysadmin/.mythtv/lircrc' config
2009-09-03 09:52:49.430 JoystickMenuThread Error: Joystick disabled - Failed to read /home/sysadmin/.mythtv/joystickmenurc
2009-09-03 09:52:49.580 Using the Qt painter
2009-09-03 09:52:49.722 Loading base theme from /usr/share/mythtv/themes/G.A.N.T/base.xml
2009-09-03 09:52:50.118 Loading base theme from /usr/share/mythtv/themes/default/base.xml
2009-09-03 09:52:50.142 Current Schema Version: 1244
2009-09-03 09:52:50.203 Registering Internal as a media playback plugin.
2009-09-03 09:52:50.262 MonitorRegisterExtensions(0x100, gif,jpg,png)
2009-09-03 09:52:50.290 Current Schema Version: 1017
2009-09-03 09:52:50.324 MonitorRegisterExtensions(0x40, mp3,mp2,ogg,oga,flac,wma,wav,ac3,oma,omg,atp,ra,dts,aac,m4a,aa3,tta,mka,aiff,swa,wv)
Segmentation fault
--- END ---

I have even blown away all the tables in the database and re-run mythtv-setup, but the issue remains.

I know I run risks when straying from "stable", but just wondering if there is a fix?

Let me know if there is any other info you need. Thanks! :-)

-Alan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


lists at murrell

Sep 3, 2009, 7:33 PM

Post #2 of 6 (750 views)
Permalink
Re: Mythfrontend seg faults [In reply to]

Hi Marc.

Thanks for your reply.

----- "Marc Randolph" <mrand [at] pobox> wrote:

> You might want/need to launch mythfrontend.real directly with
> something like:
> "gdb /usr/bin/mythfrontend.real"
>
> Here is an example of how to use gdb:
> http://www.unknownroad.com/rtfm/gdbtut/gdbsegfault.html

I followed the example and during the running of gdb, it would stop at certain points and I would have to hit <ENTER> to continue. When it started the mythfrontend GUI, it stopped again, but I couldn't get to the terminal window to hit <ENTER> to continue.

I'll try a couple other things, but are there any other suggestions in the meantime?

Thanks! :-)

-Alan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Sep 3, 2009, 9:25 PM

Post #3 of 6 (756 views)
Permalink
Re: Mythfrontend seg faults [In reply to]

On 09/03/2009 10:33 PM, lists [at] murrell wrote:
> ----- "Marc Randolph" wrote:
>> You might want/need to launch mythfrontend.real directly with
>> something like:
>> "gdb /usr/bin/mythfrontend.real"
>>
>> Here is an example of how to use gdb:
>> http://www.unknownroad.com/rtfm/gdbtut/gdbsegfault.html
>>
> I followed the example and during the running of gdb, it would stop at certain points and I would have to hit <ENTER> to continue. When it started the mythfrontend GUI, it stopped again, but I couldn't get to the terminal window to hit <ENTER> to continue.
>
> I'll try a couple other things, but are there any other suggestions in the meantime?
>
> Thanks! :-)
http://www.mythtv.org/wiki/Debugging and
http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2

specifically:

set pagination off

Mike

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


lists at murrell

Sep 3, 2009, 11:31 PM

Post #4 of 6 (752 views)
Permalink
Re: Mythfrontend seg faults [In reply to]

Hi Marc.

----- "Marc Randolph" <mrand [at] pobox> wrote:

> If your segfault is creating a core dump (a file with the word core
> in
> it, usually in the home directory of where a program is executed),
> then you don't need to use "run" on the gdb command line. Instead,
> you can analyze that core file.

I didn't see a core dump, but have found a way to continue. The end of the "run" sequence in gdb ends with this:


"Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb288e730 (LWP 4640)]
0xad7e1724 in QMutexPool::get () from /usr/lib/libqt-mt.so.3"

so it appears to be an issue with QT. Following the rest of that example usage, I did a backtrace, which output the following:

--- START ---
#0 0xad7e1724 in QMutexPool::get () from /usr/lib/libqt-mt.so.3
#1 0xad4ed6ba in QMetaObjectCleanUp::QMetaObjectCleanUp ()
from /usr/lib/libqt-mt.so.3
#2 0xad893679 in ?? () from /usr/lib/libqt-mt.so.3
#3 0xad893add in ?? () from /usr/lib/libqt-mt.so.3
#4 0xad3fbb6c in _init () from /usr/lib/libqt-mt.so.3
#5 0xb7fd0404 in ?? () from /lib/ld-linux.so.2
#6 0xb7fd0534 in ?? () from /lib/ld-linux.so.2
#7 0xb7fd446b in ?? () from /lib/ld-linux.so.2
#8 0xb7fd0036 in ?? () from /lib/ld-linux.so.2
#9 0xb7fd3c1e in ?? () from /lib/ld-linux.so.2
#10 0xb4e7abec in ?? () from /lib/tls/i686/cmov/libdl.so.2
#11 0xb7fd0036 in ?? () from /lib/ld-linux.so.2
#12 0xb4e7b01c in ?? () from /lib/tls/i686/cmov/libdl.so.2
#13 0xb4e7ab21 in dlopen () from /lib/tls/i686/cmov/libdl.so.2
#14 0xb52b91c7 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb52b352c in ?? () from /usr/lib/libQtCore.so.4
#16 0xb52b3758 in QLibrary::resolve () from /usr/lib/libQtCore.so.4
#17 0xb67cf094 in MythPlugin::init () from /usr/lib/libmyth-0.22.so.0
#18 0xb67cf7cf in MythPluginManager::init_plugin ()
from /usr/lib/libmyth-0.22.so.0
#19 0xb67d191d in MythPluginManager::MythPluginManager ()
from /usr/lib/libmyth-0.22.so.0
#20 0x0806e81c in ?? ()
#21 0xb4f0a775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#22 0x080613e1 in ?? ()
--- END ---

I am not sure which "frame" would be the one to follow through with, but that is probably a moot point since it does not appear to be a MythTV issue, but rather a QT one. If you wish to pursue this further, I am willing, but understand that it is probably beyond your scope of support :-)

> I did find someone that is running a combined FE/BE on r21651 today
> with no segfault.

Were they running Mythbuntu 9.04 as well and "upgraded" to weekly builds/trunk?

-Alan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


lists at murrell

Sep 3, 2009, 11:51 PM

Post #5 of 6 (747 views)
Permalink
Re: Mythfrontend seg faults [In reply to]

Problem has been resolved. I used apt-get to remove "mythtv-frontend", "mythtv-theme", and all the mythtv plugin packages. I thne installed only mythtv-frontend package and the frontend starts. I am now going to install the various plugin packages one by one and stop/start the frontend and see if one of them was causing the seg fault. I will post back if I find one fo them causes an issue (in case anyone else runs into this issue), otherwise assume all is good.

Thanks for your feedback!

-Alan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


lists at murrell

Sep 4, 2009, 3:14 PM

Post #6 of 6 (720 views)
Permalink
Re: Mythfrontend seg faults [In reply to]

----- "Marc Randolph" <mrand [at] pobox> wrote:

> Thanks for replying back! Since you didn't post anything further,
> I'm
> guessing that reinstalling those packages made things work.
> Interesting.

Yes, it did indeed work. I installed all the plugins with no obvious issue. I do occasionally get a crash when browsing through my videos, but no issues playing back (yet). I am putting this down to running unstable code, and would expect this to not be an issue when 0.22 is finalized and Mythbuntu upgrades appropriately.

I went with the "trunk" because I wanted the ability to catalog the TV shows I have downloaded with the "ttvdb.py" script that ships with 0.22, so I can live with the occasional crashes :-)

-Alan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.