sway-1.2_1 crashes

Greg floatboth at me.com
Fri Oct 11 07:10:25 UTC 2019



Fri Oct 11 00:34:22 GMT+03:00 2019 John Kennedy :
 
> On Thu, Oct 10, 2019 at 11:27:05AM -0700, John Kennedy wrote:
> 
>> I've had a good couple of days without starting firefox. I know GTK3 has some
>> wayland compile options, but firefox seems to depend on both GTK2 (which doesn't)
>> and GTK3 as far as pkg is concerned.
 
It shouldn't depend on gtk2, but the version in ports still includes NPAPI plugin support, which needs gtk2.
 
btw, I have Xwayland disabled completely on all my machines, Firefox works fine, the only thing that breaks without Xwayland is WebGL (some tests for the presence of GL are still only done using X, it is known and hopefully will be fixed soon). (But, compositing acceleration works, it's independent of that.)
 
> So, I think I've found at least one reliable (repeatable) way to crash sway.
> It makes it to ~17 or (tiled) urxvt windows so before sway "crashes". IE,
> bails out to virtual terminal (where I can log in remotely and run vidcontrol
> to get my original console). I've done that about 8 times in a row.
 
> It died about 17 debugging lines into a ~226-line series for opening a urxvt window.
 
> xwayland-1.19.1_11,1 X Clients under Wayland
 
I would not be surprised if that outdated version of Xw we have in ports is causing extra problems that people don't see on Linux..
 
there is xwayland 1.20 in some branch of ports on the FreeBSDDesktop GitHub, you could try that



More information about the freebsd-x11 mailing list