2025/05/08

2025-05-08 01:21:43 +0200Kaladin(~Kaladin@157-131-203-96.fiber.dynamic.sonic.net) (Quit: Leaving)
2025-05-08 01:30:40 +0200Kaladin(~Kaladin@157-131-203-96.fiber.dynamic.sonic.net) Kaladin
2025-05-08 02:11:48 +0200rascasse_(~rascasse@user/diep) (Remote host closed the connection)
2025-05-08 02:12:07 +0200Kaladin(~Kaladin@157-131-203-96.fiber.dynamic.sonic.net) (Quit: Leaving)
2025-05-08 02:32:39 +0200Natch(~natch@c-92-34-7-158.bbcust.telenor.se) (Ping timeout: 260 seconds)
2025-05-08 02:35:59 +0200Natch(~natch@c-92-34-7-158.bbcust.telenor.se) Natch
2025-05-08 02:59:46 +0200thunderrd(~thunderrd@1.4.183.239) (Ping timeout: 252 seconds)
2025-05-08 03:03:20 +0200OftenFaded89(~OftenFade@user/tisktisk) (Quit: Client closed)
2025-05-08 03:10:29 +0200sajenim(~sajenim@user/sajenim) sajenim
2025-05-08 03:12:32 +0200thunderrd(~thunderrd@101.51.205.206) thunderrd
2025-05-08 04:22:01 +0200td_(~td@i5387091E.versanet.de) (Ping timeout: 252 seconds)
2025-05-08 04:23:49 +0200td_(~td@i53870937.versanet.de)
2025-05-08 08:14:33 +0200 <deebo> hmpf, still having issue where on startup mate-panel times out, for some reason xmonad takes a really long time to start, .xsession-errors seems to say it's not recompiled because nothing changed, but still takes ages for it to be active so that i can spawn a terminal
2025-05-08 08:28:16 +0200 <deebo> fixed a few issues to get less .xsession-errors logs, and there's on suspicious one with "xmonad: X11 error: BadAtom (invalid Atom parameter), request code=18, error code=5"
2025-05-08 08:53:24 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: leaving)
2025-05-08 09:23:09 +0200mc47(~yecinem@p200300ee0f09376482f36aef415a254e.dip0.t-ipconnect.de)