[mythtv-users] mythtv setup can't talk to mysql/mariadb

[Mike Bibbings]

On 13/10/2020 10:21, Jim Abernathy wrote:
>
> On 10/13/20 2:24 AM, Stephen Worthington wrote:
>> On Mon, 12 Oct 2020 18:50:15 +0000 (UTC), you wrote:
>>
>>> From: Stephen Worthington <stephen_agent at jsw.gen.nz>
>>>
>>>> I have to say I am surprised at all the troubles you have been having
>>>> with Ubuntu 20.04.  I installed Ubuntu 20.04 in a VirtualBox virtual
>>>> machine using network tuners when it first came out and it worked fine
>>> Mine was an upgrade from 18.04...that sounds like you installed onto 
>>> 20.04 directly?
>> Yes, it was a new install of 20.04.  I am just at the point of wanting
>> to do my 18.04 to 20.04 upgrades now that the LTS to LTS upgrade path
>> is finally available.  I have four systems to upgrade, so I am hoping
>> not to meet too many problems along the way as three of those are
>> operating 24/7 and only have a few hours available on any day to do an
>> upgrade.
>
> FWIW, I did a fresh install of Ubuntu 20.04.1 LTS yesterday on an old 
> PC with Nvidia GT1030 and it failed to even install.
>
> I hit a know bug about selecting 3rd party video drivers on 
> installation. So I did it again without that checkbox and it installed.
>
> Then I sudo apt upgrade && sudo apt upgrade -y. Then I installed 
> ubuntu-restricrted-extras package ans updated all the software again.
>
> At this point mythtv installed fine, but I did NOT install mariadb. 
> Just use the default mysql.
>
> Jim A
>

I just did an in-place upgrade of Xubuntu 18.04 to Xubuntu 20.04 and it 
trashed mysql 5.7 and partially installed mariadb.

Tried reinstalling mysql 8 but this failed (ended up in FROZEN state), 
so I did a clean install of Xubuntu 20.04 and restored mythconverg 
database from backup after using ppa:mythbuntu/32 
v32.0~master.202010141347.b3d42cff22~ubuntu20.04.1) to setup mythtv 
mythweb and mythplugings. Only issue so far is failure to download 
Steppes theme :

2020-10-15 18:40:10.921500 I [6867/6894] ScreenLoad 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject: Cannot create 
children for a parent that is in a different thread.
(Parent is MythScreenStack(0x555be4006440), parent's thread is 
QThread(0x555be3594020), current thread is QThread(0x555be40e8e60)
2020-10-15 18:43:04.656497 I [6867/6867] CoreContext 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject::startTimer: 
Timers can only be used with threads started with QThread
2020-10-15 18:43:05.206264 I [6867/6867] CoreContext 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject::killTimer: 
Timers cannot be stopped from another thread
2020-10-15 18:43:07.864632 I [6867/6867] CoreContext 
mythmainwindow.cpp:2074 (customEvent) - Updating the frontend idle time 
to: 180 mins
2020-10-15 18:43:13.583252 I [6867/7004] ScreenLoad 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject: Cannot create 
children for a parent that is in a different thread.
(Parent is MythScreenStack(0x555be4006440), parent's thread is 
QThread(0x555be3594020), current thread is QThread(0x7f75fc007250)
2020-10-15 18:43:16.008234 I [6867/6867] CoreContext 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject::startTimer: 
Timers cannot be started from another thread
2020-10-15 18:43:16.748263 I [6867/6867] CoreContext 
mythcommandlineparser.cpp:2647 (operator()) - Qt: QObject::killTimer: 
Timers cannot be stopped from another thread

I was prepared for the in-place upgrade to fail, so the clean operating 
system install was  no real issue.

Mike