Bug 265808 – media-tv/mythtv-0.21_p19961-r1.ebuild breaks MythTV-Installation

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Oli Henning 2009-04-11 22:27:57 UTC]

After "emerge mythtv" (ebuild-verion mythtv-0.21_p19961-r1"
there are some files in /usr/share/mythtv/ missing, e.g. 
"/usr/share/mythtv/mainmenu.xml" isn't there.

The result is, that mythfrontend logs the error-message
"Couldn't read menu file mainmenu.xml", shows no menu items
in the myth-main-menu and then, when you press cursor-up or down
(in the empty main-menu) you get a Segmentation fault.

When i do a 'normal' ./configure (with appropriate options) & make & make install with the untared mythtv-package then the installation works
perfectly.

In summary, the following files are missing in /usr/share/mythtv/:
 info_menu.xml
 info_settings.xml
 library.xml
 mainmenu.xml
 main_settings.xml
 manage_recordings.xml
 media_settings.xml
 optical_menu.xml
 recpriorities_settings.xml
 tv_lists.xml
 tvmenu.xml
 tv_schedule.xml
 tv_search.xml
 tv_settings.xml
 util_menu.xml

BTW: The error does not occure (when running mythfrontend) if
you choosed another Menu-Theme than "Default" (e.g. "classic"
or "DVR"). In this case, mythfrontend searches it's XML-Files
in the corresponding themes-directory and will find there
some - at least the 'super-main' mainmenu.xml.


Reproducible: Always

Steps to Reproduce:
1. emerge =mythtv-0.21_p19961-r1
2. start mythfrontend
3. look in /usr/share/mythtv/.. there is no mainmenu.xml
4. bunzip and untar mythtv-0.21_p19961.tar.bz2 (from /usr/portage/distfile)
5. cd into untared directory
6. run ./configure (with the options you saw while emerging mythtv
7. make & make install
8. look in /usr/share/mythtv... mainmenu.xml and others are there
9. run mythfrontend
10. be happy :-)

Actual Results:  
mythfrontend not running

Expected Results:  
mythfrontend running

[Comment 1 jkara00 2009-05-23 03:37:54 UTC]

can confirm i am experiencing the identical issue as the OP

[Comment 2 Kirk Richard Holz 2009-05-24 02:51:08 UTC]

I can confirm this exact problem as well.

[Comment 3 Kirk Richard Holz 2009-05-24 02:56:03 UTC]

2009-05-24 10:22:18.179 MythThemedMenuPrivate: Couldn't read menu file mainmenu.xml

It appears that mythfrontend is calling MythThemedMenuPrivate when it should be calling MythThemeMenuPrivate -- a simple typo, possibly?

[Comment 4 James 2009-06-01 01:35:37 UTC]

(In reply to comment #3)
> 2009-05-24 10:22:18.179 MythThemedMenuPrivate: Couldn't read menu file
> mainmenu.xml
> 
> It appears that mythfrontend is calling MythThemedMenuPrivate when it should be
> calling MythThemeMenuPrivate -- a simple typo, possibly?
> 

I was having trouble with this problem, I don't think it has anything to do with MythThemedMenuPrivate/MythThemeMenuPrivate, it just appears that a number of files disappear (if you compare the /usr/share/mythtv directory on a working system to a non-working system, the non-working system will be missing a fair number of files).  I ran into it, not with -r1, but with -r2, I was finally able to overcome it by uninstalling mythtv, as well as the rest of the myth addons, doing a emerge --depclean (I'm not certain the last two steps were necessary), and reinstalling.  

[Comment 5 jkara00 2009-06-01 02:56:34 UTC]

upgrading to the r2 ebuild has resolved this for me without requiring to uninstall the previous versionb or do a depclean

[Comment 6 Kirk Richard Holz 2009-06-01 06:26:42 UTC]

Installing -r2 fixed this problem for me. The only other thing I had done was python-updater, I don't know if that made any difference.

[Comment 7 Doug Goldstein (RETIRED) 2009-08-03 01:27:09 UTC]

update to -r2 fixes the issue.