Hi all, I just wanted to report two issues that I am encountering with my Myth system at the moment. #1 Failure to Start FE after waking the BE I have configured my FE to use wakeonlan to wake the BE if it has shut itself down. As soon as Mythbuntu has loaded I hear a beep from the back room indicating that the BE server has started. I know that if the server doesn't stop to check the HDDs it will be up and running within 2mins and I have set the FE to retry accordingly. The problem is that the FE doesn't automatically start. The first couple of times I tried it the server was already shutting back down before I realised. The next few times I tried I noticed that the FE does actually flash up for less than a second and then crashes. All I have time to see is the progress bar screen (that resizes the GUI) and then I'm back at the desktop. I have tried to google this issue with no luck and my troubleshooting skills need some work (I'm going to try and work through http://www.mythtv.org/wiki/index.php/Troubleshooting:General_Troubleshooting_Tips). If anyone has already encountered this issue tips would be appreciated. If not I will hopefully have some log information for my next post. #2 FE crash from the Program Finder I have noticed on two of my FEs that a certain entry in the Program Finder will cause the FE to crash. The crash occurs once you select the program. Instead of seeing the time/s that it is on the FE crashes and I either see the Mythbuntu desktop or MythWelcome (if using the FE on the BE server). I can repeat this problem reliably by reopening the FE and attempting to select the same program again. The first time it happened about a week or two ago I forgot about it but it happened again this morning. I plan to keep trying until the program in question has expired and hopefully generate some helpful logs (maybe it won't happen again after a reboot? after a mythfilldatabase?). Once again I am going to try and diagnose it myself but if anyone else has noticed this please let me know. Another factor worth noting is that the first occurrence was on the servers FE while this mornings occurrence was from the dedicated FE in my lounge room. I don't know yet if the issue will occur s! imultaneously from both FEs. I opened Mythweb on the dedicated FE this morning and I was able to search for and select the troublesome program with no problem but that was the limit of the testing I could conduct in the limited time I had. As a bandaid solution for both the above issues I am going to try and program a button on my remote to restart the FE client (as per the mythtv howto). These crashes are not helping the wife-friendlyness of the system and I have had to have a mouse plugged in in order to restart the FE. I'll provide more info as soon as I know how, Glen