Me too.
I have just done a clean install with the latest Ubuntu and Mythtv on a
PC with a Nebula PCI card.
I can watch live TV by running mplayer from a terminal, but Mythtv will
not find any channels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I am having a similar problem with the Nebula DigiTV card. The change to
mythtv-backend.conf has not resolved the problem for me. Please also see
this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368215
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
It means that particular build failed. Shouldn't matter though because
it was a 0.23.0 build for Maverick. Maverick shipped with a newer
version (0.23.1). All Mythbuntu supported releases have newer versions
available now anyway, so you might want to try those. I doubt you can
even get that version
When I checked
https://launchpad.net/ubuntu/+source/mythtv/0.23.0+fixes25138-0ubuntu1
it seems this fix is in state "Failed to build". What does is mean?
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are
This bug was fixed in the package mythtv - 0.23.0+fixes25138-0ubuntu1
---
mythtv (0.23.0+fixes25138-0ubuntu1) maverick; urgency=low
[ Mario Limonciello ]
* new upstream checkout (25138)
[ Thomas Mashos ]
* Added missingok for mirobridge log in logrotate (LP: #581283)
* Back
** Branch linked: lp:mythtv/mythtv-fixes
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
The upstart script change has been pushed to autobuilds for 0.23 and
0.24. These should show up in tomorrows builds.
** Changed in: mythbuntu
Status: Triaged => Fix Committed
** Changed in: mythtv (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: mythbuntu
Status: Fix
I've pushed this change to the 0.24 auto-builds. I'm currently looking
at how to add this to the 0.23 autobuild.
** Changed in: mythbuntu
Assignee: (unassigned) => Thomas Mashos (tgm4883)
** Changed in: mythtv (Ubuntu)
Assignee: (unassigned) => Thomas Mashos (tgm4883)
--
myth-backend
** Branch linked: lp:~mythbuntu/mythtv/mythtv-trunk
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I wonder if this bug and
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/486264 are
related.
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Same problem here with a Hauppauge HVR-1110 - mythbackend is too fast
for udev and adding the dependency solved this problem.
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Just confirming that I also have this problem and that this fix solved it. The
line for me is now:
start on (local-filesystems and net-device-up IFACE=lo and started udev-finish)
Mythtv-frontend now starts before the backend is ready, but this is fine
as the frontend automatically keeps retrying
I'm running 10.04 with the recent 0.23 auto-builds and I have a dual
tuner HVR-2200 card.
This combination has the same on boot race condition where the dual
DVB-T tuners are still initialising after the backend has started and
the devices are then missing from the available tuners.
Modifying /et
OK, then we'll just need to do some regression testing to make sure this
isn't inducing another race condition between gdm and mythbackend (that's my
worry now)
On Wed, Apr 21, 2010 at 01:16, Joel Schopp
wrote:
> Just took out the "and started mysql" part and left "and started udev-
> finish" an
Just took out the "and started mysql" part and left "and started udev-
finish" and it seems to run fine.
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does adding just "started udev-finish" appear to work OK for you? The worry
with adding a dependency on mysql is that not all mythtv installs with a
backend will have mysql available.
On Wed, Apr 21, 2010 at 00:46, Joel Schopp
wrote:
> adding "and started mysql and started udev-finish" to /etc/
adding "and started mysql and started udev-finish" to /etc/init/mythtv-
backend.conf worked for me too. It seems like the right fix. So who
has the ability to roll it out?
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
You received this bug notifica
** Also affects: mythtv (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mythtv (Ubuntu)
Importance: Undecided => High
** Changed in: mythtv (Ubuntu)
Status: New => Triaged
--
myth-backend started before kernel driver it needs
https://bugs.launchpad.net/bugs/556204
18 matches
Mail list logo
