| 2025-02-06 02:35:17 +0000 | rekahsoft | (~rekahsoft@142.112.184.232) (Ping timeout: 244 seconds) |
| 2025-02-06 04:02:48 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 268 seconds) |
| 2025-02-06 04:08:12 +0000 | ChubaDuba | (~ChubaDuba@5.165.176.233) ChubaDuba |
| 2025-02-06 06:39:13 +0000 | alp | (~alp@2001:861:8ca0:4940:a52d:a41b:3770:b2af) (Remote host closed the connection) |
| 2025-02-06 06:39:31 +0000 | alp | (~alp@2001:861:8ca0:4940:e0b0:d5fb:93ef:4ef8) |
| 2025-02-06 06:40:54 +0000 | alp | (~alp@2001:861:8ca0:4940:e0b0:d5fb:93ef:4ef8) (Remote host closed the connection) |
| 2025-02-06 06:41:13 +0000 | alp | (~alp@2001:861:8ca0:4940:7eb3:2e6e:7dc9:4f15) |
| 2025-02-06 06:42:36 +0000 | alp | (~alp@2001:861:8ca0:4940:7eb3:2e6e:7dc9:4f15) (Remote host closed the connection) |
| 2025-02-06 06:42:53 +0000 | alp | (~alp@2001:861:8ca0:4940:3d30:574c:e91e:fee7) |
| 2025-02-06 06:44:19 +0000 | alp | (~alp@2001:861:8ca0:4940:3d30:574c:e91e:fee7) (Remote host closed the connection) |
| 2025-02-06 06:44:36 +0000 | alp | (~alp@2001:861:8ca0:4940:f75c:8158:a534:1f8a) |
| 2025-02-06 06:46:01 +0000 | alp | (~alp@2001:861:8ca0:4940:f75c:8158:a534:1f8a) (Remote host closed the connection) |
| 2025-02-06 06:46:18 +0000 | alp | (~alp@2001:861:8ca0:4940:2afa:c238:f26:8e7f) |
| 2025-02-06 06:48:01 +0000 | alp_ | (~alp@2001:861:8ca0:4940:9b95:20d:aabb:ced3) |
| 2025-02-06 06:49:25 +0000 | alp_ | (~alp@2001:861:8ca0:4940:9b95:20d:aabb:ced3) (Remote host closed the connection) |
| 2025-02-06 06:49:42 +0000 | alp_ | (~alp@2001:861:8ca0:4940:f903:6c8:e9e2:1b2b) |
| 2025-02-06 06:51:19 +0000 | alp | (~alp@2001:861:8ca0:4940:2afa:c238:f26:8e7f) (Ping timeout: 252 seconds) |
| 2025-02-06 06:51:26 +0000 | alp__ | (~alp@2001:861:8ca0:4940:5403:7c5f:5e1b:67a6) |
| 2025-02-06 06:54:37 +0000 | alp_ | (~alp@2001:861:8ca0:4940:f903:6c8:e9e2:1b2b) (Ping timeout: 252 seconds) |
| 2025-02-06 06:56:27 +0000 | alp__ | (~alp@2001:861:8ca0:4940:5403:7c5f:5e1b:67a6) (Ping timeout: 252 seconds) |
| 2025-02-06 07:10:50 +0000 | ft | (~ft@p3e9bcd97.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-02-06 08:38:42 +0000 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) |
| 2025-02-06 08:39:01 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-02-06 08:42:19 +0000 | alp__ | (~alp@2001:861:8ca0:4940:c619:f7a3:d4b4:8e07) |
| 2025-02-06 08:48:41 +0000 | piele | (~piele@tbonesteak.creativeserver.net) (Quit: Ciao!) |
| 2025-02-06 09:20:27 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Remote host closed the connection) |
| 2025-02-06 09:21:40 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-02-06 09:44:33 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Ping timeout: 245 seconds) |
| 2025-02-06 09:50:31 +0000 | <Solid> | geekosaur: I think EwmhDesktops is more liskin's turf, but I'll take a look later |
| 2025-02-06 09:58:57 +0000 | piele | (~piele@tbonesteak.creativeserver.net) piele |
| 2025-02-06 10:00:45 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-02-06 10:02:00 +0000 | piele | (~piele@tbonesteak.creativeserver.net) (Client Quit) |
| 2025-02-06 10:16:54 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-02-06 10:33:04 +0000 | ChubaDuba | (~ChubaDuba@5.165.176.233) (Quit: WeeChat 4.5.1) |
| 2025-02-06 11:47:30 +0000 | tv | (~tv@user/tv) (Read error: Connection reset by peer) |
| 2025-02-06 12:21:59 +0000 | catman | (~catman@user/catman) (Quit: WeeChat 4.5.1) |
| 2025-02-06 12:25:47 +0000 | catman | (~catman@user/catman) catman |
| 2025-02-06 12:50:13 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2025-02-06 12:51:59 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-02-06 13:00:26 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2025-02-06 13:36:26 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1103w-grc-10-142-112-184-232.dsl.bell.ca) rekahsoft |
| 2025-02-06 13:49:34 +0000 | yaslam | (~yaslam@user/yaslam) yaslam |
| 2025-02-06 13:56:30 +0000 | tv | (~tv@user/tv) tv |
| 2025-02-06 14:03:33 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2025-02-06 14:16:09 +0000 | yaslam | (~yaslam@user/yaslam) (Ping timeout: 276 seconds) |
| 2025-02-06 14:27:31 +0000 | piele | (~piele@eiseth.creativeserver.net) piele |
| 2025-02-06 14:29:10 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-02-06 14:31:14 +0000 | piele | (~piele@eiseth.creativeserver.net) (Client Quit) |
| 2025-02-06 14:33:51 +0000 | alp__ | (~alp@2001:861:8ca0:4940:c619:f7a3:d4b4:8e07) (Remote host closed the connection) |
| 2025-02-06 14:34:09 +0000 | alp__ | (~alp@2001:861:8ca0:4940:c852:f016:ee1c:5cf) |
| 2025-02-06 14:35:53 +0000 | piele | (~piele@eiseth.creativeserver.net) piele |
| 2025-02-06 15:56:39 +0000 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 260 seconds) |
| 2025-02-06 16:07:47 +0000 | <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 +0000 | <ectospasm> | i hadn't made any changes to xmonad |
| 2025-02-06 16:08:19 +0000 | <ectospasm> | xmonad.hs in a while |
| 2025-02-06 16:08:35 +0000 | <ectospasm> | I think it has something to do with fonts |
| 2025-02-06 16:10:04 +0000 | <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 +0000 | <ectospasm> | This started after an upgrade of my Arch Linux laptop |
| 2025-02-06 16:11:02 +0000 | <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 +0000 | <ectospasm> | https://git.eldon.me/trey/XMonad/src/branch/master/xmonad.hs |
| 2025-02-06 16:15:29 +0000 | <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 +0000 | <ectospasm> | It looks like my XMonad packages were upgraded as well. |
| 2025-02-06 17:12:43 +0000 | <L29Ah> | does it work if you build xmonad and its dependencies with cabal or stack or nix? |
| 2025-02-06 17:25:27 +0000 | piele | (~piele@eiseth.creativeserver.net) (Ping timeout: 246 seconds) |
| 2025-02-06 17:30:08 +0000 | MrElendig | (~Urist@archlinux/op/MrElendig) (Quit: aliens) |
| 2025-02-06 17:31:31 +0000 | MrElendig | (~Urist@archlinux/op/MrElendig) MrElendig |
| 2025-02-06 17:47:50 +0000 | ft | (~ft@p3e9bcd97.dip0.t-ipconnect.de) ft |
| 2025-02-06 17:52:06 +0000 | yaslam | (~yaslam@user/yaslam) yaslam |
| 2025-02-06 18:30:57 +0000 | piele | (~piele@eiseth.creativeserver.net) |
| 2025-02-06 18:34:00 +0000 | piele | (~piele@eiseth.creativeserver.net) (Client Quit) |
| 2025-02-06 18:40:38 +0000 | <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 +0000 | <geekosaur> | see the boxed warning here https://wiki.archlinux.org/title/Xmonad#Installation |
| 2025-02-06 19:41:58 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-02-06 20:45:03 +0000 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2025-02-06 22:12:36 +0000 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection) |
| 2025-02-06 22:13:22 +0000 | <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 +0000 | <ectospasm> | L29Ah: Sorry, that's too much work to do, so I'm not going to try that. |
| 2025-02-06 22:16:24 +0000 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) hackager |
| 2025-02-06 22:19:57 +0000 | <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 +0000 | <ectospasm> | https://paste.rs/a5QkP |
| 2025-02-06 22:24:50 +0000 | <geekosaur> | huh, that looks fine (although I have to wonder how TH got in there) |
| 2025-02-06 22:25:27 +0000 | <ectospasm> | TH? |
| 2025-02-06 22:25:33 +0000 | <geekosaur> | `xmonad.errors` won't contain runtime errors, it's for compile-time (`xmonad --rebuild`) errors |
| 2025-02-06 22:25:38 +0000 | <geekosaur> | Template Haskell |
| 2025-02-06 22:25:48 +0000 | <ectospasm> | Ah. |
| 2025-02-06 22:26:06 +0000 | <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 +0000 | <ectospasm> | But I'm not sure if that's coming from XMonad or autokey |
| 2025-02-06 22:26:29 +0000 | <ectospasm> | Let me post my .Xsession.errors, hold on. |
| 2025-02-06 22:27:24 +0000 | <ectospasm> | https://paste.rs/apr8p |
| 2025-02-06 22:27:37 +0000 | <geekosaur> | that's XUngrabServer, won't be xmonad |
| 2025-02-06 22:28:02 +0000 | <geekosaur> | oh wait, wrong number 🙂 |
| 2025-02-06 22:28:07 +0000 | <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 +0000 | <geekosaur> | 33 is XGrabKey |
| 2025-02-06 22:28:57 +0000 | <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 +0000 | <geekosaur> | xmonad is throwing BadAtom at startup with XChangeProperty, but is continuing |
| 2025-02-06 22:31:15 +0000 | <geekosaur> | yeh, I see no xmonad errors there |
| 2025-02-06 22:31:34 +0000 | <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 +0000 | <geekosaur> | but it's behaving a lot like xmonad crashed/dumped core, which is usually FFI |
| 2025-02-06 22:32:14 +0000 | <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 +0000 | <ectospasm> | None in ${HOME} |
| 2025-02-06 22:33:18 +0000 | <ectospasm> | And I looked in /tmp and /run earlier, couldn't find any. |
| 2025-02-06 22:34:28 +0000 | <geekosaur> | it would be in $HOME, but core dumps also need to be enabled (ulimit -c unlimited) |
| 2025-02-06 22:35:07 +0000 | <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 +0000 | <ectospasm> | I'm not aware of anything Arch does like that, I'd be surprised if they did. |
| 2025-02-06 22:36:05 +0000 | <ectospasm> | Stuff like that I'd have to explicitly set up. |
| 2025-02-06 22:36:12 +0000 | <geekosaur> | I would too, actually |
| 2025-02-06 22:36:24 +0000 | <geekosaur> | Fedora and Ubuntu do it, it's annoying |
| 2025-02-06 22:36:39 +0000 | <ectospasm> | Yeah, but they have more staff to handle such things |
| 2025-02-06 22:36:55 +0000 | <geekosaur> | doesn't mean either of them forward crash dumps to us |
| 2025-02-06 22:37:13 +0000 | <ectospasm> | Let me try the ulimit thing... |
| 2025-02-06 22:38:41 +0000 | <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 +0000 | <geekosaur> | if you're using ~/.xsession / ~/.xinitrc then you can put it there |
| 2025-02-06 22:39:04 +0000 | <ectospasm> | Run it at boot, or just before I launch X/xinit/xmonad? |
| 2025-02-06 22:39:17 +0000 | <geekosaur> | the latter |
| 2025-02-06 22:39:30 +0000 | <geekosaur> | (I mean, I would actually do the former because ugh) |
| 2025-02-06 22:39:45 +0000 | <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 +0000 | <geekosaur> | but also run `ulimit -a` in a shell to see what it currently is |
| 2025-02-06 22:39:55 +0000 | <ectospasm> | I don't see a core dump in ${HOME} |
| 2025-02-06 22:40:17 +0000 | <ectospasm> | yeah, it says `-c unlimited` |
| 2025-02-06 22:42:40 +0000 | <geekosaur> | could you have your .xinitrc do `echo "xmonad exit $?" >> ~/.xsession-errors` right after running xmonad? |
| 2025-02-06 22:42:53 +0000 | <geekosaur> | (or whatever file you're starting xmonad with) |
| 2025-02-06 22:43:16 +0000 | <ectospasm> | Yeah, it's .xinitrc, so put it after the exec xmonad line? |
| 2025-02-06 22:44:17 +0000 | <geekosaur> | also remove the `exec` so it'll actually get run |
| 2025-02-06 22:44:31 +0000 | <ectospasm> | OK |
| 2025-02-06 22:44:44 +0000 | <geekosaur> | (leave the `xmonad` obviously, we just don't want .xinitrc to replace itself with xmonad and not run the diagnostic line) |
| 2025-02-06 22:54:13 +0000 | <ectospasm> | Yep, so it's exit status 139, and here's the output of .Xsession-errors: https://paste.rs/gdJwA |
| 2025-02-06 22:54:26 +0000 | <ectospasm> | So xmonad is dumping core, I just don't know where the core file is. |
| 2025-02-06 22:55:15 +0000 | <geekosaur> | unless you're doing something weird in .xinitrc it's $HOME |
| 2025-02-06 22:55:21 +0000 | <geekosaur> | xmonad itself doesn't change directory |
| 2025-02-06 23:00:21 +0000 | <ectospasm> | Hmmm, do you know what the core dump might be named? I'm running `ls -altr`, so I figured the latest files (including the core dump) would be near the bottom. |
| 2025-02-06 23:00:37 +0000 | <ectospasm> | I also don't find anything with 'core' or 'dump' in the filename. |
| 2025-02-06 23:07:59 +0000 | <geekosaur> | it should just be `core` |
| 2025-02-06 23:08:52 +0000 | <ectospasm> | according to this: https://wiki.archlinux.org/title/Core_dump#Where_do_they_go?, they're in /var/lib/systemd/coredump/. Sure enough, there's a bunch in there for xmonad. |
| 2025-02-06 23:08:53 +0000 | <geekosaur> | possibly `core.somenumber` (which would be the pid) |
| 2025-02-06 23:09:07 +0000 | <geekosaur> | ah, so they do play sysctl games |
| 2025-02-06 23:09:20 +0000 | <ectospasm> | It appears so. |
| 2025-02-06 23:09:38 +0000 | <ectospasm> | Seems it's tied into systemd, which I appreciate. |
| 2025-02-06 23:09:45 +0000 | <ectospasm> | (I'm a fan of systemd) |
| 2025-02-06 23:09:52 +0000 | <ectospasm> | Or an apologist, if you will. |
| 2025-02-06 23:10:03 +0000 | <ectospasm> | But not here to talk about that. |
| 2025-02-06 23:10:40 +0000 | <ectospasm> | So, I'm a bit apprehensive about sharing that core dump. Any hints on how to review it? This is starting to get beyond my skillset (if using XMonad wasn't already) |
| 2025-02-06 23:12:53 +0000 | <geekosaur> | `gdb /path/to/xmonad-x86_64-linux /path/to/coredump` then `bt` |
| 2025-02-06 23:13:23 +0000 | <geekosaur> | but I'm not sure it'll be helpful, Haskell backtraces are wonky to start with and it's almost certainly built without debug information |
| 2025-02-06 23:13:39 +0000 | <geekosaur> | but if it's in an FFI call then it should at least show that |
| 2025-02-06 23:13:47 +0000 | <ectospasm> | FFI? |
| 2025-02-06 23:15:21 +0000 | <geekosaur> | foreign function interface |
| 2025-02-06 23:15:41 +0000 | <geekosaur> | we call out to C functions for practically everything, from X server calls, fonts, etc. |
| 2025-02-06 23:19:11 +0000 | <ectospasm> | OK |
| 2025-02-06 23:19:22 +0000 | <ectospasm> | Yeah, this uses coredumpctl to analyze core dumps. |
| 2025-02-06 23:19:32 +0000 | <ectospasm> | I may need to build XMonad with debugging symbols |
| 2025-02-06 23:20:36 +0000 | <ectospasm> | Also, I should probably not rebuild xmonad before launching it again while I'm trying to debug this (`coredumpctl debug` posted a message saying the executable may not match the core dump, which makes sense since I recompiled it after the dump was produced) |
| 2025-02-06 23:21:31 +0000 | <ectospasm> | I guess everything linked to it would need debugging symbols as well, not just the Haskell/XMonad bits. |
| 2025-02-06 23:21:47 +0000 | <ectospasm> | In case it's something outside of XMonad causing this. |
| 2025-02-06 23:22:26 +0000 | <ectospasm> | I suspect libXft if I had to hazard a guess, since I can't reproduce the behavior if I change the references to 'xft' in xmonad.hs to 'pango'. |
| 2025-02-06 23:23:14 +0000 | <geekosaur> | most things will have external debug symbols, although you may need to install them with pacman |
| 2025-02-06 23:23:48 +0000 | <ectospasm> | Yep. |
| 2025-02-06 23:35:46 +0000 | <ectospasm> | Is there a way for me to build the debugging symbols for the XMonad executable I build? |
| 2025-02-06 23:36:01 +0000 | <ectospasm> | It looks like coredumpctl is getting the debug symbols for everything else. |
| 2025-02-06 23:36:11 +0000 | <ectospasm> | Or at least it appears that way. |
| 2025-02-06 23:36:16 +0000 | <geekosaur> | I think you'd have to set up a build script |
| 2025-02-06 23:37:01 +0000 | <ectospasm> | Yep, I see output that I don't have anything like that set up when I do recompile it. |
| 2025-02-06 23:37:21 +0000 | <ectospasm> | Any guides on where I can set that up quickly? |
| 2025-02-06 23:39:13 +0000 | <ectospasm> | OK, so coredumpctl debug finally finished loading everything, and I see this: warning: 1491 XMonad/Prompt.hs: No such file or directory |
| 2025-02-06 23:39:27 +0000 | <ectospasm> | So it looks like I'm missing something. I wonder why it compiles? |
| 2025-02-06 23:39:48 +0000 | <ectospasm> | That's before I built debugging symbols. |
| 2025-02-06 23:41:12 +0000 | <geekosaur> | https://paste.tomsmeding.com/lkiSFKKs put this in a file called "build" in the same directory as xmonad.hs, and "chmod +x build" |
| 2025-02-06 23:41:59 +0000 | <geekosaur> | you don't have source files installed, only object files and HI files |
| 2025-02-06 23:42:09 +0000 | <geekosaur> | which are all you need to build |