[Bug 286311] x11-wm/sway: fails to start on amdgpu after ports bb43067a6928

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286311

--- Comment #10 from Evgenii Khramtsov <2khramtsov@gmail.com> ---
git bisect with subproject/wlroots is a PITA due to upstream {API chase days
after,meson wlroots project rename}, and other temporary dev branch regressions
in the way, so with manual date based bisect of two projects I found out that:

https://github.com/swaywm/sway/commit/ae7c1b139a3c

is the first commit with "drm_gem_plane_helper_prepare_fb: explicit fence not
handled" that causes the message to appear, only black screen before
ae7c1b139a3c.

Thankfully sway could be kill -9 via ssh and vt(4) doesn't get garbled.
Afterwards "Requested backend configuration failed, searching for valid
fallbacks" to be seen.

> Does adjusting environ(7) with either WLR_DRM_NO_ATOMIC=1
> or WLR_DRM_FORCE_LIBLIFTOFF=1 help? Can you reproduce with tinywl
> (part of wlroots but not installed)?

I didn't try because WLR_RENDER_NO_EXPLICIT_SYNC works.

> Anyway, properly fixing this would require bisecting wlroots
> and likely help with testing upstream patches.

I know, really. I can report something to both wlroots and drm-kmod (not
today).

(In reply to Jan Beich from comment #8)
> What happened to tinywl testing? This is a bug tracker, not user forum to run away
> after finding a workaround or speculate with few details.

I feel like this comment is too authoritarian, so I would rather keep my scarce
free volunteer time today for something else, and would report upstream a day
later or so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.