Mailing List Archive

On 04/01/2020 16:00, Klaas de Waal wrote:
> Hi,
>
> With today's master I get the following warning on start of
> mythfrontend (3 lines before and 1 line after also shown):
>
> 2020-01-04 16:55:34.268534 I Checking for theme updates every hour
> 2020-01-04 16:55:34.268722 I Registering HouseKeeperTask 'HardwareProfiler'.
> 2020-01-04 16:55:34.269404 I Starting HouseKeeper.
> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> 2020-01-04 16:55:34.433313 I Bonjour: Service registration complete:
> name 'Mythfrontend on modu' type '_mythfrontend._tcp.' domain:
> 'local.'
>
> This is with mythfrontend running in a 1280x720 window on a 1920x1200
> screen, Intel graphics only.
>
> Groetjes,
> Klaas.


I see something similar using an NVidia card.

Early in the log I see these errors

[AVHWDeviceContext @ 0x562dd8ad6cc0] libva: va_getDriverName() failed
with unknown libva error,driver_name=(null)
[AVHWDeviceContext @ 0x562dd8ad6cc0] Failed to initialise VAAPI
connection: -1 (unknown libva error).


Then later  same as Klaas

Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
Qt::WA_PaintOnScreen to exclude from backingstore sync)
Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
Qt::WA_PaintOnScreen to exclude from backingstore sync)


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 04/01/2020 16:33, Paul Harrison wrote:
>
> On 04/01/2020 16:00, Klaas de Waal wrote:
>> Hi,
>>
>> With today's master I get the following warning on start of
>> mythfrontend (3 lines before and 1 line after also shown):
>>
>> 2020-01-04 16:55:34.268534 I  Checking for theme updates every hour
>> 2020-01-04 16:55:34.268722 I  Registering HouseKeeperTask
>> 'HardwareProfiler'.
>> 2020-01-04 16:55:34.269404 I  Starting HouseKeeper.
>> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
>> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
>> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
>> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
>> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
>> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
>> 2020-01-04 16:55:34.433313 I  Bonjour: Service registration complete:
>> name 'Mythfrontend on modu' type '_mythfrontend._tcp.' domain:
>> 'local.'
>>
>> This is with mythfrontend running in  a 1280x720 window on a 1920x1200
>> screen, Intel graphics only.
>>
>> Groetjes,
>> Klaas.
>
>
> I see something similar using an NVidia card.
>
> Early in the log I see these errors
>
> [AVHWDeviceContext @ 0x562dd8ad6cc0] libva: va_getDriverName() failed
> with unknown libva error,driver_name=(null)
> [AVHWDeviceContext @ 0x562dd8ad6cc0] Failed to initialise VAAPI
> connection: -1 (unknown libva error).
>
>
> Then later  same as Klaas
>
> Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
> Qt::WA_PaintOnScreen to exclude from backingstore sync)
> Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
> Qt::WA_PaintOnScreen to exclude from backingstore sync)
>
>
> Paul H.

Paul's VAAPI report has been showing up on my systems, which don't have
that hardware, for several weeks. The 'flush' ones look as if they
might be related to another oldish report of 'I Display: New main
window/W Display: Widget does not have a window!'

John P
_______________________________________________
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 Sat, 4 Jan 2020 at 16:01, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> 2020-01-04 16:55:34.433313 I Bonjour: Service registration complete:
> name 'Mythfrontend on modu' type '_mythfrontend._tcp.' domain:
> 'local.'

Klaas - can you check whether you still get these warnings with the
latest master?

Thanks, Mark
_______________________________________________
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

> > Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> > name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> > using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> > Attempted flush to non-raster surface QWidgetWindow(0x131d220,
> > name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
> > using Qt::WA_PaintOnScreen to exclude from backingstore sync)
> > 2020-01-04 16:55:34.433313 I Bonjour: Service registration complete:
> > name 'Mythfrontend on modu' type '_mythfrontend._tcp.' domain:
> > 'local.'
>
> Klaas - can you check whether you still get these warnings with the
> latest master?
>
Hi Mark,

The Qt warnings have gone!

While on the subject of error messages, there is one left in the
mythfrontend startup log, similar but not identical to the message
reported by Paul Harrison (one line before and one line after the
error messages included):

2020-01-05 21:46:26.212846 I MythCoreContext::CheckProtoVersion():
Using protocol version 91 BuzzOff
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
object file: No such file or directory
[AVHWDeviceContext @ 0x2e6dd40] Failed to initialise VAAPI connection:
-1 (unknown libva error).
Cannot load libcuda.so.1
2020-01-05 21:46:26.339497 E CECAdapter: Failed to find any CEC devices.

This on Fedora 31, Intel graphics only.

Thanks & Regards,
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 Sun, 5 Jan 2020 at 21:02, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
> The Qt warnings have gone!

Good - thanks for confirming.

> While on the subject of error messages, there is one left in the
> mythfrontend startup log, similar but not identical to the message
> reported by Paul Harrison (one line before and one line after the
> error messages included):
>
> 2020-01-05 21:46:26.212846 I MythCoreContext::CheckProtoVersion():
> Using protocol version 91 BuzzOff
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
> object file: No such file or directory

I assume you mean the VAAPI message below?

I'm slightly baffled by this - as it is an FFmpeg log message - and I
don't see any associated/relevant MythTV logging...

Can you attach a full log? I'm assuming you have VAAPI support
compiled in. Are you using VAAPI? and is it still available after this
log message?

> [AVHWDeviceContext @ 0x2e6dd40] Failed to initialise VAAPI connection:

Thanks, Mark
_______________________________________________
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 04/01/2020 16:33, Paul Harrison wrote:
>
> On 04/01/2020 16:00, Klaas de Waal wrote:
>> Hi,
>>
>> With today's master I get the following warning on start of
>> mythfrontend (3 lines before and 1 line after also shown):
>>
>> 2020-01-04 16:55:34.268534 I  Checking for theme updates every hour
>> 2020-01-04 16:55:34.268722 I  Registering HouseKeeperTask
>> 'HardwareProfiler'.
>> 2020-01-04 16:55:34.269404 I  Starting HouseKeeper.
>> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
>> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
>> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
>> Attempted flush to non-raster surface QWidgetWindow(0x131d220,
>> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider
>> using Qt::WA_PaintOnScreen to exclude from backingstore sync)
>> 2020-01-04 16:55:34.433313 I  Bonjour: Service registration complete:
>> name 'Mythfrontend on modu' type '_mythfrontend._tcp.' domain:
>> 'local.'
>>
>> This is with mythfrontend running in  a 1280x720 window on a 1920x1200
>> screen, Intel graphics only.
>>
>> Groetjes,
>> Klaas.
>
>
> I see something similar using an NVidia card.
>
> Early in the log I see these errors
>
> [AVHWDeviceContext @ 0x562dd8ad6cc0] libva: va_getDriverName() failed
> with unknown libva error,driver_name=(null)
> [AVHWDeviceContext @ 0x562dd8ad6cc0] Failed to initialise VAAPI
> connection: -1 (unknown libva error).
>
>

When i've seen this it's caused by trying to run under Wayland.
Mark's code handles this, and opens VAAPI in a different way that
works.

Regards
Stuart

> Then later  same as Klaas
>
> Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
> Qt::WA_PaintOnScreen to exclude from backingstore sync)
> Attempted flush to non-raster surface QWidgetWindow(0x562dd85e7270,
> name="mainwindowWindow") of type QSurface::OpenGLSurface (consider using
> Qt::WA_PaintOnScreen to exclude from backingstore sync)
>
>
> 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

_______________________________________________
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 05/01/2020 21:51, Mark Kendall wrote:
> On Sun, 5 Jan 2020 at 21:02, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>> The Qt warnings have gone!
>
> Good - thanks for confirming.
>
>> While on the subject of error messages, there is one left in the
>> mythfrontend startup log, similar but not identical to the message
>> reported by Paul Harrison (one line before and one line after the
>> error messages included):
>>
>> 2020-01-05 21:46:26.212846 I MythCoreContext::CheckProtoVersion():
>> Using protocol version 91 BuzzOff
>> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
>> object file: No such file or directory
>
> I assume you mean the VAAPI message below?
>
> I'm slightly baffled by this - as it is an FFmpeg log message - and I
> don't see any associated/relevant MythTV logging...
>
> Can you attach a full log? I'm assuming you have VAAPI support
> compiled in. Are you using VAAPI? and is it still available after this
> log message?
>

It comes from an attempt to initialize the VAAPI library, it doesn't
matter if we do it, or if FFmpeg does it.

On wayland platforms, it won't initialize properly if passed an X
display (the wayland vaapi interface needs using).

You've already handled this situation by using /dev/dri/renderD128
device.


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

Hi Mark,

Stuart's answers are probably clear enough but I will attach the
configure log and the mythfrontend log to ticket #13548, it can be
relevant there also.
About the error message though, if it does not convey meaningful
information then it would be better if the message was not there....

Groetjes,
Klaas.

On Mon, 6 Jan 2020 at 17:48, Stuart Auchterlonie
<stuarta@squashedfrog.net> wrote:
>
> On 05/01/2020 21:51, Mark Kendall wrote:
> > On Sun, 5 Jan 2020 at 21:02, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
> >> The Qt warnings have gone!
> >
> > Good - thanks for confirming.
> >
> >> While on the subject of error messages, there is one left in the
> >> mythfrontend startup log, similar but not identical to the message
> >> reported by Paul Harrison (one line before and one line after the
> >> error messages included):
> >>
> >> 2020-01-05 21:46:26.212846 I MythCoreContext::CheckProtoVersion():
> >> Using protocol version 91 BuzzOff
> >> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
> >> object file: No such file or directory
> >
> > I assume you mean the VAAPI message below?
> >
> > I'm slightly baffled by this - as it is an FFmpeg log message - and I
> > don't see any associated/relevant MythTV logging...
> >
> > Can you attach a full log? I'm assuming you have VAAPI support
> > compiled in. Are you using VAAPI? and is it still available after this
> > log message?
> >
>
> It comes from an attempt to initialize the VAAPI library, it doesn't
> matter if we do it, or if FFmpeg does it.
>
> On wayland platforms, it won't initialize properly if passed an X
> display (the wayland vaapi interface needs using).
>
> You've already handled this situation by using /dev/dri/renderD128
> device.
>
>
> 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
_______________________________________________
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 Mon, 6 Jan 2020 at 21:45, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>
> Hi Mark,
>
> Stuart's answers are probably clear enough but I will attach the
> configure log and the mythfrontend log to ticket #13548, it can be
> relevant there also.
> About the error message though, if it does not convey meaningful
> information then it would be better if the message was not there....

Klaas

The message is telling you that the VAAPI functionality check failed
and as a result you are using software playback.

Assuming you are using wayland, I'm fairly sure the issue is that you
don't have the vaapi drm package installed. FFmpeg these days uses a
DRM connection first and only then falls back to trying an X11
connection.

What does 'grep -in vaapi_drm *' show when run from your mythtv source
directory?

If VAAPI DRM is available, it should show something like:-

config.h:389:#define HAVE_VAAPI_DRM 1
config.mak:547:HAVE_VAAPI_DRM=yes

Likewise 'apt search libva-drm' should tell you what packages are installed.

thanks and regards
Mark
_______________________________________________
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

Hi Mark,
>
> The message is telling you that the VAAPI functionality check failed
> and as a result you are using software playback.
>
> Assuming you are using wayland, I'm fairly sure the issue is that you
> don't have the vaapi drm package installed. FFmpeg these days uses a
> DRM connection first and only then falls back to trying an X11
> connection.
>
> What does 'grep -in vaapi_drm *' show when run from your mythtv source
> directory?
>
> If VAAPI DRM is available, it should show something like:-
>
> config.h:389:#define HAVE_VAAPI_DRM 1
> config.mak:547:HAVE_VAAPI_DRM=yes
>
> Likewise 'apt search libva-drm' should tell you what packages are installed.
>
I am using apparently x11 as indicated by the value of XDG_SESSION_TYPE.
The grep in mythtv/mythtv shows:
config.ep:1399: vaapi_drm
config.ep:5793:check_lib vaapi_drm va/va.h va/va_drm.h vaGetDisplayDRM
-lva -lva-drm
config.h:389:#define HAVE_VAAPI_DRM 1
config.mak:547:HAVE_VAAPI_DRM=yes
configure:1855: vaapi_drm
configure:6169: check_lib vaapi_drm "va/va.h va/va_drm.h"
vaGetDisplayDRM -lva -lva-drm

Which suggests that the VAAPI stuff should be there...
Maybe the use of x11 is the determining factor, as most people with
Fedora 31 seem to have Wayland as this is the current default IIRC. I
think I freshly installed this system with Fedora 29 when X11 was
still default, and have since then upgraded.

I just now installed this package;
$ sudo dnf install libva-utils
which gives us the vainfo command.
The vainfo output also gives errors:
[
klaas@modu mythtv]$ vainfo
libva info: VA-API version 1.6.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

The library /usr/lib64/dri/i965_drv_video.so is indeed not present and
I cannot find in which package it is hidden. If it exists.

Hope this helps!

Groetjes,
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 07/01/2020 21:46, Klaas de Waal wrote:
> Hi Mark,
>>
>> The message is telling you that the VAAPI functionality check failed
>> and as a result you are using software playback.
>>
>> Assuming you are using wayland, I'm fairly sure the issue is that you
>> don't have the vaapi drm package installed. FFmpeg these days uses a
>> DRM connection first and only then falls back to trying an X11
>> connection.
>>
>> What does 'grep -in vaapi_drm *' show when run from your mythtv source
>> directory?
>>
>> If VAAPI DRM is available, it should show something like:-
>>
>> config.h:389:#define HAVE_VAAPI_DRM 1
>> config.mak:547:HAVE_VAAPI_DRM=yes
>>
>> Likewise 'apt search libva-drm' should tell you what packages are installed.
>>
> I am using apparently x11 as indicated by the value of XDG_SESSION_TYPE.
> The grep in mythtv/mythtv shows:
> config.ep:1399: vaapi_drm
> config.ep:5793:check_lib vaapi_drm va/va.h va/va_drm.h vaGetDisplayDRM
> -lva -lva-drm
> config.h:389:#define HAVE_VAAPI_DRM 1
> config.mak:547:HAVE_VAAPI_DRM=yes
> configure:1855: vaapi_drm
> configure:6169: check_lib vaapi_drm "va/va.h va/va_drm.h"
> vaGetDisplayDRM -lva -lva-drm
>
> Which suggests that the VAAPI stuff should be there...
> Maybe the use of x11 is the determining factor, as most people with
> Fedora 31 seem to have Wayland as this is the current default IIRC. I
> think I freshly installed this system with Fedora 29 when X11 was
> still default, and have since then upgraded.
>
> I just now installed this package;
> $ sudo dnf install libva-utils
> which gives us the vainfo command.
> The vainfo output also gives errors:
> [
> klaas@modu mythtv]$ vainfo
> libva info: VA-API version 1.6.0
> libva info: va_getDriverName() returns 0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: va_openDriver() returns -1
> vaInitialize failed with error code -1 (unknown libva error),exit
>
> The library /usr/lib64/dri/i965_drv_video.so is indeed not present and
> I cannot find in which package it is hidden. If it exists.
>

The simplest way to check i've found is just to do

# ps -ef | grep -i wayland

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