Logs: freenode/#xmonad
| 2021-01-31 19:07:59 | → | gazler__ joins (~gazler@2001:8b0:b165:a8d2:d19:fc83:e0fa:4af3) |
| 2021-01-31 19:35:58 | × | abhixec quits (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 264 seconds) |
| 2021-01-31 19:55:22 | × | idhugo quits (~idhugo@80-62-117-97-mobile.dk.customer.tdc.net) (Ping timeout: 246 seconds) |
| 2021-01-31 19:59:54 | → | idhugo joins (~idhugo@80-62-117-97-mobile.dk.customer.tdc.net) |
| 2021-01-31 20:10:11 | <Liskni_si> | oh crap, I've been playing with randr (fizzie's autorandr was an inspiration) for a bit and now I need xmonad state to persist a pkill -9 xmonad |
| 2021-01-31 20:10:31 | <Liskni_si> | s/persist/survive/, or something |
| 2021-01-31 20:13:50 | <Solid> | oof |
| 2021-01-31 20:13:58 | <Solid> | that's what XMONAD_CACHE_DIR is for, I guess :> |
| 2021-01-31 20:18:18 | <Liskni_si> | stuff like this actually belongs to $XDG_RUNTIME_DIR, otherwise I'd need to garbage collect that |
| 2021-01-31 20:19:15 | <Liskni_si> | (I intend to use a file with $XDG_SESSION_ID in its name and periodically writeStateToFile to it, and never delete it) |
| 2021-01-31 20:19:45 | <Liskni_si> | it'll be a bit tricky to turn this into a clean PR though :-/ |
| 2021-01-31 20:20:45 | × | idhugo quits (~idhugo@80-62-117-97-mobile.dk.customer.tdc.net) (Ping timeout: 240 seconds) |
| 2021-01-31 20:21:12 | <Solid> | oh okay |
| 2021-01-31 20:21:41 | <Liskni_si> | I should've used another session to play with it, probably |
| 2021-01-31 20:26:21 | → | cfricke joins (~cfricke@unaffiliated/cfricke) |
| 2021-01-31 20:29:04 | × | cfricke quits (~cfricke@unaffiliated/cfricke) (Client Quit) |
| 2021-01-31 20:48:30 | <geekosaur> | -9? violent much? |
| 2021-01-31 20:49:12 | <geekosaur> | (also, every so often I consider having SIGINT do a --restart) |
| 2021-01-31 20:51:57 | → | growpotkin joins (~growpotki@130-45-30-154.dyn.grandenetworks.net) |
| 2021-01-31 21:08:32 | <Liskni_si> | geekosaur: systemd considers sigtermed processes as having exited cleanly and doesn't restart them |
| 2021-01-31 21:09:37 | <geekosaur> | SIGHUP then |
| 2021-01-31 21:10:14 | <geekosaur> | be nice if we exited cleanly on 1 and 15 and restarted on 2 |
| 2021-01-31 21:10:16 | <Liskni_si> | "In this context, a clean exit means an exit code of 0, or one of the signals SIGHUP, SIGINT, SIGTERM or SIGPIPE, and additionally, exit statuses and signals specified in SuccessExitStatus=." |
| 2021-01-31 21:10:37 | <geekosaur> | ah. of course they overthought it |
| 2021-01-31 21:10:43 | <Liskni_si> | but I don't think it really matters |
| 2021-01-31 21:10:45 | <Liskni_si> | or does it? |
| 2021-01-31 21:11:43 | <geekosaur> | not sure if libX11 needs to do any cleanup. I do know it caches some stuff but don't know how much the server is involved with that such that XCloseDisplay is adviseable. although come to think of it we just exitSuccess without closing anyway |
| 2021-01-31 21:12:05 | <Liskni_si> | the issue I'm trying to workaround is that the X event loop appears to get stuck or something like that, because I don't yet know what, and when that happens I just want to kill the damn thing and try again later |
| 2021-01-31 21:12:22 | <geekosaur> | that's one reason I want to have some signal handling |
| 2021-01-31 21:12:56 | <geekosaur> | we have to be careful with that though, because the Haskell runtime doesn't handle signals cleanly itself and we could crash before our signal handler even runs :( |
| 2021-01-31 21:13:08 | <geekosaur> | which is why I killed off the idea of handling SIGCHLD |
| 2021-01-31 21:13:10 | <Liskni_si> | yeah but would you trust a process that is already somewhat stuck with handling its signals correctly? :-) |
| 2021-01-31 21:13:30 | <geekosaur> | as long as we're not invoking the event loop, sure |
| 2021-01-31 21:14:16 | <geekosaur> | I mean, how many ways to get xmonad stuck have you already debugged in the past 2 weeks? :) |
| 2021-01-31 21:14:30 | <Liskni_si> | this one's the first |
| 2021-01-31 21:14:48 | <Liskni_si> | on, it's not |
| 2021-01-31 21:15:04 | <Liskni_si> | the other one I didn't debug in my main session |
| 2021-01-31 21:15:11 | <Liskni_si> | because who in their right mind would do that |
| 2021-01-31 21:15:40 | <Liskni_si> | the one I'm debugging now was completely unexpected, caught me by surprise :-) |
| 2021-01-31 21:17:26 | <geekosaur> | anyway signal handling would make a lot of sense for this case, the Haskell runtime permitting |
| 2021-01-31 21:18:10 | × | ADG1089__ quits (~aditya@223.236.190.35) (Remote host closed the connection) |
| 2021-01-31 21:18:36 | <geekosaur> | in particular making some signal invoke the --restart pathway, which would then be a way to recover from these kinds of loops (unless the loop's cause is a corrupt StackSet or something) |
| 2021-01-31 21:19:26 | geekosaur | has to go now though |
| 2021-01-31 21:19:47 | <Liskni_si> | hm, yeah, having a signal do --restart would probably be another alternative to my session-specific statefile |
| 2021-01-31 21:19:48 | × | geekosaur quits (ae68c070@cpe-174-104-192-112.neo.res.rr.com) (Quit: Connection closed) |
| 2021-01-31 21:21:58 | <Liskni_si> | this one is good because I can writeStateToFile periodically in logHook or something, and possibly recover from a crash as well as from a hang |
| 2021-01-31 21:22:47 | <Liskni_si> | on the other hand I haven't seen a crash since, um, 2009 or something |
| 2021-01-31 21:37:50 | × | xaltsc quits (~xaltsc@unaffiliated/xaltsc) (Ping timeout: 264 seconds) |
| 2021-01-31 22:07:51 | × | palo quits (~weechat@c-base/crew/palo) (Quit: WeeChat 2.9) |
| 2021-01-31 22:08:42 | → | palo joins (~weechat@c-base/crew/palo) |
| 2021-01-31 22:33:51 | × | mc47 quits (~yecinem@89.246.239.190) (Quit: Leaving) |
| 2021-01-31 22:43:19 | × | thoros quits (~thoros@194-96-55-156.hdsl.highway.telekom.at) (Quit: WeeChat 3.0) |
| 2021-01-31 22:48:02 | → | abhixec joins (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-01-31 22:53:42 | × | notis quits (~notis@185.51.134.230) (Quit: WeeChat 3.0) |
| 2021-01-31 22:54:06 | → | notis joins (~notis@185.51.134.230) |
| 2021-01-31 23:00:37 | × | abhixec quits (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 272 seconds) |
| 2021-01-31 23:02:23 | × | seschwar quits (~seschwar@unaffiliated/seschwar) (Quit: :wq) |
| 2021-01-31 23:33:18 | → | kelnoky joins (~shao@ip1f1285ec.dynamic.kabel-deutschland.de) |
| 2021-01-31 23:44:12 | → | abhixec joins (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2021-01-31 23:46:39 | <Liskni_si> | so there's a `x = f x` in getEvent in the X11 package, that's what's hanging my xmonad :-) |
| 2021-02-01 00:00:01 | × | hexo quits (~hexo@gateway/tor-sasl/hexo) (Remote host closed the connection) |
| 2021-02-01 00:00:17 | → | hexo joins (~hexo@gateway/tor-sasl/hexo) |
| 2021-02-01 00:22:31 | × | notis quits (~notis@185.51.134.230) (Ping timeout: 265 seconds) |
| 2021-02-01 00:29:05 | → | jchia__ joins (~jchia@58.32.36.158) |
| 2021-02-01 00:29:08 | × | jchia__ quits (~jchia@58.32.36.158) (Client Quit) |
| 2021-02-01 01:11:04 | → | brttmsn joins (~brtt@2600:8804:8689:3f00::2395) |
| 2021-02-01 01:11:53 | <brttmsn> | anyone here know why on a fresh install of xmonad and xmobar i keep getting the error of hGetContents: invalid argument (invalid byte sequence) |
| 2021-02-01 01:13:46 | × | kelnoky quits (~shao@ip1f1285ec.dynamic.kabel-deutschland.de) (Ping timeout: 264 seconds) |
| 2021-02-01 01:25:31 | <Liskni_si> | brttmsn: most likely because you're not using the xmobar pipe anywhere |
| 2021-02-01 01:25:50 | <brttmsn> | im using the same config ive always used and its always worked before |
| 2021-02-01 01:26:24 | <Liskni_si> | oh, "invalid byte sequence" is something else than I thought, sorry |
| 2021-02-01 01:26:31 | Liskni_si | is tired |
| 2021-02-01 01:26:47 | <brttmsn> | its cool. I just dont understand why im getting invalid byte sequence |
| 2021-02-01 01:27:11 | <Liskni_si> | my next tip is something with locales |
| 2021-02-01 01:27:45 | <brttmsn> | wait, i remember my tty kicking something back about my LANG not being set |
| 2021-02-01 01:27:49 | <brttmsn> | could that affect it? |
| 2021-02-01 01:27:53 | <Liskni_si> | could be related |
| 2021-02-01 01:28:03 | <Liskni_si> | maybe you're using some locale that wasn't generated using locale-gen or something |
| 2021-02-01 01:28:26 | <Liskni_si> | I don't really know much about this since I'm using a traditional oldschool distro that doesn't let me fuck this up |
| 2021-02-01 01:29:03 | <Liskni_si> | https://wiki.archlinux.org/index.php/locale |
| 2021-02-01 01:29:06 | <Liskni_si> | I'd look here |
| 2021-02-01 01:29:40 | <brttmsn> | yeah i just corrected my locale and reran the command to generate it |
| 2021-02-01 01:29:45 | <brttmsn> | still getting the error |
| 2021-02-01 01:30:09 | <brttmsn> | xmobar: /home/brtt/.config/xmobar/xmobarrc: hGetContents: invalid argument (invalid byte sequence) |
| 2021-02-01 01:30:15 | <brttmsn> | that's the exact error |
| 2021-02-01 01:30:39 | <Liskni_si> | oh, you're getting the error while reading the config, not while reading from the pipe |
| 2021-02-01 01:30:55 | <Liskni_si> | then maybe you just have some invalid byte sequence in the config :-) |
| 2021-02-01 01:31:01 | <brttmsn> | english? |
| 2021-02-01 01:31:47 | <Liskni_si> | what's your locale? |
| 2021-02-01 01:31:56 | <Liskni_si> | (LANG, or LC_ALL, or whatever) |
| 2021-02-01 01:32:11 | <brttmsn> | LANG=en_US.UTF-8 |
| 2021-02-01 01:34:17 | <brttmsn> | should i try rebooting now that i fixed that and see if that works? |
| 2021-02-01 01:34:54 | <Liskni_si> | if you had different LANG before, then logoff and login again might help, yeah |
| 2021-02-01 01:34:59 | × | brttmsn quits (~brtt@2600:8804:8689:3f00::2395) (Quit: WeeChat 3.0) |
| 2021-02-01 01:37:20 | → | brttmsn joins (~brtt@2600:8804:8689:3f00::2395) |
| 2021-02-01 01:37:34 | <brttmsn> | Liskni_si: that seemed to work. Got xmobar to launch |
| 2021-02-01 01:37:46 | <brttmsn> | but mine looks a bit weird |
| 2021-02-01 01:45:53 | × | brttmsn quits (~brtt@2600:8804:8689:3f00::2395) (Quit: WeeChat 3.0) |
| 2021-02-01 02:02:24 | → | brttmsn joins (~brtt@2600:8804:8689:3f00::2395) |
| 2021-02-01 02:02:31 | <brttmsn> | okay got my xmobar back |
All times are in UTC.