Logs: liberachat/#xmonad
| 2022-07-09 16:12:19 | <Zedgamer9128[m]> | maybe it is updated from the arch repo |
| 2022-07-09 16:14:05 | <Zedgamer9128[m]> | oops looks like i have to use comma |
| 2022-07-09 16:17:53 | <Zedgamer9128[m]> | okay had to installed the trayer-srg-git from aur and now its working thanks |
| 2022-07-09 16:26:38 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds) |
| 2022-07-09 16:46:15 | × | qbt quits (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2022-07-09 17:28:10 | → | tjmciver_ joins (~tjmciver@cpe-172-101-39-156.maine.res.rr.com) |
| 2022-07-09 17:30:30 | × | tjmciver quits (~tjmciver@cpe-172-101-39-156.maine.res.rr.com) (Ping timeout: 240 seconds) |
| 2022-07-09 18:01:24 | × | tjmciver_ quits (~tjmciver@cpe-172-101-39-156.maine.res.rr.com) (Ping timeout: 272 seconds) |
| 2022-07-09 18:24:43 | → | tjmciver joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-09 19:53:00 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::909a) |
| 2022-07-09 19:55:51 | × | jludwig quits (~justin@li657-110.members.linode.com) (Quit: ZNC - https://znc.in) |
| 2022-07-09 19:56:47 | → | jludwig joins (~justin@li657-110.members.linode.com) |
| 2022-07-09 20:10:33 | × | jludwig quits (~justin@li657-110.members.linode.com) (Read error: Connection reset by peer) |
| 2022-07-09 20:13:30 | → | jludwig joins (~justin@li657-110.members.linode.com) |
| 2022-07-09 20:16:19 | × | tjmciver quits (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Remote host closed the connection) |
| 2022-07-09 20:16:42 | → | tjmciver joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-09 20:20:43 | × | jludwig quits (~justin@li657-110.members.linode.com) (Quit: ZNC - https://znc.in) |
| 2022-07-09 20:21:41 | → | jludwig joins (~justin@li657-110.members.linode.com) |
| 2022-07-09 20:22:39 | → | tjmciver_ joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-09 20:25:20 | × | tjmciver quits (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Ping timeout: 244 seconds) |
| 2022-07-09 20:28:25 | tjmciver_ | is now known as tjmciver |
| 2022-07-09 20:30:20 | × | tjmciver quits (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Read error: Connection reset by peer) |
| 2022-07-09 20:30:37 | → | tjmciver joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-09 21:07:11 | → | tjmciver_ joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-09 21:09:31 | × | tjmciver quits (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Ping timeout: 256 seconds) |
| 2022-07-09 21:22:18 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:c5c0:a118:2df4:ea86) (Ping timeout: 240 seconds) |
| 2022-07-09 21:49:15 | <zawaken-> | hey, after upgrading to 0.17+ of xmonad(-contrib) on my gentoo VM, I can't seem to get the haskell-dbus module to work, xmonad and x instantly crashes if I have all my DBus configuration enabled, it does not do this on Arch or RHEL, the dbus service in OpenRC is enabled. Just importing the DBus library doesn't crash anything. I am absolutely horrible at haskell, but I doubt theres something wrong |
| 2022-07-09 21:49:17 | <zawaken-> | with my xmonad.hs, considering it works on Arch and RHEL |
| 2022-07-09 21:49:34 | <zawaken-> | Any thoughts? |
| 2022-07-09 21:50:36 | <zawaken-> | If it helps I can send my configuration, even though there shouldn't be anything wrong with it, apart from horrible code that is. |
| 2022-07-09 21:51:13 | <geekosaur[m]> | what version of ghc is it using? |
| 2022-07-09 21:51:28 | <zawaken-> | 8.10.7 |
| 2022-07-09 21:51:44 | × | tjmciver_ quits (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Remote host closed the connection) |
| 2022-07-09 21:51:44 | <zawaken-> | Stackage LTS 18.23 I believe |
| 2022-07-09 21:52:23 | <geekosaur[m]> | hm. so it's not the heap corruption crash then. (doublecheck though, xmonad tickles a heap corruption bug in ghc >= 9.0) |
| 2022-07-09 21:53:10 | <zawaken-> | The crash happens after a couple of seconds after I type in startx. |
| 2022-07-09 21:54:03 | <geekosaur[m]> | yes, if it were the heap corruption thing it would probably happen after receiving a couple of X events, specifically after the first gc |
| 2022-07-09 21:55:53 | <zawaken-> | It does crash faster it seems when I try to do anything, such as open a terminal, but it does crash automatically after a bit |
| 2022-07-09 21:56:08 | <zawaken-> | I'm not sure I understand the heap corruption thing though |
| 2022-07-09 21:57:08 | <geekosaur[m]> | it's complicated. we allocate memory for an X event ahead of time and reuse it. the bug is ghc doesn't realize it's still in use and gc-s it, after which the next X event received trashes the heap |
| 2022-07-09 21:57:31 | <geekosaur[m]> | https://gitlab.haskell.org/ghc/ghc/-/issues/21708 |
| 2022-07-09 21:58:25 | <zawaken-> | Thanks for the link :) |
| 2022-07-09 21:58:53 | <geekosaur[m]> | we have a patch that seems to work around it, although it needs more testing |
| 2022-07-09 21:59:10 | <geekosaur[m]> | and the bug is a blocker for 9.4 release so it will at some point be fixed in ghc |
| 2022-07-09 22:00:24 | <zawaken-> | If this bug were to happen, would it be regardless of how your config looks? because I have XMonad up on my VM now, but without Dbus (I use it for Polybar and eww) |
| 2022-07-09 22:00:32 | <geekosaur[m]> | but if you're on 8.10.7 then this can't be the issue since it involves optimization of join points and 8.10.7 doesn't have join points |
| 2022-07-09 22:01:53 | <zawaken-> | I can send you a link to my dotfile repository if you want to see exactly what commit I am on as well as my config. |
| 2022-07-09 22:02:26 | <zawaken-> | It is the same across systems though, so this might be some quirky Gentoo dbus behaviour |
| 2022-07-09 22:02:38 | <geekosaur[m]> | that's unclear. one user can reproduce it with any non-default config (`xmonad def` being the default config). others can only reproduce it under specific circumstances. it seems to rely on heap layout, which makes sense because if it can't rearrange the heap to reclaim the memory for something else then there wouldn't be a problem (this seems to happen with my config, for example; I've never managed to reproduce the crash) |
| 2022-07-09 22:03:15 | <geekosaur[m]> | do you have a session log? it may depend on how your session starts, but it's often `~/.xsession-errors` |
| 2022-07-09 22:04:37 | <zawaken-> | ~/.xsession-errors doesn't exist for me, but I can cook up a Xorg.0.log, aswell as a xmonad.erros |
| 2022-07-09 22:04:42 | <zawaken-> | xmonad.errors |
| 2022-07-09 22:05:34 | × | noex_ quits (~null@2600:8804:14e0:104::1e13) (Ping timeout: 244 seconds) |
| 2022-07-09 22:07:13 | → | chomwitt joins (~chomwitt@2a02:587:dc0d:4a00:eb52:69a9:fa15:908e) |
| 2022-07-09 22:07:31 | → | noex_ joins (~null@2600:8804:14e0:104:8804:14e0:104:0) |
| 2022-07-09 22:12:45 | <geekosaur[m]> | neither of those is the right log (the first is the server log, the second is for recompilation errors) |
| 2022-07-09 22:13:38 | <geekosaur[m]> | if you use `startx` then any errors will be on the original console (try CTRL+ALT+F1). otherwise you'll have to look up the display manager you use and see where it logs session errors |
| 2022-07-09 22:15:23 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds) |
| 2022-07-09 22:16:12 | <zawaken-> | https://wiki.archlinux.org/title/xorg#Session_log_redirection this should suffice no? |
| 2022-07-09 22:17:45 | <zawaken-> | I'll see if I can get something out of that. |
| 2022-07-09 22:20:33 | <zawaken-> | I think what might have happened, is that I have used a dbus-launch command that doesn't work as it should. |
| 2022-07-09 22:20:44 | <zawaken-> | It seems like it might work as it should now |
| 2022-07-09 22:21:16 | <zawaken-> | So pebcak |
| 2022-07-09 22:22:02 | <geekosaur[m]> | maybe. seems like the dbus bindings should handle that better |
| 2022-07-09 22:23:27 | <geekosaur[m]> | looks like they should at least throw an exception, but the example code doesn't pay attention to exceptions or error returns |
| 2022-07-09 22:23:39 | <zawaken-> | It doesn't work if I put it straight as 'exec xmonad', but with exec dbus-launch --sh-syntax --exit-with-session xmonad it seems to work well |
| 2022-07-09 22:25:01 | <zawaken-> | this was the part that didn't work, and now I understand why: DESKTOP="dbus-launch --sh-syntax --exit-with-session xmonad" \n exec "${DESKTOP}" |
| 2022-07-09 22:25:15 | <geekosaur[m]> | hm, `--sh-syntax` and `--exit-with-session` shouldn't do anything there. they're intended for using it as `eval dbus-launch --sh-syntax --exit-with-session` |
| 2022-07-09 22:25:28 | <geekosaur[m]> | (`eval`, not `exec`) |
| 2022-07-09 22:26:17 | <zawaken-> | I think I got it from a bug report somewhere, a good while ago, and he used it, dbus-launch xmonad should probably be enough then? |
| 2022-07-09 22:26:41 | <geekosaur[m]> | yes, if you';re not running anything else that might want access to dbus |
| 2022-07-09 22:27:48 | <zawaken-> | Yeah only xmonad as far as I know |
| 2022-07-09 22:28:13 | <geekosaur[m]> | but if you launch a couple of terminals in the background and then exec xmonad, those terminals wouldn't have access to dbus unless you used the `eval` thing |
| 2022-07-09 22:28:56 | <zawaken-> | Ah, makes sense. My .xinitrc is quite simple |
| 2022-07-09 22:31:52 | <zawaken-> | Thank you very much for the help :D |
| 2022-07-09 22:44:06 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::909a) |
| 2022-07-09 22:57:28 | zawaken- | is now known as zawaken |
| 2022-07-09 22:59:48 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:eb52:69a9:fa15:908e) (Ping timeout: 276 seconds) |
| 2022-07-09 23:47:03 | × | steve__ quits (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 256 seconds) |
| 2022-07-10 01:52:03 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Ping timeout: 276 seconds) |
| 2022-07-10 02:04:45 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds) |
| 2022-07-10 02:10:20 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2022-07-10 02:23:19 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-07-10 02:30:50 | × | td_ quits (~td@muedsl-82-207-238-037.citykom.de) (Ping timeout: 240 seconds) |
| 2022-07-10 02:32:47 | → | td_ joins (~td@muedsl-82-207-238-125.citykom.de) |
| 2022-07-10 02:49:45 | × | terrorjack quits (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
| 2022-07-10 02:52:10 | → | terrorjack joins (~terrorjac@2a01:4f8:1c1e:509a::1) |
| 2022-07-10 03:03:50 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds) |
| 2022-07-10 03:11:01 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::909a) (Quit: Going elsewhere) |
| 2022-07-10 03:12:50 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::909a) |
| 2022-07-10 03:59:06 | × | mudri quits (sid317655@helmsley.irccloud.com) (Ping timeout: 276 seconds) |
| 2022-07-10 04:02:17 | → | mudri joins (sid317655@id-317655.helmsley.irccloud.com) |
| 2022-07-10 04:54:54 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::909a) (Quit: Going elsewhere) |
| 2022-07-10 04:59:28 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::909a) |
| 2022-07-10 05:18:40 | <Solid> | why, would you look at that |
| 2022-07-10 05:18:59 | <Solid> | just sitting at the gate idly and apparently Arch has updated to 0.17.0 finally |
| 2022-07-10 05:22:13 | <Solid> | this sets up an interesting situation; depending on how fast they will upgrade to 9.2.3 it might be quite essential for us to release 0.17.1 with #404 (what a fitting PR number, btw :) |
| 2022-07-10 05:22:50 | <Solid> | though supposedly a fix for ghc/#21708 should land in 9.2.4, which would be quite ideal for us |
| 2022-07-10 05:29:23 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds) |
| 2022-07-10 07:09:21 | → | jason joins (~sogens@211.30.26.217) |
All times are in UTC.