That indeed gives much more output, but not sure it gives more clarity as it ends with this:
-- 69930 xterm CALL mprotect(0xf4aab8c6000,0x1000,0x3<PROT_READ|PROT_WRITE>) 69930 xterm RET mprotect 0 69930 xterm CALL mprotect(0xf4aab8c6000,0x1000,0x1<PROT_READ) 69930 xterm RET mprotect 0 69930 xterm CALL munmap(0xf4aab8c6000,0x1000) 69930 xterm RET munmap 0 69930 xterm CALL exit(1) 77728 ksh PSIG SIGHUP SIG_DFL -- >From the output just before this the only thing that stands out to me is that it fails to find "/home/hge/.cache/fontconfig" as that returns an error for the unveil call and the writing of "xterm: unveil" in the .xsession-errors happens immediately after that. On Sun, 5 Sept 2021 at 20:44, Theo de Raadt <dera...@openbsd.org> wrote: > > It is setgid (privdrop) for utmp support, so ktrace stops reporting on > what the program is doing. If you temporarily chmod your utmp file a+w, > remove the setgid bit from the xterm binary, then you will likely be > able to ktrace further to get closer to identifying the issue. > > henkjan gersen <h.ger...@gmail.com> wrote: > > > Assuming I should run "ktrace -di xterm" it doesn't show any failure > > condition at the end, i.e. the last lines from the kdump are > > -- > > 90075 ktrace NAMI "/usr/X11R6/bin/xterm" > > 90075 ktrace ARGS > > [0] = "xterm" > > -- > > To me that last line looks like the process launches successfully, yet > > no xterm window shows. All errors that are shown before these lines > > are because it tries to locate xterm in various system-folders until > > it finds it in /usr/X11R6/bin > > > > @Dave: I'm running using snapshots, so it will take me some time to > > get to the stage where I can try your diff. I haven't gone through > > building xenocara before (aware that the FAQ describes how to do it). > > > > On Sun, 5 Sept 2021 at 15:12, Theo de Raadt <dera...@openbsd.org> wrote: > > > > > > henkjan gersen <h.ger...@gmail.com> wrote: > > > > > > > On this mornings snapshot that I just upgraded to I can no longer open > > > > an xterm window. Based on the .xsession-error this must be related to > > > > the unveil capabilities that got added last week as I see "xterm: > > > > unveil" appearing in that file. > > > > > > > > Can someone give a hint on what I'm missing to be able to open an > > > > xterm window again? > > > > > > ktrace -di, and kdump > > > > > > The idea is to spot a failure condition near the end. > > > > >
