[mythtv-users] Can't start mythfrontend with TV off since moving to Intel graphics

Paul Gardiner lists at glidos.net
Wed Oct 28 12:01:20 UTC 2020


On 28/10/2020 11:16, Mark Kendall wrote:
> Paul
> 
> My gut feeling is that this is probably fixable (and indeed needs
> fixing) in the MythTV code.
> 
> The Qt code will use a default/dummy screen if nothing is connected at
> startup. It then detects when the new screen is connected (or powered
> on in this case).
> 
> There are various signals that we listen for in the MythTV code to
> identify when screens have been added/removed etc. See:-
> 
> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythui/mythdisplay.h#L52
> 
> The mythfrontend logs should show activity when any of the
> ScreenAdded, ScreenRemoved or PrimaryScreenChanged slots are
> triggered. The ScreenChanged slot may show activity - but only if the
> actual QScreen object has changed (this was written to handle moving
> the mythfrontend window from one screen to another - either
> programmatically or manually). If nothing else there should be a
> signal that the available geometry has changed when the monitor is
> connected.
> 
> I suggest gathering some logs with additional Qt logging to see what
> might be happening.
> 
> QT_LOGGING_RULES=qt.qpa.screen=true mythfrontend
> 
> I would try that with and without the custom EDID and leave it until
> the display has definitely turned on (i.e. to see if any Qt screen
> code is triggered)

It's great to hear that: means I don't have to even think about taking a 
look at the intel driver source. :-)

Any other arguments to specify to mythfrontend, or is that one addition 
for what you need logged?



More information about the mythtv-users mailing list