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)
2025-05-08 12:23:56 +0200LearsLeary
2025-05-08 12:45:37 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2025-05-08 13:31:04 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-05-08 14:24:20 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 252 seconds)
2025-05-08 14:43:58 +0200Digitteknohippie(~user@69.47.7.51.dyn.plus.net)
2025-05-08 14:44:07 +0200Digit(~user@69.47.7.51.dyn.plus.net) (Ping timeout: 252 seconds)
2025-05-08 15:13:29 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-05-08 15:18:46 +0200zawaken(~zawaken@user/zawaken) (Quit: ZNC - https://znc.in)
2025-05-08 15:19:12 +0200zawaken(~zawaken@user/zawaken) zawaken
2025-05-08 15:38:49 +0200 <geekosaur> not sure how you're integrated with MATE, in my case xmonad can take a long time to start if I forgot to rebuild it and dependencies changed (dbus drags in a lot of crap) but the rest of MATE starts while it's waiting.
2025-05-08 16:45:41 +0200OftenFaded(~OftenFade@user/tisktisk) (Quit: OftenFaded)
2025-05-08 17:36:22 +0200 <deebo> i just have a .local/share/applications/xmonad.desktop + xmonad as the wm in org/mate/desktop/whatever
2025-05-08 17:36:49 +0200mc47(~yecinem@p200300ee0f09376482f36aef415a254e.dip0.t-ipconnect.de) (Ping timeout: 252 seconds)
2025-05-08 17:44:32 +0200 <geekosaur> interesting
2025-05-08 17:45:07 +0200 <geekosaur> mate-panel starts independently of xmonad for me and is usually running before xmonad starts; the log applet says "Waiting for xmonad" until xmonad starts up and sends its first update
2025-05-08 17:49:26 +0200 <deebo> yeah i actually started reading the code for 'mate-session', looks like all it does is get the values from dconf and then runs the defined panel, wm, file manager etc (if enabled)
2025-05-08 17:50:09 +0200 <deebo> so nto really sure what's going on, especially since xmonad seems to log nothing has changed so build is skipped
2025-05-08 17:50:14 +0200 <deebo> something's just hanging
2025-05-08 18:13:19 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 245 seconds)
2025-05-08 18:15:23 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-05-08 18:39:42 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-05-08 19:10:01 +0200 <deebo> enabled org.mate.debug in dconf and it just started working, for no apparent reason
2025-05-08 19:10:28 +0200 <deebo> teaching sand to think was a mistake
2025-05-08 19:11:15 +0200 <deebo> but with external monitor the applet doesnt do anything, even though i can see the messages in dbus