This is sort of a weird one. Background is that I have a laptop with a bunch of VMs all running OpenBSD, now 6.6 (thanks!). The host runs X and one of the VMs runs the window manager which can then log into other VMs (or the host) to do whatever. My development environment, named void, is one those VMs.
So far so strange. It's my setup and I like it. To run X apps, XAuthority credentials are banded about. All of the VMs have no problem with this except void, on which xauth segfaults. The login process when forwarding X credetials is essentially: var=$(xauth list $DISPLAY) ssh $remote xauth add $var ssh $remote DISPLAY=$DISPLAY $thing The strange thing is that with a few identical VMs running on this host, only on one of them does xauth segfault. All have today been upgraded to 6.6 and the fault was present on 6.5 too (I ignored it because I don't really need X there and hoped it would Just Go Away; it didn't). OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@chicken$ xauth list drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce [ksh]flask@chicken$ ssh void OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@void$ xauth add drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce /usr/X11R6/bin/xauth: file /home/flask/.Xauthority does not exist Segmentation fault (core dumped) [ksh]flask@void$ ^D [ksh]flask@chicken$ ssh shelob OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 [ksh]flask@shelob$ xauth add drogo.datum:0 MIT-MAGIC-COOKIE-1 86963dd9ee88bbfcc9eb66846b9cf4ce [ksh]flask@shelob$ I don't even know where to begin with this one (well I have some places to start looking but the fact that the otherwise-identical VMs react differently tells me this might be something deeper than the obvious so I'm waiting). I *think* this worked once but I can't be sure if I just didn't notice it failing. If nothing else I'll get around to figuring out how to build individual xenocara components and then step through the process to figure out what's broken in xauth but before I get to that I thought I'd see if anyone more familiar with these systems has any ideas. Matthew
