Re: sway-1.2_1 crashes

John Kennedy <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
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.

  So, I think I've found at least one reliable (repeatable) way to crash sway.

  Starting up sway, I pop one floating window (xterm).  Run this little script:

	#!/bin/sh

	for y in 0 1 # 2 3 4 5 6 7 8 9
	    do
	    for x in 0 1 2 3 4 5 6 7 8 9
		do
			urxvt &
			echo $y $x
			sleep 1
		done
	    done

  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.

    [from `sway -d']
	...
	2019-10-10 14:06:10 - [xwayland/xwm.c:941] XCB_MAP_NOTIFY (41943047)
	2019-10-10 14:06:10 - [xwayland/xwm.c:1206] XCB_CLIENT_MESSAGE (41943047)
	2019-10-10 14:06:10 - [types/wlr_surface.c:609] New wlr_surface 0x80483b700 (res 0x803ab4480)
	2019-10-10 14:06:10 - [xwayland/xwm.c:1375] New xwayland surface: 0x80483b700
	2019-10-10 14:06:10 - [xwayland/xwm.c:391] XCB_ATOM_WM_CLASS: urxvt URxvt
	2019-10-10 14:06:10 - [xwayland/xwm.c:441] XCB_ATOM_WM_NAME: urxvt
	2019-10-10 14:06:10 - [xwayland/xwm.c:525] WM_PROTOCOLS (2)
	2019-10-10 14:06:10 - [xwayland/xwm.c:555] WM_HINTS (9)
	2019-10-10 14:06:10 - [xwayland/xwm.c:607] WM_NORMAL_HINTS (18)
	2019-10-10 14:06:10 - [xwayland/xwm.c:441] XCB_ATOM_WM_NAME: urxvt
	2019-10-10 14:06:10 - [xwayland/xwm.c:479] NET_WM_PID 7257
	(EE) 
	Fatal server error:
	(EE) failed to read Wayland events: Broken pipe
	(EE) 
	xterm: fatal IO error 35 (Resource temporarily unavailable) or KillClient on X server ":0"
	Segmentation fault

  It died about 17 debugging lines into a ~226-line series for opening a urxvt window.

  If you run it without the sleep, it'll complain that the X display isn't available but
not crash, at least in my simple test of ~20 runs.

    [pkg info | grep -e sway- -e wlroot -e wayland]
	sway-1.2_3                     i3-compatible Wayland compositor
	wayland-1.16.0_1               Wayland composite "server"
	wayland-protocols-1.17         Wayland protocols
	wlroots-0.8.1                  Modular Wayland compositor library
	xwayland-1.19.1_11,1           X Clients under Wayland

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.