2024/10/02

2024-10-02 01:38:18 +0200kaskal-(~kaskal@213-147-165-35.nat.highway.webapn.at) (Quit: ZNC - https://znc.in)
2024-10-02 01:38:39 +0200kaskal(~kaskal@2001:4bb8:2af:db4a:8acd:a0ac:f117:1e24) kaskal
2024-10-02 04:20:15 +0200td_(~td@i5387093B.versanet.de) (Ping timeout: 252 seconds)
2024-10-02 04:22:15 +0200td_(~td@i5387093C.versanet.de)
2024-10-02 06:41:11 +0200ml|(~ml|@user/ml/x-5298235) (Ping timeout: 265 seconds)
2024-10-02 06:54:53 +0200ml|(~ml|@user/ml/x-5298235) ml|
2024-10-02 09:42:40 +0200catman(~catman@user/catman) (Read error: Connection reset by peer)
2024-10-02 09:47:53 +0200Digitteknohippie(~user@user/digit) Digit
2024-10-02 09:48:02 +0200Digit(~user@user/digit) (Ping timeout: 252 seconds)
2024-10-02 09:55:55 +0200DigitteknohippieDigit
2024-10-02 10:08:07 +0200ft(~ft@p4fc2acce.dip0.t-ipconnect.de) (Quit: leaving)
2024-10-02 10:16:43 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2024-10-02 10:36:06 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 276 seconds)
2024-10-02 11:10:29 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2024-10-02 11:54:41 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-10-02 11:55:12 +0200tv(~tv@user/tv) (Read error: Connection reset by peer)
2024-10-02 11:58:13 +0200tv(~tv@user/tv) tv
2024-10-02 14:11:47 +0200Node1(~Node1@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2)
2024-10-02 14:12:12 +0200Node1FoxOnSocks
2024-10-02 14:16:43 +0200 <FoxOnSocks> Hej, I'm encountering a "fun" problem. I've just setup my XMonad environment on a brand new Arch Linux install, from dotfiles I've been using for years and years, everything seems to work until....
2024-10-02 14:16:43 +0200 <FoxOnSocks> I launch my terminal (st), and it works fine, but then if I launch some applications or some commands, *sometimes*, it crashes the terminal. Right now if I run nvim, the st instance crashes.
2024-10-02 14:16:44 +0200 <FoxOnSocks> Now I would assume that this is an issue with st, but a) I haven't touched st, it's been working fine for years, and b) if I launch st from a terminal, it works fine.
2024-10-02 14:16:44 +0200 <FoxOnSocks> It only crashes when it's launched through an Xmonad shortcut as defined in my xmonad.hs.
2024-10-02 14:16:45 +0200 <FoxOnSocks> I did change the xmonad.hs a little to modify some hotkeys and suppress a warning, but I can't see why this would happen.
2024-10-02 14:16:45 +0200 <FoxOnSocks> https://github.com/bag-man/dotfiles/blob/master/xmonad/xmonad.hs
2024-10-02 14:16:46 +0200 <FoxOnSocks> Any help would be very appreciated, not sure where to start with this one tbh.
2024-10-02 14:20:02 +0200 <FoxOnSocks> I've also had inconsistencies with commands to be run in conjunction with launching Xmonad (traditionally with .xinitrc), I played around with .profile, but ended up putting commands in /etc/lemurs/wms/xmonad where I launch Xmonad. However sometimes it seems like they don't run, othertimes they do.
2024-10-02 14:25:27 +0200FoxOnSocks(~Node1@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2) (Quit: Client closed)
2024-10-02 14:26:38 +0200FoxOnSocks(~FoxOnSock@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2)
2024-10-02 15:09:45 +0200ash3en(~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) ash3en
2024-10-02 15:10:12 +0200ash3en(~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) (Remote host closed the connection)
2024-10-02 17:11:19 +0200ash3en(~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) ash3en
2024-10-02 17:11:41 +0200ash3en(~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) (Client Quit)
2024-10-02 18:08:06 +0200ft(~ft@p4fc2acce.dip0.t-ipconnect.de) ft
2024-10-02 18:08:22 +0200de-vri-es(~de-vri-es@voyager.de-vri.es) (Ping timeout: 244 seconds)
2024-10-02 18:51:41 +0200de-vri-es(~de-vri-es@voyager.de-vri.es) de-vri-es
2024-10-02 21:04:29 +0200FoxOnSocks(~FoxOnSock@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2) (Quit: Client closed)
2024-10-02 21:05:28 +0200FoxOnSocks(~FoxOnSock@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2)
2024-10-02 21:42:21 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net) Maeda
2024-10-02 22:16:41 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving)
2024-10-02 23:25:56 +0200FoxOnSocks(~FoxOnSock@2a00:801:4f3:fb9c:22d2:cc07:9cb3:2) (Quit: Client closed)