mythbuntu-bugs team mailing list archive

[Launchpad Bug Tracker <642992@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mythtv - 1:0.24.0+fixes27162-0ubuntu1

---------------
mythtv (1:0.24.0+fixes27162-0ubuntu1) natty; urgency=low

  [ Mario Limonciello ]
  * Drop 36_setgroups.  Been merged upstream.
  * Add upstart script into the packaging.  It's been dropped upstream.
    ref svn 24280 upstream.
  * Bump version to 0.24 fixes r27162
  * Refresh patches due to upstream changes:
    * Mythfilldatabase logging
    * Force dbus reboot/halt.
    * Default directories.
    * Python 2.6
    * proper shutdown behavior for ubuntu.
  * Drop 40_libudev.  Merged upstream.
  * Drop 09_perl_bindings_prefix.  Merged upstream.
  * debian/rules: cleanup deprecated configure options.
  * Install mythpreviewgen into mythtv-frontend (LP: #616083)
  * Remove faad support, no longer listed in configure, fixes FTBFS.
  * remove circular dependency.
  * Reduce zealousness in files cleaned in clean rule.
  * Remove qmake invocation.
  * Add depends on python-mysqldb
  * Install metadata to /usr/share/mythtv so it can be used by MNV.
    (LP: #624064)
  * Add a --list-missing option to make sure that all packaged files
    get installed, and the build fails otherwise.
  * Correct the missing locales and fonts.
  * Install python and perl directly into their appropriate directories.
  * Remove dummy libmyth-perl package.
  * Modify ubuntu shutdown behavior patch to only use dbus if commands fail.
  * Update shutdown patch for upstream recommendations.
  * Conflicts/Replaces on old libmyth package (LP: #665402)
  * Merge mythtv/mythplugins/myththemes source packages into one.
  * Add a new get-svn-source rule to use with mythbuntu-weekly-build.
  * In the update-control-files rule, update the ABI as well.
  * Conflicts/Replaces for no longer used mythplugins-dbg package.
  * Drop references to mythplugins-dbg in the apport rules.
  * Fix the installation of mythmusic. (LP: #672045)
  * Create a mysql.txt symlink from mythtv-setup as well.

  [ Gerald Barker ]
  * Copy 'internetcontent' scripts to /usr/share/mythtv/ as part of
    mythbackend install so they can be requeted by MythNetvision

  [ Thomas Mashos ]
  * Added missingok for mirobridge log in logrotate (LP: #581283)
  * Updated perl bindings patch for upstream changes (LP: #586293)
  * Added libqt4-webkit-dev dependency to satisify maverick FTBFS
  * Added new python and perl dependencies
  * Moved backup and restore scripts from mythtv-database to mythtv-common
  * Added Replaces for mythtv-common (LP: 622983)

  [ John Baab ]
  * Fixed missing log folder for frontend only install (LP: #642992)
 -- Mario Limonciello <Mario_Limonciello@xxxxxxxx>   Thu, 11 Nov 2010 11:51:35 -0600

** Changed in: mythtv (Ubuntu)
       Status: Invalid => Fix Released

-- 
10.04 Frontend-only install: no logs are output to /var/log/mythtv
https://bugs.launchpad.net/bugs/642992
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in ubuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Fix Committed
Status in “mythtv” package in Ubuntu: Fix Released

Bug description:
After performing a stock install of the current 10.04 distribution of Mythbuntu with a frontend-only configuration, there was no /var/log/mythtv folder created (and consequently no logs ever written to it), after multiple sessions using mythtv and multiple reboots.  Other strange symptoms are that the theme that loads in mythfrontend is the terra theme rather than the Mythbuntu theme, the first menu screen often gets stuck just drawing the background without ever showing any of the menu options and then crashing with a (presumed, since I have no log) segfault after a few minutes, and if it does get past this point and render the menu options, it will crash about 10 minutes later (still no logs to share with what error it crashes).  This bug is intended to be about the lack of logging and not the crashing (I don't want to start trying to troubleshoot the crashing until I have reliable logging) but I wanted to mention the related symptoms for context.  The network connection is reliable and it is up at the time that mythfrontend is starting.

This is on a box with an Intel Atom 410PT mainboard using VGA out.