MythTV Official Community Forum

Hi Bill Thanks for your suggestions. I gave up after 12 hours of effort troubleshooting over 3 days and following several other threads reporting the exact same problem. My configuration being completely fresh had the default user mythtv and default password mythtv and both config.xml files had the ...

Installed fresh Ubuntu 18.04.2 64 and installed MythTv 0.30 via apt-get install having added the required repositories (PPA) & checked via. - apt-cache policy package name and used sudo add-apt-repository ppa:mythbuntu. When I attempted to configure I got caught in the add user name to group MythTv ...

Ah ha, I spoke too soon reporting the return of FPG functionality. About a week after I posted the last message all EPG data stopped showing again for SBS and the Channel 9 channels have come out in sympathy. I checked Live TV to see if viewing the SBS channels might restore the SBS grab but to my g...

Hi
I will capture an image of my current environment 1st and upgrade to 18.04 when I get some free time.
Thanks for your assistance which has been very helpful and most appreciated.

Hello Can upgrade from 0.28 to 30.0 or do I need to do it in two steps? If I upgrade will mythweb then work or do I need to apply a post upgrade remediation? Where do I check the version of Mythweb i have installed and how do I avoid accidentally install an earlier version Mythweb? Mythweb was insta...

Hi Paul

As far as I know I have the latest version of Mythweb. What is the best way of checking? Can you provide specific version numbers you are recommending?

Hi I applied the changes as suggested which restored the showing of Listing and recorded programs in Mythweb however when I tried to schedule a recording and went to commit I got the following: datetime: 2019-02-07 18:08:36 (ACDT) errornum: 256 error type: User Error error string: !!NoTrans: SQL Err...

Hi Wesnewell My location in my profile is correct and does not require alteration The location filed reads South Australia as it has since it was created. There is a separate field for user to set a flag which is Ireland in my case because that is where I am from and remain a citizen of Ireland curr...

Hi Gribnif I checked my etc folder and despite the gedit errors it did complete the file save and the file contains the text you provided. On restarting the Myth server and firefox I still have the same problem. Noticing that many files in the etc folder have extension of .conf rather than cnf so I ...

I tried using sudo gedit /etc/my.cnf and was not allowed to save getting the following: ** (gedit:27002): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported What tool should I use to write thisw line. I note that the my.cnf was empty so was this file c...

Hi I can report that now SBS EPG data is coming through for all SBS channels. Two days after the last configuration attempts the missing SBS EPG came through. I wish i know definitively why it was resolved but I cannot which is a shame in case anyone else has the same problem. I could not understand...

MythWeb Errors Monday, 4 February 2019 4:34 PM Selecting Recording in MythWeb returns: datetime: 2019-02-04 15:47:22 (ACDT) errornum: 256 error type: User Error error string: !!NoTrans: SQL Error: Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'mythconverg.r...

Hello The very first line of this thread advised the location: - "I am using XMLTV EPG grabber in South Australia however I am not getting any SBS channel group EPG showing as unknown." I don't know why I have been referred to the UK? The Kodi Mythtv client can see all the EPG providing me with a wo...

Running the scan channels recovered EPG for channel 31 SBS Viceland HD & 34 SBS food. Still no EPG for Channels 3 SBS One, 30 SBS One HD, 32 SBS Viceland, 34 NITV and 44 Adelaide. I don't know why some SBS EPG has come through and not all. I have made sure I have started all the channels in Live TV ...

OK I used sudo systemctl stop mythtv-backend which worked showing that indeed the backend was not properly stopping. This must be a fresh bug as I have not seen this problem before. I'm still struggling to understand the solution advise I reviewed specifically "then scan existing transport (know the...