Mailing List Archive

On 06/02/2022 10:40, Klaas de Waal wrote:
> Hi,
>
> I have now on two different systems that the checkbox for "This server
> is the Master Backend" is unexpectedly unchecked. This is with testing
> the fixes/32. It could just be that I did something wrong but if others
> also experience this issue it might be a bug.
>
> Klaas.

I have mythtv-setup problems too, but thought they were caused by
unwanted interaction between boxes intended to be independent. At
present I have switched off the problem box and am wondering if I need a
DB restore. I dislike the full-screen arrogance of the default setup,
and that it finds several servers with no obvious way of knowing which
is which. Fortunately, once set up, it usually works. And I know I'm
supposed to use the 'ten foot interface' model with a single syatem...

Yesterday on a 'buntu laptop (rarely used) I had a small DB backup with
a schema of, iirc, 1307...

Perhaps the fact that my daughter retired at Christmas has something to
do with it.

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com> wrote:

> On 06/02/2022 10:40, Klaas de Waal wrote:
> > Hi,
> >
> > I have now on two different systems that the checkbox for "This server
> > is the Master Backend" is unexpectedly unchecked. This is with testing
> > the fixes/32. It could just be that I did something wrong but if others
> > also experience this issue it might be a bug.
> >
> > Klaas.
>
> I have mythtv-setup problems too, but thought they were caused by
> unwanted interaction between boxes intended to be independent. At
> present I have switched off the problem box and am wondering if I need a
> DB restore. I dislike the full-screen arrogance of the default setup,
> and that it finds several servers with no obvious way of knowing which
> is which. Fortunately, once set up, it usually works. And I know I'm
> supposed to use the 'ten foot interface' model with a single syatem...
>
> My problems did start after trying to test an updated Dutch translation on
my laptop.
It looks like starting mythfrontend with the -p command line option, as
recommended in the Wiki page
https://www.mythtv.org/wiki/Translation#Do_the_translation, is what causes
the problems.
I did expect the "mythfrontend -p" to ask for the language; instead it
comes up with a backend selection page.
There are two backends shown with completely identical descriptions.
Selecting the first one gives a popup box with a prompt for a PIN code.
Entering 0000 fails, the box remains.
Selecting the second one works OK without a PIN code. This happens to be
the production backend in my attic and this is not what I wanted so I just
exited after clicking around for a while.
Now on BOTH systems, my laptop and the one in the attic, the "This server
is the Master Backend" is unchecked.
I have been able to reproduce this once but not twice.

Looks like there are the following issues:

- The "mythfrontend -p" command is expected to ask for country and language
but instead it does something completely different. It could be that the
documentation in https://www.mythtv.org/wiki/Translation#Do_the_translation
is not correct.
- The backend configuration is clobbered by "mythfrontend -p". This should
never happen and is the most serious issue.
- I can NOT start mythfrontend when I select the backend via the backend
selection page; it then asks for a PIN code which is not accepted. I can
however just start mythfrontend without the "-p" option and then it starts
OK. This is inconsistent.
- The two backends presented in the backend selection page have a 100%
identical description. This makes selecting the correct backend a lottery.

I also think that the default for mythtv-setup should be to appear in a
window and not full screen. Typical use for mythtv-setup, at least for me,
to run it via ssh on a computer screen and not on the TV. The annoying
thing is that this can only be changed in mythfrontend.

Klaas.

On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:

>On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com> wrote:
>
>> On 06/02/2022 10:40, Klaas de Waal wrote:
>> > Hi,
>> >
>> > I have now on two different systems that the checkbox for "This server
>> > is the Master Backend" is unexpectedly unchecked. This is with testing
>> > the fixes/32. It could just be that I did something wrong but if others
>> > also experience this issue it might be a bug.
>> >
>> > Klaas.
>>
>> I have mythtv-setup problems too, but thought they were caused by
>> unwanted interaction between boxes intended to be independent. At
>> present I have switched off the problem box and am wondering if I need a
>> DB restore. I dislike the full-screen arrogance of the default setup,
>> and that it finds several servers with no obvious way of knowing which
>> is which. Fortunately, once set up, it usually works. And I know I'm
>> supposed to use the 'ten foot interface' model with a single syatem...
>>
>> My problems did start after trying to test an updated Dutch translation on
>my laptop.
>It looks like starting mythfrontend with the -p command line option, as
>recommended in the Wiki page
>https://www.mythtv.org/wiki/Translation#Do_the_translation, is what causes
>the problems.
>I did expect the "mythfrontend -p" to ask for the language; instead it
>comes up with a backend selection page.
>There are two backends shown with completely identical descriptions.
>Selecting the first one gives a popup box with a prompt for a PIN code.
>Entering 0000 fails, the box remains.
>Selecting the second one works OK without a PIN code. This happens to be
>the production backend in my attic and this is not what I wanted so I just
>exited after clicking around for a while.
>Now on BOTH systems, my laptop and the one in the attic, the "This server
>is the Master Backend" is unchecked.
>I have been able to reproduce this once but not twice.
>
>Looks like there are the following issues:
>
>- The "mythfrontend -p" command is expected to ask for country and language
>but instead it does something completely different. It could be that the
>documentation in https://www.mythtv.org/wiki/Translation#Do_the_translation
>is not correct.
>- The backend configuration is clobbered by "mythfrontend -p". This should
>never happen and is the most serious issue.
>- I can NOT start mythfrontend when I select the backend via the backend
>selection page; it then asks for a PIN code which is not accepted. I can
>however just start mythfrontend without the "-p" option and then it starts
>OK. This is inconsistent.
>- The two backends presented in the backend selection page have a 100%
>identical description. This makes selecting the correct backend a lottery.

If you copy /usr/share/mythtv/devicemaster.xml to
/home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
allow you to change the names that show up when selecting backends.

>I also think that the default for mythtv-setup should be to appear in a
>window and not full screen. Typical use for mythtv-setup, at least for me,
>to run it via ssh on a computer screen and not on the TV. The annoying
>thing is that this can only be changed in mythfrontend.

I believe that it is possible to use -O to override settings that are
in the settings table if the program does not have a native way of
changing them. So something like this might work:

-O RunFrontendInWindow=1

>Klaas.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 06/02/2022 14:32, Stephen Worthington wrote:
> On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:
>
>> On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com> wrote:
>>
>>> On 06/02/2022 10:40, Klaas de Waal wrote:
>>>> Hi,
>>>>
>>>> I have now on two different systems that the checkbox for "This server
>>>> is the Master Backend" is unexpectedly unchecked. This is with testing
>>>> the fixes/32. It could just be that I did something wrong but if others
>>>> also experience this issue it might be a bug.
>>>>
>>>> Klaas.
>>>
>>> I have mythtv-setup problems too, but thought they were caused by
>>> unwanted interaction between boxes intended to be independent. At
>>> present I have switched off the problem box and am wondering if I need a
>>> DB restore. I dislike the full-screen arrogance of the default setup,
>>> and that it finds several servers with no obvious way of knowing which
>>> is which. Fortunately, once set up, it usually works. And I know I'm
>>> supposed to use the 'ten foot interface' model with a single syatem...
>>>
>>> My problems did start after trying to test an updated Dutch translation on
>> my laptop.
>> It looks like starting mythfrontend with the -p command line option, as
>> recommended in the Wiki page
>> https://www.mythtv.org/wiki/Translation#Do_the_translation, is what causes
>> the problems.
>> I did expect the "mythfrontend -p" to ask for the language; instead it
>> comes up with a backend selection page.
>> There are two backends shown with completely identical descriptions.
>> Selecting the first one gives a popup box with a prompt for a PIN code.
>> Entering 0000 fails, the box remains.
>> Selecting the second one works OK without a PIN code. This happens to be
>> the production backend in my attic and this is not what I wanted so I just
>> exited after clicking around for a while.
>> Now on BOTH systems, my laptop and the one in the attic, the "This server
>> is the Master Backend" is unchecked.
>> I have been able to reproduce this once but not twice.
>>
>> Looks like there are the following issues:
>>
>> - The "mythfrontend -p" command is expected to ask for country and language
>> but instead it does something completely different. It could be that the
>> documentation in https://www.mythtv.org/wiki/Translation#Do_the_translation
>> is not correct.
>> - The backend configuration is clobbered by "mythfrontend -p". This should
>> never happen and is the most serious issue.
>> - I can NOT start mythfrontend when I select the backend via the backend
>> selection page; it then asks for a PIN code which is not accepted. I can
>> however just start mythfrontend without the "-p" option and then it starts
>> OK. This is inconsistent.
>> - The two backends presented in the backend selection page have a 100%
>> identical description. This makes selecting the correct backend a lottery.
>
> If you copy /usr/share/mythtv/devicemaster.xml to
> /home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
> allow you to change the names that show up when selecting backends.
>
>> I also think that the default for mythtv-setup should be to appear in a
>> window and not full screen. Typical use for mythtv-setup, at least for me,
>> to run it via ssh on a computer screen and not on the TV. The annoying
>> thing is that this can only be changed in mythfrontend.
>
> I believe that it is possible to use -O to override settings that are
> in the settings table if the program does not have a native way of
> changing them. So something like this might work:
>
> -O RunFrontendInWindow=1
>
>> Klaas.

Thanks, Stephen, for your suggestions. So far I haven't seen any
response to my editing of devicemaster.xml, but I did notice that one
box is showing 32.202201... and another 33.202202... Perhaps it needs a
reboot to be effective. I had restarted the backend.

Starting mythtv-setup with the -w option made things more bearable, but
it still wanted to go through the whole setup process again. So I tried
drop-and-restore using the most recent backup.

{{{

[john@HPFed mythtv]$ perl mythconverg_restore.pl --drop_database
--create_database --filename
/home/john/SGs/MythDBbak/mythconverg-1375-20220203225742.sql.gz
DBD::mysql::st execute failed: Column count of mysql.proc is wrong.
Expected 21, found 20. Created with MariaDB 100015, now running 100513.
Please use mariadb-upgrade to fix this error at mythconverg_restore.pl
line 1052.

ERROR: Unable to drop database.

Fortunately I had "one I made earlier"

[john@HPFed mythtv]$ perl mythconverg_restore.pl --drop_database
--create_database --filename
/home/john/SGs/MythDBbak/mythconverg-1375-20220202181807.sql.gz

Successfully restored backup.
[john@HPFed mythtv]$

}}}

This is very similar to what I saw after the DB update failures of a few
days ago, before the key-length commit, but then the partially-upgraded
backup was quite small. Both those above are 28 MB, and 100 MB on the
el7 box.

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 06/02/2022 19:04, John Pilkington wrote:

> On 06/02/2022 14:32, Stephen Worthington wrote:
>> On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:
>>
>>> On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com>
>>> wrote:
>>>
>>>> On 06/02/2022 10:40, Klaas de Waal wrote:
>>>>> Hi,
>>>>>
>>>>> I have now on two different systems that the checkbox for "This
>>>>> server
>>>>> is the Master Backend" is unexpectedly unchecked. This is with
>>>>> testing
>>>>> the fixes/32. It could just be that I did something wrong but if
>>>>> others
>>>>> also experience this issue it might be a bug.
>>>>>
>>>>> Klaas.
>>>>
>>>> I have mythtv-setup problems too, but thought they were caused by
>>>> unwanted interaction between boxes intended to be independent.  At
>>>> present I have switched off the problem box and am wondering if I
>>>> need a
>>>> DB restore.    I dislike the full-screen arrogance of the default
>>>> setup,
>>>> and that it finds several servers with no obvious way of knowing which
>>>> is which.   Fortunately, once set up, it usually works.  And I know
>>>> I'm
>>>> supposed to use the 'ten foot interface' model with a single syatem...
>>>>
>>>> My problems did start after trying to test an updated Dutch
>>>> translation on
>>> my laptop.
>>> It looks like starting mythfrontend with the -p command line option, as
>>> recommended in the Wiki page
>>> https://www.mythtv.org/wiki/Translation#Do_the_translation, is what
>>> causes
>>> the problems.
>>> I did expect the "mythfrontend -p" to ask for the language; instead it
>>> comes up with a backend selection page.
>>> There are two backends shown with completely identical descriptions.
>>> Selecting the first one gives a popup box with a prompt for a PIN code.
>>> Entering 0000 fails, the box remains.
>>> Selecting the second one works OK without a PIN code. This happens
>>> to be
>>> the production backend in my attic and this is not what I wanted so
>>> I just
>>> exited after clicking around for a while.
>>> Now on BOTH systems, my laptop and the one in the attic, the "This
>>> server
>>> is the Master Backend" is unchecked.
>>> I have been able to reproduce this once but not twice.
>>>
>>> Looks like there are the following issues:
>>>
>>> - The "mythfrontend -p" command is expected to ask for country and
>>> language
>>> but instead it does something completely different. It could be that
>>> the
>>> documentation in
>>> https://www.mythtv.org/wiki/Translation#Do_the_translation
>>> is not correct.
>>> - The backend configuration is clobbered by "mythfrontend -p". This
>>> should
>>> never happen and is the most serious issue.
>>> - I can NOT start mythfrontend when I select the backend via the
>>> backend
>>> selection page; it then asks for a PIN code which is not accepted. 
>>> I can
>>> however just start mythfrontend without the "-p" option and then it
>>> starts
>>> OK. This is inconsistent.
>>> - The two backends presented in the backend selection page have a 100%
>>> identical description. This makes selecting the correct backend a
>>> lottery.
>>
>> If you copy /usr/share/mythtv/devicemaster.xml to
>> /home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
>> allow you to change the names that show up when selecting backends.
>>
>>> I also think that the default for mythtv-setup should be to appear in a
>>> window and not full screen. Typical use for mythtv-setup, at least
>>> for me,
>>> to run it via ssh on a computer screen and not on the TV. The annoying
>>> thing is that this can only be changed in mythfrontend.
>>
>> I believe that it is possible to use -O to override settings that are
>> in the settings table if the program does not have a native way of
>> changing them.  So something like this might work:
>>
>> -O RunFrontendInWindow=1
>>
>>> Klaas.
>
> Thanks, Stephen, for your suggestions.  So far I haven't seen any
> response to my editing of devicemaster.xml, but I did notice that one
> box is showing 32.202201... and another 33.202202...  Perhaps it needs
> a reboot to be effective.  I had restarted the backend.
>
>
You need to tell the backend where to look for the new devicemaster.xml
file.

https://www.mythtv.org/wiki/UPnP#Overriding_the_default_devicemaster.xml_file


Paul H.

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 06/02/2022 22:05, Paul Harrison wrote:
> On 06/02/2022 19:04, John Pilkington wrote:
>
>> On 06/02/2022 14:32, Stephen Worthington wrote:
>>> On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:
>>>
>>>> On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com>
>>>> wrote:
>>>>
>>>>> On 06/02/2022 10:40, Klaas de Waal wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have now on two different systems that the checkbox for "This
>>>>>> server
>>>>>> is the Master Backend" is unexpectedly unchecked. This is with
>>>>>> testing
>>>>>> the fixes/32. It could just be that I did something wrong but if
>>>>>> others
>>>>>> also experience this issue it might be a bug.
>>>>>>
>>>>>> Klaas.
>>>>>
>>>>> I have mythtv-setup problems too, but thought they were caused by
>>>>> unwanted interaction between boxes intended to be independent.  At
>>>>> present I have switched off the problem box and am wondering if I
>>>>> need a
>>>>> DB restore.    I dislike the full-screen arrogance of the default
>>>>> setup,
>>>>> and that it finds several servers with no obvious way of knowing which
>>>>> is which.   Fortunately, once set up, it usually works.  And I know
>>>>> I'm
>>>>> supposed to use the 'ten foot interface' model with a single syatem...
>>>>>
>>>>> My problems did start after trying to test an updated Dutch
>>>>> translation on
>>>> my laptop.
>>>> It looks like starting mythfrontend with the -p command line option, as
>>>> recommended in the Wiki page
>>>> https://www.mythtv.org/wiki/Translation#Do_the_translation, is what
>>>> causes
>>>> the problems.
>>>> I did expect the "mythfrontend -p" to ask for the language; instead it
>>>> comes up with a backend selection page.
>>>> There are two backends shown with completely identical descriptions.
>>>> Selecting the first one gives a popup box with a prompt for a PIN code.
>>>> Entering 0000 fails, the box remains.
>>>> Selecting the second one works OK without a PIN code. This happens
>>>> to be
>>>> the production backend in my attic and this is not what I wanted so
>>>> I just
>>>> exited after clicking around for a while.
>>>> Now on BOTH systems, my laptop and the one in the attic, the "This
>>>> server
>>>> is the Master Backend" is unchecked.
>>>> I have been able to reproduce this once but not twice.
>>>>
>>>> Looks like there are the following issues:
>>>>
>>>> - The "mythfrontend -p" command is expected to ask for country and
>>>> language
>>>> but instead it does something completely different. It could be that
>>>> the
>>>> documentation in
>>>> https://www.mythtv.org/wiki/Translation#Do_the_translation
>>>> is not correct.
>>>> - The backend configuration is clobbered by "mythfrontend -p". This
>>>> should
>>>> never happen and is the most serious issue.
>>>> - I can NOT start mythfrontend when I select the backend via the
>>>> backend
>>>> selection page; it then asks for a PIN code which is not accepted. I
>>>> can
>>>> however just start mythfrontend without the "-p" option and then it
>>>> starts
>>>> OK. This is inconsistent.
>>>> - The two backends presented in the backend selection page have a 100%
>>>> identical description. This makes selecting the correct backend a
>>>> lottery.
>>>
>>> If you copy /usr/share/mythtv/devicemaster.xml to
>>> /home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
>>> allow you to change the names that show up when selecting backends.
>>>
>>>> I also think that the default for mythtv-setup should be to appear in a
>>>> window and not full screen. Typical use for mythtv-setup, at least
>>>> for me,
>>>> to run it via ssh on a computer screen and not on the TV. The annoying
>>>> thing is that this can only be changed in mythfrontend.
>>>
>>> I believe that it is possible to use -O to override settings that are
>>> in the settings table if the program does not have a native way of
>>> changing them.  So something like this might work:
>>>
>>> -O RunFrontendInWindow=1
>>>
>>>> Klaas.
>>
>> Thanks, Stephen, for your suggestions.  So far I haven't seen any
>> response to my editing of devicemaster.xml, but I did notice that one
>> box is showing 32.202201... and another 33.202202...  Perhaps it needs
>> a reboot to be effective.  I had restarted the backend.
>>
>>
> You need to tell the backend where to look for the new devicemaster.xml
> file.
>
> https://www.mythtv.org/wiki/UPnP#Overriding_the_default_devicemaster.xml_file
>
>
>
> Paul H.
>

OK, thanks Paul. I had assumed that ~/.mythtv would work, as it does
for the themes. And I've had enough excitement for today, and things
seem to be working. But my experience with (at least two) boxes 'unable
to drop the database' when trying to use their latest backup alarms me,
and I would prefer not to try it again.

John

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, 6 Feb 2022 at 23:06, Paul Harrison <mythtv@mythqml.net> wrote:

> On 06/02/2022 19:04, John Pilkington wrote:
>
> > On 06/02/2022 14:32, Stephen Worthington wrote:
> >> On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:
> >>
> >>> On Sun, 6 Feb 2022 at 12:36, John Pilkington <johnpilk222@gmail.com>
> >>> wrote:
> >>>
> >>>> On 06/02/2022 10:40, Klaas de Waal wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I have now on two different systems that the checkbox for "This
> >>>>> server
> >>>>> is the Master Backend" is unexpectedly unchecked. This is with
> >>>>> testing
> >>>>> the fixes/32. It could just be that I did something wrong but if
> >>>>> others
> >>>>> also experience this issue it might be a bug.
> >>>>>
> >>>>> Klaas.
> >>>>
> >>>> I have mythtv-setup problems too, but thought they were caused by
> >>>> unwanted interaction between boxes intended to be independent. At
> >>>> present I have switched off the problem box and am wondering if I
> >>>> need a
> >>>> DB restore. I dislike the full-screen arrogance of the default
> >>>> setup,
> >>>> and that it finds several servers with no obvious way of knowing which
> >>>> is which. Fortunately, once set up, it usually works. And I know
> >>>> I'm
> >>>> supposed to use the 'ten foot interface' model with a single syatem...
> >>>>
> >>>> My problems did start after trying to test an updated Dutch
> >>>> translation on
> >>> my laptop.
> >>> It looks like starting mythfrontend with the -p command line option, as
> >>> recommended in the Wiki page
> >>> https://www.mythtv.org/wiki/Translation#Do_the_translation, is what
> >>> causes
> >>> the problems.
> >>> I did expect the "mythfrontend -p" to ask for the language; instead it
> >>> comes up with a backend selection page.
> >>> There are two backends shown with completely identical descriptions.
> >>> Selecting the first one gives a popup box with a prompt for a PIN code.
> >>> Entering 0000 fails, the box remains.
> >>> Selecting the second one works OK without a PIN code. This happens
> >>> to be
> >>> the production backend in my attic and this is not what I wanted so
> >>> I just
> >>> exited after clicking around for a while.
> >>> Now on BOTH systems, my laptop and the one in the attic, the "This
> >>> server
> >>> is the Master Backend" is unchecked.
> >>> I have been able to reproduce this once but not twice.
> >>>
> >>> Looks like there are the following issues:
> >>>
> >>> - The "mythfrontend -p" command is expected to ask for country and
> >>> language
> >>> but instead it does something completely different. It could be that
> >>> the
> >>> documentation in
> >>> https://www.mythtv.org/wiki/Translation#Do_the_translation
> >>> is not correct.
> >>> - The backend configuration is clobbered by "mythfrontend -p". This
> >>> should
> >>> never happen and is the most serious issue.
> >>> - I can NOT start mythfrontend when I select the backend via the
> >>> backend
> >>> selection page; it then asks for a PIN code which is not accepted.
> >>> I can
> >>> however just start mythfrontend without the "-p" option and then it
> >>> starts
> >>> OK. This is inconsistent.
> >>> - The two backends presented in the backend selection page have a 100%
> >>> identical description. This makes selecting the correct backend a
> >>> lottery.
> >>
> >> If you copy /usr/share/mythtv/devicemaster.xml to
> >> /home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
> >> allow you to change the names that show up when selecting backends.
> >>
> >>> I also think that the default for mythtv-setup should be to appear in a
> >>> window and not full screen. Typical use for mythtv-setup, at least
> >>> for me,
> >>> to run it via ssh on a computer screen and not on the TV. The annoying
> >>> thing is that this can only be changed in mythfrontend.
> >>
> >> I believe that it is possible to use -O to override settings that are
> >> in the settings table if the program does not have a native way of
> >> changing them. So something like this might work:
> >>
> >> -O RunFrontendInWindow=1
> >>
> >>> Klaas.
> >
> > Thanks, Stephen, for your suggestions. So far I haven't seen any
> > response to my editing of devicemaster.xml, but I did notice that one
> > box is showing 32.202201... and another 33.202202... Perhaps it needs
> > a reboot to be effective. I had restarted the backend.
> >
> >
> You need to tell the backend where to look for the new devicemaster.xml
> file.
>
>
> https://www.mythtv.org/wiki/UPnP#Overriding_the_default_devicemaster.xml_file
>
>
> We live and learn! I did not know this.
But maybe we can add something that makes the default identification a bit
easier.
Currently it shows the string "MythTV AV Media Server" plus the MythTV
version and date, now 32.202....
Which happens to be the same for my production backend and my development
laptop.
Can we tack on the hostname and/or the IP address somewhere?
E.g. "MythTV AV Media Server v32" plus "hostname:192.168.1.23" would be
perfect unless there is more than one mythbackend running per host.
I did experiment a bit but getting the MythUIButtonListItem to do what I
want proved too much on a late Sunday evening.
Also, we should agree if this is a good idea before we implement it. Maybe
a ticket.

And then there is the issue of the master backend setting being modified
when "mythfrontend --prompt" is used.
And why is it possible to start mythfrontend without the --prompt but that
it fails on a pin code validation when --prompt is used....

Klaas.

On 06/02/2022 22:35, Klaas de Waal wrote:
>
>
> On Sun, 6 Feb 2022 at 23:06, Paul Harrison <mythtv@mythqml.net
> <mailto:mythtv@mythqml.net>> wrote:
>
> On 06/02/2022 19:04, John Pilkington wrote:
>
> > On 06/02/2022 14:32, Stephen Worthington wrote:
> >> On Sun, 6 Feb 2022 14:43:35 +0100, you wrote:
> >>
> >>> On Sun, 6 Feb 2022 at 12:36, John Pilkington
> <johnpilk222@gmail.com <mailto:johnpilk222@gmail.com>>
> >>> wrote:
> >>>
> >>>> On 06/02/2022 10:40, Klaas de Waal wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I have now on two different systems that the checkbox for "This
> >>>>> server
> >>>>> is the Master Backend" is unexpectedly unchecked. This is with
> >>>>> testing
> >>>>> the fixes/32. It could just be that I did something wrong but if
> >>>>> others
> >>>>> also experience this issue it might be a bug.
> >>>>>
> >>>>> Klaas.
> >>>>
> >>>> I have mythtv-setup problems too, but thought they were caused by
> >>>> unwanted interaction between boxes intended to be independent.  At
> >>>> present I have switched off the problem box and am wondering if I
> >>>> need a
> >>>> DB restore.    I dislike the full-screen arrogance of the default
> >>>> setup,
> >>>> and that it finds several servers with no obvious way of
> knowing which
> >>>> is which.   Fortunately, once set up, it usually works.  And I
> know
> >>>> I'm
> >>>> supposed to use the 'ten foot interface' model with a single
> syatem...
> >>>>
> >>>> My problems did start after trying to test an updated Dutch
> >>>> translation on
> >>> my laptop.
> >>> It looks like starting mythfrontend with the -p command line
> option, as
> >>> recommended in the Wiki page
> >>> https://www.mythtv.org/wiki/Translation#Do_the_translation
> <https://www.mythtv.org/wiki/Translation#Do_the_translation>, is what
> >>> causes
> >>> the problems.
> >>> I did expect the "mythfrontend -p" to ask for the language;
> instead it
> >>> comes up with a backend selection page.
> >>> There are two backends shown with completely identical
> descriptions.
> >>> Selecting the first one gives a popup box with a prompt for a
> PIN code.
> >>> Entering 0000 fails, the box remains.
> >>> Selecting the second one works OK without a PIN code. This happens
> >>> to be
> >>> the production backend in my attic and this is not what I
> wanted so
> >>> I just
> >>> exited after clicking around for a while.
> >>> Now on BOTH systems, my laptop and the one in the attic, the "This
> >>> server
> >>> is the Master Backend" is unchecked.
> >>> I have been able to reproduce this once but not twice.
> >>>
> >>> Looks like there are the following issues:
> >>>
> >>> - The "mythfrontend -p" command is expected to ask for country and
> >>> language
> >>> but instead it does something completely different. It could be
> that
> >>> the
> >>> documentation in
> >>> https://www.mythtv.org/wiki/Translation#Do_the_translation
> <https://www.mythtv.org/wiki/Translation#Do_the_translation>
> >>> is not correct.
> >>> - The backend configuration is clobbered by "mythfrontend -p".
> This
> >>> should
> >>> never happen and is the most serious issue.
> >>> - I can NOT start mythfrontend when I select the backend via the
> >>> backend
> >>> selection page; it then asks for a PIN code which is not accepted.
> >>> I can
> >>> however just start mythfrontend without the "-p" option and
> then it
> >>> starts
> >>> OK. This is inconsistent.
> >>> - The two backends presented in the backend selection page have
> a 100%
> >>> identical description. This makes selecting the correct backend a
> >>> lottery.
> >>
> >> If you copy /usr/share/mythtv/devicemaster.xml to
> >> /home/mythtv/.mythtv/devicemaster.xml and edit it there, that should
> >> allow you to change the names that show up when selecting backends.
> >>
> >>> I also think that the default for mythtv-setup should be to
> appear in a
> >>> window and not full screen. Typical use for mythtv-setup, at least
> >>> for me,
> >>> to run it via ssh on a computer screen and not on the TV. The
> annoying
> >>> thing is that this can only be changed in mythfrontend.
> >>
> >> I believe that it is possible to use -O to override settings
> that are
> >> in the settings table if the program does not have a native way of
> >> changing them.  So something like this might work:
> >>
> >> -O RunFrontendInWindow=1
> >>
> >>> Klaas.
> >
> > Thanks, Stephen, for your suggestions.  So far I haven't seen any
> > response to my editing of devicemaster.xml, but I did notice that
> one
> > box is showing 32.202201... and another 33.202202...  Perhaps it
> needs
> > a reboot to be effective.  I had restarted the backend.
> >
> >
> You need to tell the backend where to look for the new devicemaster.xml
> file.
>
> https://www.mythtv.org/wiki/UPnP#Overriding_the_default_devicemaster.xml_file
> <https://www.mythtv.org/wiki/UPnP#Overriding_the_default_devicemaster.xml_file>
>
>
> We live and learn! I did not know this.
> But maybe we can add something that makes the default identification a
> bit easier.
> Currently it shows the string  "MythTV AV Media Server" plus the MythTV
> version and date, now 32.202....

If anything we probably need to put the major version number first.
On my TV both show up as "MythTV AV Se..." (ie. it's truncated)

For now devicemaster is the way to do it. I'll see if we can do
something as part of the upnp rework.


Regards
Stuart

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org