10.04 Frontend-only install: no logs are output to /var/log/mythtv

Bug #642992 reported by Halle Winkler
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mythbuntu
Fix Released
Undecided
rhpot1991
mythtv (Ubuntu)
Fix Released
Undecided
rhpot1991

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.

Tags: log logging logs
Revision history for this message
Halle Winkler (winkler-politepix) wrote :

In the course of trying to troubleshoot this I saw this exchange in which nearly-identical behavior was described:

http://readlist.com/lists/mythtv.org/mythtv-users/33/165176.html

Revision history for this message
Mario Limonciello (superm1) wrote :

So i would suspect that you can workaround the logging bug by creating /var/log/mythtv owned by user mythtv, group mythtv. (and rwx by both)

Revision history for this message
Halle Winkler (winkler-politepix) wrote :

Confirming that the workaround works and I now have a frontend log, thanks Mario.

Revision history for this message
rhpot1991 (rhpot1991) wrote :

I have a fresh 10.04 frontend only install which does not show this behavior.

Revision history for this message
Gibby (gibby) wrote :

I just did a fresh install of 10.04. There was not /var/log/mythtv prior to launching the frontend. Once I did the upgrade to 0.23.1 to match my backend, there was still no /var/log/mythtv however after I launched and closed the frontend the directory did exist.

rhpot1991 (rhpot1991)
Changed in mythbuntu:
assignee: nobody → rhpot1991 (rhpot1991)
Changed in mythtv (Ubuntu):
assignee: nobody → rhpot1991 (rhpot1991)
Revision history for this message
rhpot1991 (rhpot1991) wrote :

Marking invalid for the ubuntu mythtv packages. After looking into the issue I have found that this issue only affects new Mythbuntu frontend only installs. Adding mythtv-frontend to an existing Mythbuntu or Ubuntu installation does not produce this issue.

Changed in mythbuntu:
status: New → In Progress
Changed in mythtv (Ubuntu):
status: New → Invalid
rhpot1991 (rhpot1991)
Changed in mythbuntu:
status: In Progress → Fix Committed
Revision history for this message
rhpot1991 (rhpot1991) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Thu, 11 Nov 2010 11:51:35 -0600

Changed in mythtv (Ubuntu):
status: Invalid → Fix Released
Thomas Mashos (tgm4883)
Changed in mythbuntu:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.