Stefan Hagen <[email protected]> writes: > Hi Amit, > > Amit Kulkarni wrote (2022-04-02 00:14 CEST): >> ---------- Forwarded message --------- >> From: Ashlen <[email protected]> >> Date: Fri, Apr 1, 2022 at 1:37 PM >> Subject: removing libutil.so.15.1 and libX11.so.17.1 per sysclean(8) >> breaks xmonad(1) >> To: <[email protected]> >> >> >> Hi, I'm on this snapshot with updated packages: >> >> >> $ sysctl -n kern.version >> OpenBSD 7.1 (GENERIC.MP) #454: Thu Mar 31 09:28:09 MDT 2022 >> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> >> >> sysclean(8) from ports recommends to delete >> /usr/X11R6/lib/libX11.so.17.1 and /usr/lib/libutil.so.15.1 but if these >> files are removed, xmonad(1) will fail to start and it quits back to >> xenodm(1) login. These are the relevant messages in ~/.xsession-errors >> (I've seen both cause this).
Yes, I hit this too. I believe Stefan's diagnosis and the suggested workaround is correct. I don't see an easy way to prevent this problem from recurring considering xmonad configuration mechanism of rebuilding the binary and stashing into the home dir. Some kind of static-linking monstrosity might be an option. If somebody finds a recipe, feel free to suggest an update to ports/x11/xmonad/files/build Thanks Greg
