
On top of known good 0.13 from ports tree first. Previous CFT didn't get a lot of feedback and was mostly to kill time waiting for wlroots (not sway) release.ĭid a shortcut before bisecting: reverted wlroots-related commits and applied > Why not a CFT on freebsd-x11 mailing list before merging this? Vulkan state wasn't clear but upstream rebased just before 0.14.0 Before wlroots 0.14.0 there was supposed to be 0.13.1, see All cherry-picks were tested months ago Sway isn't the only wlroots consumer, so I can't avoid patching
#Cgi texture flickery upgrade#
> why did you upgrade wlroots to 0.14 when this is not even merged (In reply to Evgeniy Khramtsov from comment #10) If it doesn't help report upstream with debug logs attached. I'd try updating sway 1.6.1/1.7 (not released yet, so use for now). I don't see this locally on Skylake (0x1912) with drm-devel-kmod. Likely exposed by Maybe a bug in drm-kmod or a corner case in sway/wlroots that's specific to your setup. (In reply to Evgeniy Khramtsov from comment #9)
#Cgi texture flickery update#
Maybe related to wlroots update because VULKAN option doesn't touch OPENGL code. I've downgraded to sway-1.6_3 but can't reproduce. > Assertion failed (width > 0), function wlr_texture_from_pixels, sometimes sway crashes after starting Firefox both (In reply to Evgeniy Khramtsov from comment #5)
#Cgi texture flickery drivers#
Without KMS one would need to resort to framebuffer (via /dev/ttyv0) similar to īoth renderers are currenly mainly for debugging wlroots, its consumers, GPU drivers and downstream integration i.e., for experiments. WLR_RENDERER=pixman maybe more stable but probably still requires drm-kmod. Try running forcing Xwayland via "env -u WAYLAND_DISPLAY" or "env GDK_BACKEND=x11 WINIT_UNIX_BACKEND=x11". Wayland-native Vulkan *clients* are also currently broken, reported in > flickering while scrolling in alacritty. > Z-fighting flickering artifacts in Firefox > Removing assert gets me the desktop comment 3 was late because I mainly dogfood Sway from the development branch, so when landing forgot to test runtime inside jail.

(In reply to Evgeniy Khramtsov from comment #4) A commit in branch main references this bug:Ĭommit 507dbffa521a9ca9e5a2baacc81262b9bb9da13a
