Mailing List Archive

On Sat, 7 Jan 2023 at 15:03, James Abernathy <jfabernathy@gmail.com> wrote:

> I was trying to install MythTV and came to the part where I'm setting up
> the backend with mythtv-setup and when I select New Video Source it never
> responds. I can't exit, and have to switch to a console login (Ctl-Alt-F3)
> and reboot.
>

I saw somebody else report exactly the same issue on IRC in #mythtv-users.
I was going to suggest they file an issue on GitHub about it, but they'd
left the channel by the time I saw it. I'd suggest you do that if nobody
else has already.

Cheers, Ian

On Sat, Jan 7, 2023 at 10:47 AM Ian Cameron <mkbloke@gmail.com> wrote:

>
>
> On Sat, 7 Jan 2023 at 15:03, James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>> I was trying to install MythTV and came to the part where I'm setting up
>> the backend with mythtv-setup and when I select New Video Source it never
>> responds. I can't exit, and have to switch to a console login (Ctl-Alt-F3)
>> and reboot.
>>
>
> I saw somebody else report exactly the same issue on IRC in
> #mythtv-users. I was going to suggest they file an issue on GitHub about
> it, but they'd left the channel by the time I saw it. I'd suggest you do
> that if nobody else has already.
>
> Cheers, Ian
>

Okay, I will. Not sure I can be as helpful as I'd like with this lack of
real data. I checked the logs and nothing of real interest.

Jim A

On Sat, 7 Jan 2023 10:51:34 -0500, you wrote:

>On Sat, Jan 7, 2023 at 10:47 AM Ian Cameron <mkbloke@gmail.com> wrote:
>
>>
>>
>> On Sat, 7 Jan 2023 at 15:03, James Abernathy <jfabernathy@gmail.com>
>> wrote:
>>
>>> I was trying to install MythTV and came to the part where I'm setting up
>>> the backend with mythtv-setup and when I select New Video Source it never
>>> responds. I can't exit, and have to switch to a console login (Ctl-Alt-F3)
>>> and reboot.
>>>
>>
>> I saw somebody else report exactly the same issue on IRC in
>> #mythtv-users. I was going to suggest they file an issue on GitHub about
>> it, but they'd left the channel by the time I saw it. I'd suggest you do
>> that if nobody else has already.
>>
>> Cheers, Ian
>>
>
>Okay, I will. Not sure I can be as helpful as I'd like with this lack of
>real data. I checked the logs and nothing of real interest.
>
>Jim A

Like all the MythTV programs, mythtv-setup.real accepts debug options
on its command line. Run this from a command line to see the options:

mythtv-setup.real --help

When running it without --help, make sure to do it from the mythtv
user or a user in the mythtv group (such as the user that runs the GUI
and mythfrontend). When run from the command line, the log output
will normally be back to that terminal, so you can see it and collect
it using a command line like this:

mythtv-setup.real --loglevel debug -v all 2&>1 | tee mythtv-setup.log
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sat, Jan 7, 2023 at 11:33 AM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Sat, 7 Jan 2023 10:51:34 -0500, you wrote:
>
> >On Sat, Jan 7, 2023 at 10:47 AM Ian Cameron <mkbloke@gmail.com> wrote:
> >
> >>
> >>
> >> On Sat, 7 Jan 2023 at 15:03, James Abernathy <jfabernathy@gmail.com>
> >> wrote:
> >>
> >>> I was trying to install MythTV and came to the part where I'm setting
> up
> >>> the backend with mythtv-setup and when I select New Video Source it
> never
> >>> responds. I can't exit, and have to switch to a console login
> (Ctl-Alt-F3)
> >>> and reboot.
> >>>
> >>
> >> I saw somebody else report exactly the same issue on IRC in
> >> #mythtv-users. I was going to suggest they file an issue on GitHub
> about
> >> it, but they'd left the channel by the time I saw it. I'd suggest you
> do
> >> that if nobody else has already.
> >>
> >> Cheers, Ian
> >>
> >
> >Okay, I will. Not sure I can be as helpful as I'd like with this lack of
> >real data. I checked the logs and nothing of real interest.
> >
> >Jim A
>
> Like all the MythTV programs, mythtv-setup.real accepts debug options
> on its command line. Run this from a command line to see the options:
>
> mythtv-setup.real --help
>
> When running it without --help, make sure to do it from the mythtv
> user or a user in the mythtv group (such as the user that runs the GUI
> and mythfrontend). When run from the command line, the log output
> will normally be back to that terminal, so you can see it and collect
> it using a command line like this:
>
> mythtv-setup.real --loglevel debug -v all 2&>1 | tee mythtv-setup.log
>

Thanks, for accuracy I fixed the typo 2>&1. However, I did get a lot of
logging, about 2M worth.

The relevant part seems to be:

2023-01-07 12:42:26.904467 I MSqlQuery::exec(DBManager1) SELECT CAST(name
AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took 1ms, Returned 0
row(s)
2023-01-07 12:42:26.904756 D Setting 'Perform EIT Scan' changed to 1
2023-01-07 12:42:26.904815 D Setting 'Perform EIT Scan' changed to 0
2023-01-07 12:42:26.906689 I MSqlQuery::exec(DBManager1) SELECT
xmltvgrabber, userid, password, lineupid FROM videosource WHERE sourceid =
'0' <<<< Took 0ms, Returned 0 row(s)
2023-01-07 12:42:26.906952 I InputHandler: Locking input devices
2023-01-07 12:42:26.906966 N Suspending idle timer
2023-01-07 12:42:26.907751 D Launching: tv_find_grabbers baseline
2023-01-07 12:42:26.927515 I Managed child (PID: 2551) has started! *
command=tv_find_grabbers baseline, timeout=25
2023-01-07 12:42:26.927787 I (0xaaaae405f790)::IncrRef() -> 2
2023-01-07 12:42:26.928227 I XMLTVGrabber::Load(): Running
'tv_find_grabbers baseline'.
2023-01-07 12:42:26.968551 I Managed child (PID: 2551) has exited!
command=tv_find_grabbers baseline, status=32512, result=127
2023-01-07 12:42:26.978728 I (0xaaaae405f790)::DecrRef() -> 1
2023-01-07 12:42:26.978757 E XMLTVGrabber::Load(): Failed to run
tv_find_grabbers
2023-01-07 12:42:26.978817 I (0xaaaae405f790)::DecrRef() -> 0
2023-01-07 12:42:26.981466 I MSqlQuery::exec(DBManager1) SELECT
CAST(xmltvgrabber AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.983209 I MSqlQuery::exec(DBManager1) SELECT
CAST(useeit AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took 0ms,
Returned 0 row(s)
2023-01-07 12:42:26.984887 I MSqlQuery::exec(DBManager1) SELECT
CAST(useeit AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took 0ms,
Returned 0 row(s)
2023-01-07 12:42:26.986451 I MSqlQuery::exec(DBManager1) SELECT
CAST(freqtable AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.988096 I MSqlQuery::exec(DBManager1) SELECT
CAST(scanfrequency AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.989601 I MSqlQuery::exec(DBManager1) SELECT
CAST(dvb_nit_id AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.991284 I MSqlQuery::exec(DBManager1) SELECT
CAST(bouquet_id AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.992665 I MSqlQuery::exec(DBManager1) SELECT
CAST(region_id AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.993490 I MSqlQuery::exec(DBManager1) SELECT
CAST(lcnoffset AS CHAR) FROM videosource WHERE sourceid = '0' <<<< Took
0ms, Returned 0 row(s)
2023-01-07 12:42:26.996443 I InputHandler: Unlocking input devices
2023-01-07 12:42:26.996456 N Resuming idle timer
2023-01-07 12:42:46.386036 I (0xffff640078f0)::IncrRef() -> 2
2023-01-07 12:42:46.386052 I (0xffff640078f0)::DecrRef() -> 1
2023-01-07 12:42:46.386071 I (0xffff640104c0)::IncrRef() -> 2
2023-01-07 12:42:46.386080 I (0xffff640104c0)::DecrRef() -> 1
2023-01-07 12:42:46.386096 I (0xffff64005f40)::IncrRef() -> 2
2023-01-07 12:42:46.386103 I (0xffff64005f40)::DecrRef() -> 1
2023-01-07 12:42:46.386108 I (0xffff640077b0)::IncrRef() -> 2

I can put the rest of it on the github issue.

Jim A

On 1/7/23 12:02, James Abernathy wrote:

> 2023-01-07 12:42:26.968551 I  Managed child (PID: 2551) has exited! command=tv_find_grabbers baseline, status=32512, result=127

Just curious, is the xmltv package installed (guessing not).

From the command line, running the command: find_grabbers baseline
should work if the package is there. Ansible doesn't require the
package.

FYI, logging to a file is better using --logpath /tmp (or any
directory even .). You'll see that it includes the filename
and line number of where the message was printed.

--
Bill

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

On Sat, Jan 7, 2023 at 2:32 PM Bill Meek <keemllib@gmail.com> wrote:

> On 1/7/23 12:02, James Abernathy wrote:
>
> > 2023-01-07 12:42:26.968551 I Managed child (PID: 2551) has exited!
> command=tv_find_grabbers baseline, status=32512, result=127
>
> Just curious, is the xmltv package installed (guessing not).
>
> From the command line, running the command: find_grabbers baseline
> should work if the package is there. Ansible doesn't require the
> package.
>
> FYI, logging to a file is better using --logpath /tmp (or any
> directory even .). You'll see that it includes the filename
> and line number of where the message was printed.
>
> --
> Bill
>

The first time I tried it I did not have xmltv installed. After I got it
working by using ssh -X jim@192.168.0.131 and running mythtv-setup, I then
did a fresh install with XMLTV prior to running mythtv-setup the first
time. I had the same issue and fixed it via ssh -X ...

Next was where you have the log from. It does not have XMLTV installed
since EIT EPG is the simplest to get working with OTA tuners. I'm keeping
that SSD separate so I can try anything someone comes up with.

Jim A

On Sat, Jan 7, 2023 at 2:53 PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Sat, Jan 7, 2023 at 2:32 PM Bill Meek <keemllib@gmail.com> wrote:
>
>> On 1/7/23 12:02, James Abernathy wrote:
>>
>> > 2023-01-07 12:42:26.968551 I Managed child (PID: 2551) has exited!
>> command=tv_find_grabbers baseline, status=32512, result=127
>>
>> Just curious, is the xmltv package installed (guessing not).
>>
>> From the command line, running the command: find_grabbers baseline
>> should work if the package is there. Ansible doesn't require the
>> package.
>>
>> FYI, logging to a file is better using --logpath /tmp (or any
>> directory even .). You'll see that it includes the filename
>> and line number of where the message was printed.
>>
>> --
>> Bill
>>
>
> The first time I tried it I did not have xmltv installed. After I got it
> working by using ssh -X jim@192.168.0.131 and running mythtv-setup, I
> then did a fresh install with XMLTV prior to running mythtv-setup the first
> time. I had the same issue and fixed it via ssh -X ...
>
> Next was where you have the log from. It does not have XMLTV installed
> since EIT EPG is the simplest to get working with OTA tuners. I'm keeping
> that SSD separate so I can try anything someone comes up with.
>
> Jim A
>

And BTW, this hardware is Intel Iris Graphics:

Operating System: EndeavourOS
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.1.3-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 15.0 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics

On Sat, Jan 7, 2023 at 3:21 PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Sat, Jan 7, 2023 at 2:53 PM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Sat, Jan 7, 2023 at 2:32 PM Bill Meek <keemllib@gmail.com> wrote:
>>
>>> On 1/7/23 12:02, James Abernathy wrote:
>>>
>>> > 2023-01-07 12:42:26.968551 I Managed child (PID: 2551) has exited!
>>> command=tv_find_grabbers baseline, status=32512, result=127
>>>
>>> Just curious, is the xmltv package installed (guessing not).
>>>
>>> From the command line, running the command: find_grabbers baseline
>>> should work if the package is there. Ansible doesn't require the
>>> package.
>>>
>>> FYI, logging to a file is better using --logpath /tmp (or any
>>> directory even .). You'll see that it includes the filename
>>> and line number of where the message was printed.
>>>
>>> --
>>> Bill
>>>
>>
>> The first time I tried it I did not have xmltv installed. After I got it
>> working by using ssh -X jim@192.168.0.131 and running mythtv-setup, I
>> then did a fresh install with XMLTV prior to running mythtv-setup the first
>> time. I had the same issue and fixed it via ssh -X ...
>>
>> Next was where you have the log from. It does not have XMLTV installed
>> since EIT EPG is the simplest to get working with OTA tuners. I'm keeping
>> that SSD separate so I can try anything someone comes up with.
>>
>> Jim A
>>
>
> And BTW, this hardware is Intel Iris Graphics:
>
> Operating System: EndeavourOS
> KDE Plasma Version: 5.26.5
> KDE Frameworks Version: 5.101.0
> Qt Version: 5.15.7
> Kernel Version: 6.1.3-arch1-1 (64-bit)
> Graphics Platform: X11
> Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
> Memory: 15.0 GiB of RAM
> Graphics Processor: Mesa Intel® Xe Graphics
>

FORGET LAST reply. Wrong message thread