-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screencast: Output is corrupt with DmaBuf Transport (v0.6.0+) #223
Comments
Heres some details:
Also for reference heres a list of intel releated packages on my system
Includes mesa package Also did notice a libva error, but I highly doubt that is related. If it is i can provide info. Hopefully the information i have provided here can help, if you need anything else, lmk. |
This sounds like a bug in chromium which is fixed and will be in the 105 release. You might be able to check this by using a chromium dev build from their website |
Do you have a crbug.com url for this bug? |
I just did a fresh build of fea4934 and I'm using this config: [screencast]
max_fps=60
chooser_cmd=slurp -f %o -or
chooser_type=none
cropmode=wlroots
region=1280,0:2560x1412
force_mod_linear=1 Result: GPU: AMD RX 5700 XT with I tried with and without OBS verbose log: https://obsproject.com/logs/LU053S1kMTqPI0W6 XDPW log:
|
If you see a corrupted image (abstract art) instead of the output of your screen using xdg-desktop-portal (xdpw) v 0.6.0 and later please provide:
force_mod_linear
is used)If the image is still corrupt with OBS please do the following:
Please build OBS from master, (or use the attached flatpak taken from the CI of obsproject/obs-studio#5377 [1])
and provide logs from the same session:
DEBUG
Log: eg. the output of/usr/lib/xdg-desktop-portal-wlr -r -l TRACE
--verbose
flag and either paste the log here or upload it via OBS and paste the URL here.The reason to ask for all that information is: DmaBufs depend highly on the used hardware and drivers. When the clients displays a corrupt image the issues can range from wrong negotiation of DmaBuf capabilities, to wrong API usage of clients or a driver bug.
This link can get invalid
[1]: https://github.com/obsproject/obs-studio/suites/7129787888/artifacts/283059476
The text was updated successfully, but these errors were encountered: