Re: FYI: new X server in -current, among other X things

["David H. Gutteridge" <david%gutteridge.ca@localhost>]

On Fri, 15 Jul 2022 at 15:12:07 +1000, matthew green wrote:
> i've updated most of xsrc to their latest versions.
> fontconfig and Mesa are remaining.  i've tested the
> new code on amd64 and arm64, and built several ports
> to confirm they still build.  the biggest change is
> the new xorg-server.
> 
> there are probably a few build issues left to find
> across all ports, and perhaps some run-time ones too
> but basic testing looks fine for me.
> 
> please send-pr or email here if you find problems.

TL;DR: after upgrading via the sets available from releng builds from
July 16th (http://releng.netbsd.org/builds/HEAD/202207160630Z) I'm not
able to start X on amd64 with i915 graphics. Separately, there may be
issues with libX11 1.8.1 where clients will hang due to recursive locks
occurring.

I haven't had time to look into this in any detail, but after upgrading
kernel and userland to the July 16th sets (and running etcupgrade), I'm
now unable to start any window manager. I get the following:

[   378.027] (EE) 
[   378.027] (EE) Backtrace:
[   378.033] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x44) [0x1467d46d5]
[   378.033] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x79) [0x1467d0465]
[   378.033] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0) [0x75b46379c930]
[   378.034] (EE) 
[   378.034] (EE) Segmentation fault at address 0x0
[   378.034] (EE) 
Fatal server error:
[   378.034] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   378.034] (EE) 
[   378.034] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   378.034] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   378.034] (EE) 
[   378.053] (EE) Server terminated with error (1). Closing log file.

This happens with ctwm as part of the base installation, as well as with
other pre-existing window managers and such from pkgsrc built against
9.99.97.

Separately, libX11 added a feature called "thread safety constructor"
which we have enabled. It can cause hangs with X11 clients that aren't
coded safely. This did include xfce4-settings from Xfce until the
version I pushed to pkgsrc a couple of days ago (4.16.3). I believe
LXDE is also affected, but haven't had time to deal with it yet. Not
sure about any other DEs or X clients. (I'm not able to test at the
moment, of course.)

Regards,

Dave