#5 "The intention for the rule is to start when an interface that isn't lo comes up (be it eth0, wlan0, what not)"
I don't understand this inention. On single machine setup it is sufficient to have myth backend listening on localhost, and this rule breaks such setup with unknown reason. -- You received this bug notification because you are a member of UBUNTU - AL - BR, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/907301 Title: mythtv backend wouldn't start automatically after the latest update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: Mythtv Backend doesn't start on machine boot. The mythtv-backend.conf in /etc/init doesn't trigger, at least on my setup. I think the "start on" conditions are not being met. Latest version: 2:0.24.1+fixes.20111207.40f3bae-0ubuntu0mythbuntu1 Attached is a version that works on my server, with changed "start on" conditions To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/907301/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : [email protected] Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
