Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,310 events total
2025-02-06 08:42:19 alp__ joins (~alp@2001:861:8ca0:4940:c619:f7a3:d4b4:8e07)
2025-02-06 08:48:41 × piele quits (~piele@tbonesteak.creativeserver.net) (Quit: Ciao!)
2025-02-06 09:20:27 × ash3en quits (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Remote host closed the connection)
2025-02-06 09:21:40 ash3en joins (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207)
2025-02-06 09:44:33 × ash3en quits (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Ping timeout: 245 seconds)
2025-02-06 09:50:31 <Solid> geekosaur: I think EwmhDesktops is more liskin's turf, but I'll take a look later
2025-02-06 09:58:57 piele joins (~piele@tbonesteak.creativeserver.net)
2025-02-06 10:00:45 ash3en joins (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207)
2025-02-06 10:02:00 × piele quits (~piele@tbonesteak.creativeserver.net) (Client Quit)
2025-02-06 10:16:54 L29Ah joins (~L29Ah@wikipedia/L29Ah)
2025-02-06 10:33:04 × ChubaDuba quits (~ChubaDuba@5.165.176.233) (Quit: WeeChat 4.5.1)
2025-02-06 11:47:30 × tv quits (~tv@user/tv) (Read error: Connection reset by peer)
2025-02-06 12:21:59 × catman quits (~catman@user/catman) (Quit: WeeChat 4.5.1)
2025-02-06 12:25:47 catman joins (~catman@user/catman)
2025-02-06 12:50:13 L29Ah parts (~L29Ah@wikipedia/L29Ah) ()
2025-02-06 12:51:59 L29Ah joins (~L29Ah@wikipedia/L29Ah)
2025-02-06 13:00:26 × ash3en quits (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2025-02-06 13:36:26 rekahsoft joins (~rekahsoft@bras-base-orllon1103w-grc-10-142-112-184-232.dsl.bell.ca)
2025-02-06 13:49:34 yaslam joins (~yaslam@user/yaslam)
2025-02-06 13:56:30 tv joins (~tv@user/tv)
2025-02-06 14:03:33 L29Ah parts (~L29Ah@wikipedia/L29Ah) ()
2025-02-06 14:16:09 × yaslam quits (~yaslam@user/yaslam) (Ping timeout: 276 seconds)
2025-02-06 14:27:31 piele joins (~piele@eiseth.creativeserver.net)
2025-02-06 14:29:10 L29Ah joins (~L29Ah@wikipedia/L29Ah)
2025-02-06 14:31:14 × piele quits (~piele@eiseth.creativeserver.net) (Client Quit)
2025-02-06 14:33:51 × alp__ quits (~alp@2001:861:8ca0:4940:c619:f7a3:d4b4:8e07) (Remote host closed the connection)
2025-02-06 14:34:09 alp__ joins (~alp@2001:861:8ca0:4940:c852:f016:ee1c:5cf)
2025-02-06 14:35:53 piele joins (~piele@eiseth.creativeserver.net)
2025-02-06 15:56:39 × mc47 quits (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 260 seconds)
2025-02-06 16:07:47 <ectospasm> I am having a problem with XMonad. It exits without an error code (I see nothing about it in xmonad.errors) when I try to bring up a prompt to change or send the current window to another workspace.
2025-02-06 16:08:00 <ectospasm> i hadn't made any changes to xmonad
2025-02-06 16:08:19 <ectospasm> xmonad.hs in a while
2025-02-06 16:08:35 <ectospasm> I think it has something to do with fonts
2025-02-06 16:10:04 <ectospasm> There are two places in xmonad.hs where I refer to Xft fonts, and I changed 'xft' to 'pango' and the crashing/exiting stopped (but my prompt hotkeys don't work, either).
2025-02-06 16:10:29 <ectospasm> This started after an upgrade of my Arch Linux laptop
2025-02-06 16:11:02 <ectospasm> The only thing I saw that got upgraded was fontconfig, but I don't know how to fix this.
2025-02-06 16:12:27 <ectospasm> https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs
2025-02-06 16:15:29 <ectospasm> xmonad 0.18.0-27 xmonad-contrib 0.18.1-12 xmonad-utils 0.1.3.3-258
2025-02-06 16:16:49 <ectospasm> It looks like my XMonad packages were upgraded as well.
2025-02-06 17:12:43 <L29Ah> does it work if you build xmonad and its dependencies with cabal or stack or nix?
2025-02-06 17:25:27 × piele quits (~piele@eiseth.creativeserver.net) (Ping timeout: 246 seconds)
2025-02-06 17:30:08 × MrElendig quits (~Urist@archlinux/op/MrElendig) (Quit: aliens)
2025-02-06 17:31:31 MrElendig joins (~Urist@archlinux/op/MrElendig)
2025-02-06 17:47:50 ft joins (~ft@p3e9bcd97.dip0.t-ipconnect.de)
2025-02-06 17:52:06 yaslam joins (~yaslam@user/yaslam)
2025-02-06 18:30:57 piele joins (~piele@eiseth.creativeserver.net)
2025-02-06 18:34:00 × piele quits (~piele@eiseth.creativeserver.net) (Client Quit)
2025-02-06 18:40:38 <geekosaur> there's something you need to do after upgrading Arch packages to keep your xmonad config running, I have to check the wiki
2025-02-06 18:41:25 <geekosaur> see the boxed warning here https://wiki.archlinux.org/title/Xmonad#Installation
2025-02-06 19:41:58 ash3en joins (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207)
2025-02-06 20:45:03 × ash3en quits (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2025-02-06 22:12:36 × haskellbridge quits (~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection)
2025-02-06 22:13:22 <ectospasm> geekosaur: I actually recompile xmonad before I launch it every time. I have an alias stx='xmonad --recompile && startx &> ~/.Xsession-errors' when I start X.org, so I recompile every time.
2025-02-06 22:14:11 <ectospasm> L29Ah: Sorry, that's too much work to do, so I'm not going to try that.
2025-02-06 22:16:24 haskellbridge joins (~hackager@syn-024-093-192-219.res.spectrum.com)
2025-02-06 22:19:57 <geekosaur> then I would wonder if Arch (yet again) failed to recompile dependent libraries. `ldd ~/.xmonad/xmonad-x86_64-linux` (if you use XDG, `ldd ~/.cache/xmonad/xmonad-x86_64-linux`)
2025-02-06 22:23:13 <ectospasm> https://paste.rs/a5QkP
2025-02-06 22:24:50 <geekosaur> huh, that looks fine (although I have to wonder how TH got in there)
2025-02-06 22:25:27 <ectospasm> TH?
2025-02-06 22:25:33 <geekosaur> `xmonad.errors` won't contain runtime errors, it's for compile-time (`xmonad --rebuild`) errors
2025-02-06 22:25:38 <geekosaur> Template Haskell
2025-02-06 22:25:48 <ectospasm> Ah.
2025-02-06 22:26:06 <ectospasm> Yeah, My .Xsession.errors seems to show a few lines of this: <class 'Xlib.error.BadAccess'>: code = 10, resource_id = 1323, sequence_number = 37, major_opcode = 33, minor_opcode = 0
2025-02-06 22:26:19 <ectospasm> But I'm not sure if that's coming from XMonad or autokey
2025-02-06 22:26:29 <ectospasm> Let me post my .Xsession.errors, hold on.
2025-02-06 22:27:24 <ectospasm> https://paste.rs/apr8p
2025-02-06 22:27:37 <geekosaur> that's XUngrabServer, won't be xmonad
2025-02-06 22:28:02 <geekosaur> oh wait, wrong number 🙂
2025-02-06 22:28:07 <ectospasm> That's right after I trigger the exit. I'm having a hard time calling it a crash, but X completely dies.
2025-02-06 22:28:17 <geekosaur> 33 is XGrabKey
2025-02-06 22:28:57 <geekosaur> sounds like autokey, you'd get any xmonad errors about key grabs right up front. oh, and xmonad's X errors look different from that
2025-02-06 22:30:49 <geekosaur> xmonad is throwing BadAtom at startup with XChangeProperty, but is continuing
2025-02-06 22:31:15 <geekosaur> yeh, I see no xmonad errors there
2025-02-06 22:31:34 <ectospasm> The other thing I've noticed, is my dzen2 bar at the top isn't displaying the little battery and clock widgets I'm piping through dzen2.
2025-02-06 22:31:42 <geekosaur> but it's behaving a lot like xmonad crashed/dumped core, which is usually FFI
2025-02-06 22:32:14 <ectospasm> So I don't know where to look at the core dumps. I don't see any on ~/.xmonad, and I'm not sure where else they'd be.
2025-02-06 22:33:06 <ectospasm> None in ${HOME}
2025-02-06 22:33:18 <ectospasm> And I looked in /tmp and /run earlier, couldn't find any.
2025-02-06 22:34:28 <geekosaur> it would be in $HOME, but core dumps also need to be enabled (ulimit -c unlimited)
2025-02-06 22:35:07 <geekosaur> (there's also a sysctl thing but I hope they didn't use that, especially if it's sending it to some automated crash reporter that won't be smart enough to send it to us)
2025-02-06 22:35:57 <ectospasm> I'm not aware of anything Arch does like that, I'd be surprised if they did.
2025-02-06 22:36:05 <ectospasm> Stuff like that I'd have to explicitly set up.
2025-02-06 22:36:12 <geekosaur> I would too, actually
2025-02-06 22:36:24 <geekosaur> Fedora and Ubuntu do it, it's annoying
2025-02-06 22:36:39 <ectospasm> Yeah, but they have more staff to handle such things
2025-02-06 22:36:55 <geekosaur> doesn't mean either of them forward crash dumps to us
2025-02-06 22:37:13 <ectospasm> Let me try the ulimit thing...
2025-02-06 22:38:41 <geekosaur> you need to run that at boot before xmonad starts for it to be effective; I don't know how Arch allows you to do that
2025-02-06 22:39:01 <geekosaur> if you're using ~/.xsession / ~/.xinitrc then you can put it there
2025-02-06 22:39:04 <ectospasm> Run it at boot, or just before I launch X/xinit/xmonad?
2025-02-06 22:39:17 <geekosaur> the latter
2025-02-06 22:39:30 <geekosaur> (I mean, I would actually do the former because ugh)
2025-02-06 22:39:45 <ectospasm> Yeah, I killed X, ran `ulimit -c unlimited`, then my stx (startx) alias which recompiled xmonad before startx.
2025-02-06 22:39:50 <geekosaur> but also run `ulimit -a` in a shell to see what it currently is
2025-02-06 22:39:55 <ectospasm> I don't see a core dump in ${HOME}
2025-02-06 22:40:17 <ectospasm> yeah, it says `-c unlimited`
2025-02-06 22:42:40 <geekosaur> could you have your .xinitrc do `echo "xmonad exit $?" >> ~/.xsession-errors` right after running xmonad?
2025-02-06 22:42:53 <geekosaur> (or whatever file you're starting xmonad with)
2025-02-06 22:43:16 <ectospasm> Yeah, it's .xinitrc, so put it after the exec xmonad line?
2025-02-06 22:44:17 <geekosaur> also remove the `exec` so it'll actually get run

All times are in UTC.