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?
Plea
As mentioned earlier, I have tried to run the database repair, but the
problem comes back. Mythweb shows all the tables as OK. The problem
seems to be alleviated if I run the backend setup and just go through
the menus for the tuners (but actually change nothing, just
next>next>next>finish type of
Note that this issue started when I upgraded from an older Mythbuntu
(forget what I upgraded from, but it was at least a year old, 11.04) to
Mythubuntu 12.04.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launc
This doesn't sound like it's related to packaging, as database upgrades
only happen when upgrading a major version (eg. 0.25 -> 0.26). Minor
upgrades don't change the database so there isn't anything to update. This
sounds like another issue to me (perhaps hardware).
Have you run a check on the da
It was just the latest mythtv updates for mythbuntu 0.25.
New version: 2:0.25.3+fixes.20130202.1d4d50b-0ubuntu0mythbuntu2
Old version:2:0.25.3+fixes.20130127.79a24c9-0ubuntu0mythbuntu2
I doubt it is a problem with that upgrade though as I've experienced
this issue several times now. I think that
What did you upgrade from/to?
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, 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 Myth
The problem happened again. It seems to come back after upgrading mythtv
packages & rebooting the server (frontend and backend are on the same
computer).
This is a big problem as we are losing a lot of programs I have set up
to record. Any ideas?
--
You received this bug notification because you
Update:
So due to the error above and I realized that liveTV was also failing, I
thought it may be corrupted database entries for the tuner. I deleted
both of my HDHomeRun tuners in the backend setup and re-added them.
The problem has gone away. Not only that, I used to have problems seeing
4 tun
** Attachment added: "Updated mythbackend.log"
https://bugs.launchpad.net/mythbuntu/+bug/1097868/+attachment/3488321/+files/mythbackend.log
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1
I'm attaching my mythbackend.log again.
The symptom is duplicate entries in the mythfrontend for a recording,
both of which are grayed out with an X next to them. Looking at the
/var/lib/mythtv/recordings folder, I can confirm that there are no files
for those recordings.
If you open the attached
The problem happened again on two different days. It is not 100% of the
time, but what is odd is that it is always happening with the same two
programs so far.
** Changed in: mythbuntu
Status: Invalid => New
--
You received this bug notification because you are a member of Mythbuntu
Bug T
Okay, the problem is gone. I repaired the tables, I opened and then re-
saved each of the recording schedules that I have in mythweb and it all
seems to be okay. I'm not sure what action fixed it, but I'm good for
now. Hopefully it does not rear its head again.
** Changed in: mythbuntu
Stat
I just saw that some of the mornings recordings worked, but not all.
Two addition kids programs recorded fine:
"The Cat in the Hat Knows a Lot About That!" episode "Inside Out; Hear Here"
"Super Why!" episode "Bedtime for Bear"
Is there something that would cause only some of the new recordings
I re-ran the repair again today, and also some repair options from
inside of mythweb that I could find. I just tried to schedule a program
2 minutes before the start time, and so far it seems to be working.
I'll wait for my next scheduled recording (news in 4 hours) and see if
that works. I'll upd
Yes, I believe I performed a reboot as I upgraded the kernel as the same
time as the mythtv packages were updated. The apt task was complete
though. Are you suggesting that the upgrade was making changes to the
database in the background that extend past the synchronous application
of the upgrade d
Did you reboot immediately after upgrading? Perhaps the upgrade wasn't
complete yet. You shouldn't need to start from scratch, MythTV should
have made a database backup before attempting the upgrade, so you should
be able to restore that then do the upgrade again.
--
You received this bug notific
16 matches
Mail list logo
