"Unable to add DRM framebuffer" with mpv #2181
Comments
|
Does everything still work fine even though error messages are printed? |
|
I didn't test many other apps. But it seems mpv and sway still work fine, despite the error message. |
|
So this is just Sway trying to use direct scan-out and failing (falling back to regular composition). This is harmless, but the error messages could be improved. swaywm/sway#5010 is an attempt at reducing the noise. |
|
This happens with RetroArch and RPCS3 too, aren't they supposed to be able to use direct scan-out? Or maybe I'm confused as to what direct scan-out is :) |
|
Direct scan-out means that the display engine directly reads from the client's buffer, without the compositor needing to copy to an intermediate buffer. Whether direct scan-out is possible depends on the display engine capabilities and the buffer format/modifier used by the client. |
|
I think this didn't happen before though. Also if I switch to OpenGL in RetroArch it doesn't occur. |
|
This is still an issue, my sway.log grows to 2MB after a couple minutes session in RPCS3 or RetroArch. |
This avoids some log spam. Eventually when we wire up the atomic test commit this will take care of the other log spam referenced below. References: swaywm#5010 References: swaywm/wlroots#2181 Closes: swaywm/wlroots#2532
This avoids some log spam. Eventually when we wire up the atomic test commit this will take care of the other log spam referenced below. References: #5010 References: swaywm/wlroots#2181 Closes: swaywm/wlroots#2532
|
The error messages should have been downgraded to DEBUG now. |
mpv version: 0.32.0
wlroots version: 0.10.0.r124.gf72686c0-1 (up to f72686c)
sway version: sway version 1.4-726d187d (May 10 2020, branch 'master')
When mpv plays in fullscreen mode, lots of the following error messages are printed out.
mpv command:
sway-drm.log
Not sure if it is wlroots' problem or mpv's though.
The text was updated successfully, but these errors were encountered: