Comment 14 for bug 326768

On a fresh install of mythbuntu 9.04 I get this problem. The fix described above does not work for me. (It doesn't change the behavior at all as far as I can tell).

My situation is more complex since I use a HDHomeRun tuner (so I need the network working as well). Here is what I've tried:

1) The default boot has mysql coming up from rc2.d at something low like S10 (I can't remember). Then S31mythbackend, then S50NetworkManager. Fails 80% of the time. I boot to a crippled mythfrontend that has scrambled keymappings and a broken theme. If I kill the frontend, restart the backend, and run frontend it works.

2) Don't auto start mythfrontend or mythbackend. Still use S50NetworkManager to bring the network up. Boot. From the desktop manually start mythbackend, then start mythfrontend. Works every time.

3) Loads of combinations of NetworkManager, manually configuring the network, moving mysql around and mythbackend around in rc2.d. Using my SxxWaitForHDHomeRun script. It's hard to find any combination that works.

I wrote a script that does mysql STATUS queries and prints the uptime. Put it all over rc2.d. The server shows a constantly increasing uptime so I don't think it's getting killed. At S31 it shows 5 sec of uptime. Still, mythbackend can't see it. Some queries work, some fail.

Finally had to: a) manually config the network (to give time for the HDHomeRun to be available on the network), b) move mythbackend to S99zMythbackend so it starts up really late. Now it works 90% of the time but it still fails a query or two from time to time (but then they start working again).

Crazy things going on...