| 2022-04-15 00:01:08 +0200 | <geekosaur> | welp, I think I reproduced the xmonad crash… can't tell for certain but there's an X error of a bad colormap parameter |
| 2022-04-15 00:02:22 +0200 | <geekosaur> | hm, lot of noise in the session log |
| 2022-04-15 00:12:40 +0200 | <geekosaur> | bleh. restarted okay but now I don't have logs… |
| 2022-04-15 00:12:47 +0200 | <geekosaur> | guess I have to wait for debugging |
| 2022-04-15 00:14:05 +0200 | <geekosaur> | which means I also have to wait to play with vbox since that's what's crashing it here (which may mean it's unrelated_ |
| 2022-04-15 00:14:07 +0200 | <geekosaur> | ) |
| 2022-04-15 00:33:30 +0200 | <abastro[m]> | geekosaur: https://github.com/Abastro/pulpmonad/blob/master/app/Main.hs |
| 2022-04-15 00:38:58 +0200 | <geekosaur> | hm. that caused me to get a nasty suspicion, but no, it's not the debugStack |
| 2022-04-15 00:39:40 +0200 | <geekosaur> | I am reliably able to crash xmonad on 9.2.1 (but not 8.10.7) by starting VirtualBox |
| 2022-04-15 00:39:54 +0200 | <geekosaur> | otherwise it's been stable |
| 2022-04-15 00:40:34 +0200 | <geekosaur> | and I don't see much of anything else that would do it (mixing forkProcess with threads is a problem, but you don't appear to have anything that uses threads) |
| 2022-04-15 00:51:21 +0200 | <geekosaur> | I'm seeing a lot of user error (Error in function getWindowAttributes) but I think that happens anyway |
| 2022-04-15 00:52:17 +0200 | <geekosaur> | and some BadDrawable errors which might be related if it's trying to draw a border. wonder if we need to userCode that path or otherwise guard against exceptions if a window goes away while being managed |
| 2022-04-15 01:06:05 +0200 | <geekosaur> | switching back to 8.10.7 so I can mess with vbox (or reproduce the problem anyway) |
| 2022-04-15 01:06:49 +0200 | <geekosaur> | would like to know what it is about vbox and the second window it appears to open that I have yet to identify (because xmonad crashes when it pops) that is doing this |
| 2022-04-15 01:07:04 +0200 | <geekosaur> | even when xmonad doesn't crash there's a lot of border flickering before it settles down |
| 2022-04-15 01:08:25 +0200 | <geekosaur> | I can't be the only one using vbox with xmonad |
| 2022-04-15 01:08:38 +0200 | <geekosaur> | (haven't done this before, I usually use vmware) |
| 2022-04-15 01:25:03 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds) |
| 2022-04-15 01:35:08 +0200 | <abastro[m]> | Oh right, I have a much simpler repo with more frequent crashes |
| 2022-04-15 01:58:17 +0200 | <geekosaur> | back on 8.10.7 and the crashes have stopped… along with the BadDrawable errors |
| 2022-04-15 01:58:42 +0200 | <geekosaur> | wonder if it's a timing issue |
| 2022-04-15 01:59:06 +0200 | <geekosaur> | sadly vbox is still not behaving |
| 2022-04-15 02:03:10 +0200 | <abastro[m]> | Hmm |
| 2022-04-15 02:33:57 +0200 | rekahsoft | (~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) |
| 2022-04-15 02:51:16 +0200 | <abastro[m]> | geekosaur: This is also failing: https://github.com/Abastro/xmonad-test/blob/master/app/Main.hs |
| 2022-04-15 02:57:20 +0200 | <geekosaur> | sigh. I really need you to capture an X error or exception somehow, or give me a backtrace from a core dump |
| 2022-04-15 02:58:23 +0200 | <abastro[m]> | Oh. Sorry that I am bothering you |
| 2022-04-15 02:58:54 +0200 | <abastro[m]> | I don't know how to capture X error, tho I guess I could try to dig up the core dump |
| 2022-04-15 02:58:55 +0200 | <geekosaur> | not bothering me, just that I can't reproduce it here (the vbox thing seems unrelated) |
| 2022-04-15 02:59:13 +0200 | <geekosaur> | any exception or X error shouldbe in ~/.xsession-errors |
| 2022-04-15 02:59:36 +0200 | <geekosaur> | you wouldhave to log in on a text console to get it since it would be wiped out if you logged back into an X session |
| 2022-04-15 03:00:31 +0200 | <abastro[m]> | Hmmm |
| 2022-04-15 03:01:37 +0200 | <geekosaur> | (ctrl-alt-f1 usually) |
| 2022-04-15 03:17:05 +0200 | darkstardevx | (~darkstard@50.53.212.60) |
| 2022-04-15 03:37:51 +0200 | <abastro[m]> | Uhm why startx not even opening it |
| 2022-04-15 03:47:13 +0200 | <abastro[m]> | Welp I was trying to do it from root, meh |
| 2022-04-15 03:55:56 +0200 | <abastro[m]> | Somehow I have to install xterm to login from login shell?? |
| 2022-04-15 04:02:42 +0200 | <abastro[m]> | Well, I can't seem to run a xsession profile from login shell |
| 2022-04-15 04:21:31 +0200 | <abastro[m]> | geekosaur: how do I login from login shell? Uh, I can't seem to do these basic things |
| 2022-04-15 04:33:00 +0200 | <abastro[m]> | Okay actually, I can avoid overwriting it by just switching to tty2. |
| 2022-04-15 04:33:33 +0200 | <abastro[m]> | However, there is only environment settings going on. |
| 2022-04-15 04:34:31 +0200 | <abastro[m]> | Oh, finally found it I guess |
| 2022-04-15 04:38:15 +0200 | <abastro[m]> | https://paste.tomsmeding.com/2haEqtNt |
| 2022-04-15 04:49:49 +0200 | <abastro[m]> | Posted an issue: https://github.com/xmonad/xmonad/issues/389 |
| 2022-04-15 05:38:00 +0200 | rekahsoft | (~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) (Ping timeout: 248 seconds) |
| 2022-04-15 06:31:25 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-15 06:32:23 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-15 06:33:30 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-15 06:35:28 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-15 06:38:24 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-15 06:38:27 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-15 06:40:16 +0200 | mohab | (~mohab@156.223.10.66) |
| 2022-04-15 06:41:25 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
| 2022-04-15 07:11:47 +0200 | MarkLumbao[m] | (~mark-lumb@2001:470:69fc:105::cfc6) |
| 2022-04-15 07:14:14 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-04-15 07:52:04 +0200 | <abhixec> | anyone have any luck with hidpi scaling on xmonad? |
| 2022-04-15 08:01:26 +0200 | <Solid> | liskin: hotels in the region of zurihac are now going for 200EUR a night Oo |
| 2022-04-15 08:01:32 +0200 | <Solid> | and we probably all need four nights each |
| 2022-04-15 08:01:47 +0200 | <Solid> | at this point I'm so insanely thankful to our sponsors |
| 2022-04-15 08:02:58 +0200 | <abastro[m]> | 200eur for single personnel? |
| 2022-04-15 08:03:12 +0200 | <abastro[m]> | abhixec: Well i am using hidpi |
| 2022-04-15 08:04:13 +0200 | <abhixec> | abastro[m]: what do you do to scale applications properly when connected to hidpi(5k) monitor? |
| 2022-04-15 08:04:33 +0200 | <abastro[m]> | Oh mine is merely 2.5k but |
| 2022-04-15 08:04:34 +0200 | <abhixec> | and how do you scale it back to its original size when you disconnect(laptop screen) |
| 2022-04-15 08:04:42 +0200 | <abastro[m]> | Hmmm |
| 2022-04-15 08:04:51 +0200 | <abastro[m]> | Well that should be more tricky I think |
| 2022-04-15 08:05:09 +0200 | <abastro[m]> | Basically, I am using some kind of gtk settings to adjust it. |
| 2022-04-15 08:05:44 +0200 | <abastro[m]> | Soo.. could be more pain if you have to actively switch |
| 2022-04-15 08:05:56 +0200 | <abastro[m]> | I wonder if Per-monitor settings is possible |
| 2022-04-15 08:06:05 +0200 | <abhixec> | but that would only work for gtk apps if I have qt or xmobar will still be very small though |
| 2022-04-15 08:06:08 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-04-15 08:06:41 +0200 | <abastro[m]> | Yea you kind of need to do it manually |
| 2022-04-15 08:07:07 +0200 | <abastro[m]> | For each apps |
| 2022-04-15 08:07:59 +0200 | <abhixec> | -_- :'( |
| 2022-04-15 08:09:37 +0200 | <abastro[m]> | Alternative is sacrificing hdpi so that it renders 1 pixel over 4 pixels of 4k monitor |
| 2022-04-15 08:11:05 +0200 | <abastro[m]> | You know, using xrandr |
| 2022-04-15 08:11:22 +0200 | <abhixec> | abastro[m]: how do I do that? |
| 2022-04-15 08:12:01 +0200 | <abhixec> | xrandr scalling factor option doesn't quite work as expected because the windows appear to outside the visible portion of the screen |
| 2022-04-15 08:13:09 +0200 | <abastro[m]> | Did you try sth like |
| 2022-04-15 08:13:09 +0200 | <abastro[m]> | xrandr --mode 1920x1080 |
| 2022-04-15 08:13:22 +0200 | <abhixec> | let me try that! |
| 2022-04-15 08:13:47 +0200 | <abastro[m]> | (Ofc do not forget the --output part) |
| 2022-04-15 08:14:47 +0200 | <abhixec> | yep |
| 2022-04-15 08:14:53 +0200 | <abhixec> | I guess for that this would work |
| 2022-04-15 08:14:54 +0200 | <abhixec> | thanks! |
| 2022-04-15 08:15:18 +0200 | <abhixec> | not ideal but atleast it is now usable as oppose to having super tiny text |
| 2022-04-15 08:15:41 +0200 | <abhixec> | really wish there was a better support for 4K+ :( |
| 2022-04-15 08:16:17 +0200 | <abastro[m]> | Yea, I wonder how e.g. gnome handles it |
| 2022-04-15 08:17:24 +0200 | <abastro[m]> | Actually x font part could be managed separately, I found |
| 2022-04-15 08:17:32 +0200 | <abastro[m]> | https://vincent.jousse.org/blog/en/archlinux-retina-hidpi-macbookpro-xmonad |
| 2022-04-15 08:17:40 +0200 | <abastro[m]> | Try this and find to which extend it works |
| 2022-04-15 08:25:01 +0200 | <abhixec> | I think I have seen this the problem is that it would work if I am only going to be using the external monitor but if I want to be switching then I guess I would need to make this changes and restart x each time |
| 2022-04-15 08:25:10 +0200 | <abhixec> | which wouldn't be ideal |
| 2022-04-15 08:31:18 +0200 | <geekosaur> | this is one of the big reasonspeople want wayland: x11 can't do this right |
| 2022-04-15 08:35:30 +0200 | <abastro[m]> | Oh, inherent problem of X11? |
| 2022-04-15 08:37:12 +0200 | <abastro[m]> | I see, so that is why |
| 2022-04-15 08:37:24 +0200 | <abastro[m]> | ~~Can I fork Waymonad and work on it~~ |
| 2022-04-15 08:39:13 +0200 | <geekosaur> | of course you can. https://github.com/L-as/waymonad |
| 2022-04-15 08:39:34 +0200 | <geekosaur> | it needs a fair amount ofwork and currently has worse pointer issues than the one you hit with 9.2.2 :) |
| 2022-04-15 08:41:06 +0200 | <abastro[m]> | Pointer issues? Meh |
| 2022-04-15 08:41:17 +0200 | <abastro[m]> | Btw what is the pointer issue I encountered |
| 2022-04-15 08:41:21 +0200 | <abastro[m]> | FFI or internal? |
| 2022-04-15 08:41:51 +0200 | <abastro[m]> | I wonder if I could somehow enable stacktrace |
| 2022-04-15 08:42:21 +0200 | <Solid> | It says "Please report this as a GHC bug: https://www.haskell.org/ghc/reportabug" |
| 2022-04-15 08:42:26 +0200 | <Solid> | perhaps you should consider that |
| 2022-04-15 08:44:36 +0200 | <liskin> | Solid: oh, that's quite expensive |
| 2022-04-15 08:45:23 +0200 | <liskin> | Suddenly half an hour by train from my friend's at the other side of the lake doesn't seem so bad :-D |
| 2022-04-15 08:47:25 +0200 | <Solid> | :D |
| 2022-04-15 08:48:49 +0200 | <Solid> | yeah without the opencollective donations I don't think I could attend |
| 2022-04-15 08:49:04 +0200 | <Solid> | though at this point it makes me wonder whether I need to pay tax |
| 2022-04-15 08:49:08 +0200 | <Solid> | because it'd be quite a lot of money |
| 2022-04-15 08:51:08 +0200 | <liskin> | I think you don't need to pay tax on this |
| 2022-04-15 08:55:12 +0200 | <geekosaur> | abastro[m], no way to know just from that,but my first suspicion is always FFI. in particular I (and a bunch of others) should have hit it if it were intrinsic to 9.2.2 |
| 2022-04-15 09:00:29 +0200 | <geekosaur> | also there's no stack to trace in Haskell |
| 2022-04-15 09:01:20 +0200 | <geekosaur> | this is the garbage collector hitting a heap object that doesn't have the right metadata, meaning it's been overwritten with garbage |
| 2022-04-15 09:01:31 +0200 | <geekosaur> | by that point it's too late to know what or why |
| 2022-04-15 09:02:47 +0200 | <geekosaur> | and any information about where the heap object came from disappeared when its closure type did |
| 2022-04-15 09:35:20 +0200 | scardina1 | scardinal |
| 2022-04-15 09:37:49 +0200 | <MarkLumbao[m]> | Hi everyone it's my first time installing Xmonad via stack so I'm manually adding it as a new session option in lightdm. But I couldn't get it to work. I already added /usr/share/xsessions/xmonad.desktop with the following content |
| 2022-04-15 09:38:23 +0200 | <MarkLumbao[m]> | [Desktop Entry]... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/c4664259f1d52bbd6adebb6e75000b71d121…) |
| 2022-04-15 09:38:43 +0200 | <MarkLumbao[m]> | but the option is not shown in my greeter. |
| 2022-04-15 09:39:26 +0200 | <MarkLumbao[m]> | btw I'm using Garuda Linux, my default wm is i3wm, my greeter is slick-greeter |
| 2022-04-15 09:49:18 +0200 | <abastro[m]> | Oh soo.. overwritten with garbage :< |
| 2022-04-15 09:49:34 +0200 | <abastro[m]> | Haskell and its ffi... |
| 2022-04-15 09:50:34 +0200 | <abastro[m]> | Was saying to geekosaur btw |
| 2022-04-15 09:51:41 +0200 | <abastro[m]> | Solid: I am afraid of the mighty ghc repo |
| 2022-04-15 10:02:01 +0200 | <Solid> | abastro[m]: Haskell's FFI is pretty good, actually; at least in terms of efficiency ( see e.g. https://github.com/dyu/ffi-overhead#results-500m-calls ) |
| 2022-04-15 10:02:05 +0200 | <Solid> | and don't fear the GHC repo |
| 2022-04-15 10:02:21 +0200 | <Solid> | if you can reproduce it and it's actually a compiler bug, people will be glad to know about it |
| 2022-04-15 10:02:51 +0200 | <abastro[m]> | I do not mean efficiency, yeah |
| 2022-04-15 10:03:07 +0200 | <abastro[m]> | I mean more the ability to debug |
| 2022-04-15 10:03:23 +0200 | <Solid> | well, it's FFI |
| 2022-04-15 10:03:29 +0200 | <abastro[m]> | It seems geekosaur cannot reproduce it, so I guess it might be local to my end |
| 2022-04-15 10:17:17 +0200 | maybefbi | (~maybeatf@138.75.51.49) |
| 2022-04-15 10:17:45 +0200 | <maybefbi> | What kind of hie.yaml do I need for this directory structure: |
| 2022-04-15 10:17:45 +0200 | <maybefbi> | - path: "xmonad-git/tests" |
| 2022-04-15 10:17:45 +0200 | <maybefbi> | component: "xmonad:test:properties" |
| 2022-04-15 10:17:58 +0200 | <maybefbi> | sorry wrong copy paste |
| 2022-04-15 10:18:37 +0200 | <maybefbi> | What kind of hie.yaml do I need for this directory structure: . |
| 2022-04-15 10:18:37 +0200 | <maybefbi> | ├── stack.yaml |
| 2022-04-15 10:18:37 +0200 | <maybefbi> | ├── stack.yaml.lock |
| 2022-04-15 10:18:37 +0200 | <maybefbi> | ├── xmobar-git |
| 2022-04-15 10:18:37 +0200 | <maybefbi> | ├── xmonad-contrib-git |
| 2022-04-15 10:18:38 +0200 | <maybefbi> | ├── xmonad-git |
| 2022-04-15 10:18:40 +0200 | <maybefbi> | └── xmonad.hs |
| 2022-04-15 10:18:59 +0200 | <maybefbi> | I tried $ gen-hie > hie.yaml |
| 2022-04-15 10:19:15 +0200 | <maybefbi> | but it just causes Segmentation fault |
| 2022-04-15 10:19:31 +0200 | <abastro[m]> | What is xmonad-git and xmobar-git? |
| 2022-04-15 10:19:47 +0200 | <maybefbi> | it is a git clone of xmonad, and xmobar repo |
| 2022-04-15 10:19:59 +0200 | <maybefbi> | im on xmonad compiled using the above directory structure now |
| 2022-04-15 10:20:02 +0200 | <maybefbi> | it is working |
| 2022-04-15 10:20:21 +0200 | <maybefbi> | im just trying to create an hie.yaml so i can get the Haskell Language Server to work |
| 2022-04-15 10:20:32 +0200 | <Solid> | maybefbi: this may be a question more appropriate for #haskell of #haskell-language-server |
| 2022-04-15 10:20:40 +0200 | <Solid> | s/of/or/ |
| 2022-04-15 10:20:43 +0200 | <maybefbi> | ah cool thanks. i will ask there |
| 2022-04-15 10:35:00 +0200 | <abastro[m]> | I want to say, that is a bit weird setup if you are just using xmonad |
| 2022-04-15 10:38:23 +0200 | <Solid> | It's the setup that INSTALL.md suggests :) |
| 2022-04-15 10:40:38 +0200 | <abastro[m]> | Oh. |
| 2022-04-15 10:40:46 +0200 | <abastro[m]> | So that's how you install latest xmonad on git! |
| 2022-04-15 10:40:57 +0200 | <abastro[m]> | Hm that makes sense, that now I think about it |
| 2022-04-15 10:42:42 +0200 | <abastro[m]> | Solid: since you are here, I want to ask.. why is comonoid not used in haskell? In which context would it be used? |
| 2022-04-15 10:42:42 +0200 | <abastro[m]> | Thinking about why copattern is relatively not useful now |
| 2022-04-15 10:44:25 +0200 | <Solid> | Well the fundamental reason is that Hask, being a closed Cartesian category (if you ignore the stuff about Hask obviously not being a category), does not have non-trivial comonoids (meaning every object is a comonoid in exactly one, and always the same, way) |
| 2022-04-15 10:45:12 +0200 | <abastro[m]> | Is it the property of every closed cartesian category? |
| 2022-04-15 10:45:12 +0200 | <Solid> | This is why e.g. the Comonad class can get away with a Functor constraint only and not some kind of CoApplicative |
| 2022-04-15 10:45:17 +0200 | <Solid> | yes |
| 2022-04-15 10:45:39 +0200 | <abastro[m]> | I dislike how it is biased towards monoid |
| 2022-04-15 10:46:09 +0200 | <abastro[m]> | I guess I have to accept this kind of bias? |
| 2022-04-15 10:46:17 +0200 | <Solid> | And by some theorem of I think Lambek (not too sure about the origin) simply typed lambda theories correspond exactly to closed Cartesian categories |
| 2022-04-15 10:46:23 +0200 | <Solid> | pretty much yes |
| 2022-04-15 10:46:41 +0200 | <abastro[m]> | How about pattern (destructor) vs. copattern (constructor) |
| 2022-04-15 10:47:01 +0200 | <abastro[m]> | It seems like asymmetry extends out to that as well |
| 2022-04-15 10:47:02 +0200 | <Solid> | Actually, with linear Haskell landing now we can probably talk about non-trivial comonoids again |
| 2022-04-15 10:47:30 +0200 | <Solid> | AFAIK linear type theories replace the Cartesian-ness with symmetric monoidal-ness |
| 2022-04-15 10:47:43 +0200 | <Solid> | but I don't know anyting about linear type theories |
| 2022-04-15 10:48:20 +0200 | <abastro[m]> | Hmmm |
| 2022-04-15 10:48:26 +0200 | <abastro[m]> | Interesting stuffs |
| 2022-04-15 10:48:56 +0200 | <abastro[m]> | How about Copattern? |
| 2022-04-15 11:08:54 +0200 | <Solid> | don't know anything about that either :D |
| 2022-04-15 11:18:31 +0200 | <abastro[m]> | Okay, sorry for bothering you. I thought you would know everything related with co- duals |
| 2022-04-15 11:33:24 +0200 | <liskin> | maybefbi: let me know if you find anything; last time I checked, there was no way to tell HLS about the xmonad.hs ghc env |
| 2022-04-15 11:34:29 +0200 | <liskin> | Solid: I'm afk due to travels these days but I'll take a look at the GHA errors later |
| 2022-04-15 11:34:35 +0200 | <liskin> | geekosaur: ^ |
| 2022-04-15 11:34:42 +0200 | <Solid> | awesome, thank you! |
| 2022-04-15 11:34:56 +0200 | <maybefbi> | liskin, ok |
| 2022-04-15 11:59:51 +0200 | butterfly[m] | (~butterfly@2001:470:69fc:105::1:70db) |
| 2022-04-15 12:54:38 +0200 | Czernobog | (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-15 12:55:46 +0200 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-04-15 14:03:19 +0200 | <geekosaur> | abastro[m], that kind of question is the sort of thing #haskell gets into long diversions over (and was the original reason for #haskell-in-depth but nobody uses it for that any more) |
| 2022-04-15 14:04:34 +0200 | <abastro[m]> | Sorry, which kind of question you mean? |
| 2022-04-15 14:05:01 +0200 | <geekosaur> | MarkLumbao[m], that looks like an applications desktop entry. I needed both that and the sessions entry for things to work |
| 2022-04-15 14:06:53 +0200 | <geekosaur> | unfortunately I don't have the session desktop entry any more since I run xmonad under mate, but it was a relatively simple edit job on the existing sessions |
| 2022-04-15 14:07:39 +0200 | <geekosaur> | the preferred way to do this is not to use an application entry at all, but define a "X default session" entry which runs ~/.xsession and you run xmonad there |
| 2022-04-15 14:13:45 +0200 | <geekosaur> | oh, I see they rewired things since I last did this and that is in fact a valid session. did you restart the session manager? most of them only read sessions on start |
| 2022-04-15 14:14:25 +0200 | <geekosaur> | still, the easiest way to do this is install xinit-xsession (if you have easy access to AUR from Garuda) and use .xinitrc |
| 2022-04-15 14:31:45 +0200 | Czernobog | (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-15 14:32:39 +0200 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-04-15 15:01:03 +0200 | <MarkLumbao[m]> | geekosaur: I'll try installing xinit-xsession and see what I can do with it thanks :) |
| 2022-04-15 15:01:51 +0200 | <geekosaur> | yes.in any case I thinkthe Exec=xmonad in your xsession entry needs a matching xmonad.desktop in /usr/share/applications to work; it's not simply a program entry |
| 2022-04-15 15:02:03 +0200 | <geekosaur> | at least, that's what I recall from back when I did it |
| 2022-04-15 15:03:14 +0200 | <geekosaur> | but then you'll run into that your PATH is wrong, because the whole setupdoesn't read your .profile or .bash_profile or whatever, which is another reason to use the xinit-xsession route |
| 2022-04-15 15:03:26 +0200 | <geekosaur> | it still won't by default but it's easier to fix |
| 2022-04-15 15:04:09 +0200 | <MarkLumbao[m]> | I did add that earlier as well since that's what I've read on lightdm docs in Arch wiki but it didn't work as well. |
| 2022-04-15 15:08:12 +0200 | chomwitt | (~chomwitt@2a02:587:dc0f:ad00:3949:ab21:9834:ebc) |
| 2022-04-15 15:22:56 +0200 | benin | (~benin@183.82.204.110) (Quit: The Lounge - https://thelounge.chat) |
| 2022-04-15 15:28:23 +0200 | Polo | (~^@user/polo) |
| 2022-04-15 15:30:48 +0200 | Polo | (~^@user/polo) (Quit: Textual IRC Client: www.textualapp.com) |
| 2022-04-15 15:31:11 +0200 | Polo | (~GiverOfDo@56.15.195.173.client.static.strong-in52.as13926.net) |
| 2022-04-15 15:31:14 +0200 | Polo | (~GiverOfDo@56.15.195.173.client.static.strong-in52.as13926.net) (Changing host) |
| 2022-04-15 15:31:14 +0200 | Polo | (~GiverOfDo@user/polo) |
| 2022-04-15 15:37:36 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 15:38:51 +0200 | Polo_ | (~GiverOfDo@2607:fb91:bd04:dc9:29ae:af45:5ce9:81d1) |
| 2022-04-15 15:38:52 +0200 | Polo_ | (~GiverOfDo@2607:fb91:bd04:dc9:29ae:af45:5ce9:81d1) (Changing host) |
| 2022-04-15 15:38:52 +0200 | Polo_ | (~GiverOfDo@user/polo) |
| 2022-04-15 15:41:17 +0200 | Polo | (~GiverOfDo@user/polo) (Ping timeout: 256 seconds) |
| 2022-04-15 15:41:45 +0200 | Polo | (~GiverOfDo@user/polo) |
| 2022-04-15 15:42:06 +0200 | LordOfLand | (~GiverOfDo@user/polo) (Ping timeout: 250 seconds) |
| 2022-04-15 15:45:08 +0200 | Polo_ | (~GiverOfDo@user/polo) (Ping timeout: 250 seconds) |
| 2022-04-15 15:47:35 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 15:51:29 +0200 | Polo | (~GiverOfDo@user/polo) (Ping timeout: 256 seconds) |
| 2022-04-15 15:53:48 +0200 | LordOfLand | (~GiverOfDo@user/polo) (Ping timeout: 250 seconds) |
| 2022-04-15 15:54:56 +0200 | Czernobog | (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-15 15:55:55 +0200 | Czernobog | (~Czernobog@user/czernobog) |
| 2022-04-15 16:02:14 +0200 | Polo | (~GiverOfDo@user/polo) |
| 2022-04-15 16:25:32 +0200 | Polo | (~GiverOfDo@user/polo) (Quit: one) |
| 2022-04-15 16:30:21 +0200 | <abastro[m]> | geekosaur: How do I use xephyr? |
| 2022-04-15 16:31:37 +0200 | <geekosaur> | xephyr is a nested X server. you do something like: xinit /usr/bin/xephyr :1 -- /path/to/xmonad (full paths are important here) |
| 2022-04-15 16:32:01 +0200 | <geekosaur> | then you get a window which is basically an independent X session, without having to give up your regular X session or risk losing it |
| 2022-04-15 16:32:38 +0200 | <geekosaur> | as I said in #haskell, you generally want to change $HOME first so programs like firefoxs don't get upset about their configs being in use in multiple places |
| 2022-04-15 16:32:43 +0200 | <abastro[m]> | And.. Where do I run the `xinit` command? |
| 2022-04-15 16:33:34 +0200 | <geekosaur> | hm |
| 2022-04-15 16:34:07 +0200 | <geekosaur> | I would open a new terminal window, make a directory to serve as the $HOME for the xephyr session, then set HOME to that |
| 2022-04-15 16:34:18 +0200 | <geekosaur> | then run the xinit command in that window |
| 2022-04-15 16:37:47 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-15 16:39:27 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-15 16:40:05 +0200 | <abastro[m]> | Well, it doesn't start |
| 2022-04-15 16:40:18 +0200 | <abastro[m]> | Do I have to drop to login shell for this? |
| 2022-04-15 16:41:15 +0200 | <abastro[m]> | xmonad-x86_64-linux: user error (unrecognized flags:[":0"]) |
| 2022-04-15 16:41:15 +0200 | <abastro[m]> | Invalid MIT-MAGIC-COOKIE-1 keyxinit: giving up |
| 2022-04-15 16:47:49 +0200 | <geekosaur> | that doesn't sound quite right |
| 2022-04-15 16:49:29 +0200 | <abastro[m]> | Was it wrong that I did not drop to the login shell? |
| 2022-04-15 16:51:24 +0200 | <geekosaur> | no, I just tried it locally and got the same error; I guess they changed how xinit works and you need a proper .xinitrc |
| 2022-04-15 16:51:51 +0200 | <abastro[m]> | Oh no :( |
| 2022-04-15 16:52:17 +0200 | <geekosaur> | no, I just got things backwards, the server comes after the -- |
| 2022-04-15 16:52:20 +0200 | <geekosaur> | hold on |
| 2022-04-15 16:52:40 +0200 | <abastro[m]> | Hmm |
| 2022-04-15 16:53:18 +0200 | <geekosaur> | okay, that works. except I need to arrange for it to find the xmonad libs :) |
| 2022-04-15 16:53:40 +0200 | <geekosaur> | although actually you get a default config just by not having an xmonad.hs, so that may actually work better for testing |
| 2022-04-15 16:54:15 +0200 | <geekosaur> | xinit =xmonad -- =Xephyr :1 (except I think = is a zsh extension, so you need to use full paths still) |
| 2022-04-15 16:54:42 +0200 | <abastro[m]> | Fatal server error: |
| 2022-04-15 16:54:42 +0200 | <abastro[m]> | (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) |
| 2022-04-15 16:54:58 +0200 | <geekosaur> | did you use full paths? |
| 2022-04-15 16:55:05 +0200 | <abastro[m]> | Yes. |
| 2022-04-15 16:55:06 +0200 | <geekosaur> | otherwise it'll try to use :0 |
| 2022-04-15 16:55:33 +0200 | <abastro[m]> | Still says that server is already running |
| 2022-04-15 16:56:12 +0200 | <abastro[m]> | xephyr is at /usr/bin/Xephyr right? That program exists |
| 2022-04-15 16:56:17 +0200 | <abastro[m]> | And xmonad is my custom xmonad |
| 2022-04-15 16:56:33 +0200 | <abastro[m]> | Let me test just `xmonad` in cabal bin |
| 2022-04-15 16:57:05 +0200 | <geekosaur> | xinit /home/allbery/.cabal/bin/xmonad -- /usr/bin/Xephyr :1 |
| 2022-04-15 16:57:15 +0200 | <geekosaur> | remember that you changed $HOME so ~ won't work |
| 2022-04-15 16:57:18 +0200 | <abastro[m]> | Did `xinit /home/abastro/.cabal/bin/xmonad -- /usr/bin/Xephyr :1` |
| 2022-04-15 16:57:29 +0200 | <abastro[m]> | _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/9499e2d4fbc20d3ac3b2e0ebf44755b989f4…) |
| 2022-04-15 16:58:23 +0200 | <geekosaur> | odd. I wonder if you already have a :1 |
| 2022-04-15 16:58:42 +0200 | <abastro[m]> | Oh I guess so |
| 2022-04-15 16:58:44 +0200 | <geekosaur> | or if your system has things locked up so tight that it can't create new server sockets without whacking systemd on the head |
| 2022-04-15 16:58:52 +0200 | <geekosaur> | (default is :0) |
| 2022-04-15 16:59:08 +0200 | <abastro[m]> | Yep, :1 was occupied |
| 2022-04-15 16:59:08 +0200 | <abastro[m]> | lol |
| 2022-04-15 16:59:26 +0200 | <abastro[m]> | Aand that ran my current profile lol |
| 2022-04-15 17:03:27 +0200 | <geekosaur> | did you do the stuff to create a new home directory? |
| 2022-04-15 17:04:03 +0200 | <abastro[m]> | Ye, well I don't have anything in `$HOME/.xmonad` at least |
| 2022-04-15 17:06:08 +0200 | <geekosaur> | https://paste.tomsmeding.com/6F3vAdz8 |
| 2022-04-15 17:06:08 +0200 | <abastro[m]> | I clicked and I got `user error (Error in function getWindowAttributes)` |
| 2022-04-15 17:06:20 +0200 | <geekosaur> | that happens every so often |
| 2022-04-15 17:06:42 +0200 | <geekosaur> | at some point we should clean that up, but it would be a breaking change to the X11 package |
| 2022-04-15 17:10:31 +0200 | <abastro[m]> | Hmm, I just randomly got dropped out |
| 2022-04-15 17:11:43 +0200 | <geekosaur> | does the terminal you ran xephyr in show anything? |
| 2022-04-15 17:12:32 +0200 | <abastro[m]> | No. |
| 2022-04-15 17:13:14 +0200 | <abastro[m]> | And this time it just works without errors |
| 2022-04-15 17:15:45 +0200 | <abastro[m]> | Okay perhaps that one is working, let me test with my custom one |
| 2022-04-15 17:19:27 +0200 | <abastro[m]> | Yep, it seems to exit at random moment without notice. |
| 2022-04-15 17:19:59 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 17:20:15 +0200 | <abastro[m]> | Sometimes it works well for long, sometimes it immediately crash |
| 2022-04-15 17:20:44 +0200 | <geekosaur> | yes, that'd be expected for heap corruption |
| 2022-04-15 17:20:55 +0200 | <abastro[m]> | The crash happens much more often when being run from native |
| 2022-04-15 17:20:57 +0200 | <geekosaur> | what we really need is something like memcheck |
| 2022-04-15 17:21:05 +0200 | <abastro[m]> | I hate how it doesn't give any notice.. |
| 2022-04-15 17:21:34 +0200 | <geekosaur> | not sure how well it works with how ghc manages its heap though |
| 2022-04-15 17:40:25 +0200 | <abastro[m]> | Found problem with custom $HOME |
| 2022-04-15 17:40:44 +0200 | <abastro[m]> | cabal.. |
| 2022-04-15 17:43:01 +0200 | <abastro[m]> | Oh I think the problem happens much more often with my custom minimal xmonad |
| 2022-04-15 17:43:03 +0200 | <abastro[m]> | I wonder why |
| 2022-04-15 17:47:10 +0200 | <abastro[m]> | `desktopConfig` makes it break! |
| 2022-04-15 17:48:32 +0200 | <abastro[m]> | Just clicking it make it crashes hmm |
| 2022-04-15 17:48:48 +0200 | <abastro[m]> | And again I got: |
| 2022-04-15 17:48:50 +0200 | <abastro[m]> | xmonad-x86_64-linux: internal error: evacuate: strange closure type 4721 |
| 2022-04-15 17:48:50 +0200 | <abastro[m]> | (GHC version 9.2.2 for x86_64_unknown_linux) |
| 2022-04-15 17:48:50 +0200 | <abastro[m]> | Please report this as a GHC bug: https://www.haskell.org/ghc/reportabug |
| 2022-04-15 17:48:56 +0200 | <abastro[m]> | Hard to reproduce |
| 2022-04-15 17:50:07 +0200 | <geekosaur> | desktopConfig is pretty simple, just ewmh and docks on top of def |
| 2022-04-15 17:50:44 +0200 | <geekosaur> | both involve X props though |
| 2022-04-15 17:52:53 +0200 | <abastro[m]> | This is quite strange. |
| 2022-04-15 17:53:05 +0200 | <abastro[m]> | I can indeed crash it using `xmonad def` |
| 2022-04-15 17:53:12 +0200 | <abastro[m]> | but it takes more effort |
| 2022-04-15 17:53:45 +0200 | <abastro[m]> | In contrast, with `desktopConfig` it crashes more often |
| 2022-04-15 17:54:58 +0200 | <abastro[m]> | In that case, Mod+Q makes it crash more often it seems. |
| 2022-04-15 17:55:07 +0200 | <geekosaur> | so it's something about the X11 interface and probably properties |
| 2022-04-15 17:55:25 +0200 | <geekosaur> | (core xmonad still uses props but only the basic ICCCM set) |
| 2022-04-15 17:55:53 +0200 | <abastro[m]> | I dislike how `evacuate: strange closure type` this message only seldom appears in the log. |
| 2022-04-15 17:56:13 +0200 | <abastro[m]> | Does `xmonad def` also use X11 interface? |
| 2022-04-15 17:56:27 +0200 | <geekosaur> | xmonad always uses the X11 interface, it is a window manager |
| 2022-04-15 17:56:38 +0200 | <abastro[m]> | Ahh |
| 2022-04-15 17:56:38 +0200 | <geekosaur> | the question is how much and what parts |
| 2022-04-15 17:56:45 +0200 | <abastro[m]> | Yep, likely |
| 2022-04-15 17:56:50 +0200 | <abastro[m]> | I wonder how I could actually debug this |
| 2022-04-15 17:56:56 +0200 | <geekosaur> | ewmh and docks exercise X11 properties a lot more |
| 2022-04-15 17:57:16 +0200 | <geekosaur> | (ewmh sets a bunch of root window props in logHook, docks reads strut props on new windows) |
| 2022-04-15 17:59:45 +0200 | <abastro[m]> | I see, sounds likely |
| 2022-04-15 18:00:13 +0200 | <abastro[m]> | That said, it is funny how my more involved personal config works better in 9.2.2 - it only crashes once in a week |
| 2022-04-15 18:00:28 +0200 | <geekosaur> | but none of this explains why I couldn't reproduce it with my config, which uses props even more |
| 2022-04-15 18:00:59 +0200 | <geekosaur> | (I think I still set _NET_WORKAREA because some programs I use break without it) |
| 2022-04-15 18:01:11 +0200 | <abastro[m]> | Minimal config with `xmonad desktopConfig`: crashes once a dozen click |
| 2022-04-15 18:01:11 +0200 | <abastro[m]> | My greatly complex config: Nah, I won't crash until you are least suspecting |
| 2022-04-15 18:01:47 +0200 | <abastro[m]> | Oh, you are experimenting with your own config? |
| 2022-04-15 18:02:08 +0200 | <abastro[m]> | I guess it happens less with involved config then. I cannot imagine why. |
| 2022-04-15 18:03:10 +0200 | <abastro[m]> | I guess this is related with invoking props in certain way, bare-bone config would more likely use it in certain pattern |
| 2022-04-15 18:03:12 +0200 | <abastro[m]> | I wish I could debug this |
| 2022-04-15 18:05:41 +0200 | Guest2525 | (~Guest25@151.246.65.10) |
| 2022-04-15 18:06:08 +0200 | <Guest2525> | does anyone use XMonad.Actions.DynamicWorkspaces here |
| 2022-04-15 18:08:25 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2022-04-15 18:10:13 +0200 | <geekosaur> | abastro[m], that pattern (more involved configs making it happen less often) just sounds like a bigger heap and therefore fewer opportunities to detect corruption |
| 2022-04-15 18:11:28 +0200 | <abastro[m]> | geekosaur: Makes sense! Did you try with minimal config (`xmonad desktopConfig`) yourself? |
| 2022-04-15 18:12:30 +0200 | <geekosaur> | no, because I was running my primary session and wanted to keep it working, plus I was hoping that a more involved config would make it happen more often instead of hiding it in a larger heap |
| 2022-04-15 18:13:13 +0200 | <geekosaur> | I have xephyr set up now with a default config, and would have to do some work to be able to build a config within it |
| 2022-04-15 18:38:42 +0200 | Guest2525 | (~Guest25@151.246.65.10) (Quit: Client closed) |
| 2022-04-15 18:44:24 +0200 | <geekosaur> | still setting up (gave it its own ghcup so I could set 9.2.2 within the testbed without changing my default from 8.10.7) |
| 2022-04-15 18:45:09 +0200 | <geekosaur> | will build xmonad and -contrib with package-env foo after (currently I use cabal which might be another reason I can't reproduce it, conceivably) |
| 2022-04-15 18:47:05 +0200 | <abastro[m]> | Well, I also use cabal |
| 2022-04-15 18:47:30 +0200 | <geekosaur> | buildscript? |
| 2022-04-15 18:47:40 +0200 | <abastro[m]> | Yep |
| 2022-04-15 18:48:10 +0200 | <abastro[m]> | I set up a thin wrapper around cabal install for build script |
| 2022-04-15 18:52:07 +0200 | <geekosaur> | while I'm at it: xmonad latest release, git, something else? |
| 2022-04-15 18:53:26 +0200 | <geekosaur> | wait, I think you said that in the ticket |
| 2022-04-15 19:00:56 +0200 | <abastro[m]> | Yep, 0.17.0 |
| 2022-04-15 19:08:17 +0200 | <geekosaur> | bleh, had to tweak $PATH in my little sandbox too. need to set up a script for that |
| 2022-04-15 19:08:40 +0200 | <geekosaur> | aeons ago I had such a setup, now I'm having to rediscover everything I'd set up before |
| 2022-04-15 19:12:23 +0200 | LordOfLand | (~GiverOfDo@user/polo) (Quit: one) |
| 2022-04-15 19:15:22 +0200 | <geekosaur> | got it set up. not crashing so far |
| 2022-04-15 19:15:48 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 19:18:30 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::d5c4) |
| 2022-04-15 19:30:51 +0200 | maybefbi | (~maybeatf@138.75.51.49) (Remote host closed the connection) |
| 2022-04-15 20:02:09 +0200 | LordOfLand | (~GiverOfDo@user/polo) (Remote host closed the connection) |
| 2022-04-15 20:02:45 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 20:06:47 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-04-15 20:08:33 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-04-15 20:25:43 +0200 | LordOfLand | (~GiverOfDo@user/polo) (Quit: one) |
| 2022-04-15 20:43:46 +0200 | <geekosaur> | I've been banging at it every so often, it's still not crashing |
| 2022-04-15 20:44:49 +0200 | <geekosaur> | I am tempted to suggest you nuke and rebuild xmonad-contrib and all its dependencies (which includes xmonad) |
| 2022-04-15 21:24:41 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving) |
| 2022-04-15 21:31:28 +0200 | LordOfLand | (~GiverOfDo@user/polo) |
| 2022-04-15 22:24:42 +0200 | <geekosaur> | well, shit. virtualbox works perfectly under xephyr. now I have to figure out what's wrong with my config |
| 2022-04-15 23:13:48 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-04-15 23:17:47 +0200 | <abastro[m]> | Hmmm |
| 2022-04-15 23:20:08 +0200 | <abastro[m]> | I wonder if the -dynamic field relevant |
| 2022-04-15 23:23:34 +0200 | <geekosaur> | possible, I build default (static) |
| 2022-04-15 23:32:56 +0200 | <geekosaur> | if it turns out that -dynamic matters, you probably do have a ghc bug and should report it |
| 2022-04-15 23:38:29 +0200 | <abastro[m]> | Hmm |
| 2022-04-15 23:38:48 +0200 | <abastro[m]> | I see, let me test that |
| 2022-04-15 23:39:47 +0200 | LordOfLand | POLO |
| 2022-04-15 23:40:49 +0200 | allbery_b | (~geekosaur@xmonad/geekosaur) |
| 2022-04-15 23:40:49 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
| 2022-04-15 23:40:52 +0200 | allbery_b | geekosaur |
| 2022-04-15 23:48:51 +0200 | <geekosaur> | -dynamic isn't making it crash here :( |
| 2022-04-15 23:57:03 +0200 | <abastro[m]> | Okay, something very weird is going on then.. |