← Back to team overview

linux-traipu team mailing list archive

[Bug 1097868] Re: After upgrade, recordings table is corrupted and new recordings are not working

 

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 UBUNTU -
AL - BR, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1097868

Title:
  After upgrade, recordings table is corrupted and new recordings are
  not working

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Expired

Bug description:
  I just updated my mythbuntu and after the last update mythtv is unable
  to record scheduled recordings anymore.

  The symptom is that in the "Watch Recordings", there are 2 entries for
  each program that are grayed out.

  For example, I have Sesame Street set to record each day and only keep
  2 recordings maximum for my girls. Today, when this attempted to
  record the 10AM showing, I ended up with two entries in the
  mythfrondend. Both show "Sesame Street - Elmo and Zoe's Hat Contest"
  on Jan 9 10:00 AM. Both are grayed out with the X by the title.

  Logging into the mysql database, I ran this query:
  select * from recorded where subtitle like 'Elmo and Zoe%';

  Please see the attached "recordings.sql" file for the two results.

  In that table, the basename column value for the two records is
  1121_20130109100001.mpg and 1121_20130109100000.mpg

  Looking at my /var/lib/mythtv/recordings, I see what it should be:
  $ ls -lh /var/lib/mythtv/recordings/1121_20130109*
  -rw-r--r-- 1 mythtv mythtv 1.4G Jan  9 09:05 /var/lib/mythtv/recordings/1121_20130109083000.mpg
  -rw-rw-rw- 1 mythtv mythtv 8.1K Jan  9 10:00 /var/lib/mythtv/recordings/1121_20130109083000.mpg.-1.100x75.png
  -rw-rw-rw- 1 mythtv mythtv  71K Jan  9 09:05 /var/lib/mythtv/recordings/1121_20130109083000.mpg.png
  -rw-r--r-- 1 mythtv mythtv 1.4G Jan  9 09:35 /var/lib/mythtv/recordings/1121_20130109090000.mpg
  -rw-rw-rw- 1 mythtv mythtv  13K Jan  9 10:00 /var/lib/mythtv/recordings/1121_20130109090000.mpg.-1.100x75.png
  -rw-rw-rw- 1 mythtv mythtv 101K Jan  9 09:35 /var/lib/mythtv/recordings/1121_20130109090000.mpg.png

  So, for some reason, it seems, that the record in the database is
  using 2013-01-09 @10 but the file is being save with @9.

  I'm thinking that I may have to delete my whole database and re-
  configure mythtv.

  Since I can't record programs and view them using mythfrontend
  anymore, this is a major issue for me. I've never had a problem like
  this with mythtv in the 4 or so years I have been using it. Any help
  would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: mythtv-backend 2:0.25.3+fixes.20130104.010e576-0ubuntu0mythbuntu3 [origin: LP-PPA-mythbuntu-0.25]
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  .var.log.mythtv.mythavtest.log:
   
  .var.log.mythtv.mythccextractor.log:
   
  .var.log.mythtv.mythjobqueue.log:
   
  .var.log.mythtv.mythlcdserver.log:
   
  .var.log.mythtv.mythmediaserver.log:
   
  .var.log.mythtv.mythshutdown.log:
   
  .var.log.mythtv.mythtranscode.log:
   
  .var.log.mythtv.mythutil.log:
   
  .var.log.mythtv.mythwelcome.log:
   
  ApportVersion: 2.0.1-0ubuntu15.1
  Architecture: amd64
  CrashDB: mythbuntu
  Date: Wed Jan  9 11:00:23 2013
  InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release amd64 (20120818.1)
  Installed_mythtv_dbg: 0.0
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mythtv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1097868/+subscriptions


References