Hey all -
I was getting pretty frustrated, so I rolled up my sleeves. What did I learn? Trust your gut. My hunch was that simply the database connection was timing out. IT WAS.
From Synaptic I installed libgmyth0-dev (and all the dependencies it wanted), then I went to sourceforge, and downloaded the source code for gmyth. I waded through the code trying to find a #define for the timeout value. I couldn't seem to find it, so went with a little brute force, and in gmyth_query_connect_with_timeout (gmyth/gmyth_query.c) I overrode the "guint timeout" parameter by setting a higher timeout (30 seconds instead of somewhere in the world where I thought I saw a default of 10).
I rebuilt gmyth with "./configure --enable-debug --prefix=/usr" and while it initially still wasn't working, that was because I was getting "access denied" DB errors (as it turns out, in all my mucking with the gconf-editor settings, I set the wrong password. I can now officially confirm that YES, it's looking for the DATABASE user name and password, found in your "general settings" from your mythtv frontend).
gmyth_query_connect_with_timeout(GMythQuery * gmyth_query,
GMythBackendInfo * backend_info,
timeout = 30;
I guess at least MY solution to the connection timeout error is to increase the timeout. (1) is it possible to make the default timeout longer? (2) is it possible to add another gconf-editor option to allow a user to specify the db timeout?
Is this outside of the realm of these developers? I'm lost at where to go next with this info, so I'm hoping someone else in the forum can take it from here or provide me with the know-how to move this forward.