| 2022-11-04 00:01:40 +0100 | rundown | (~eb0t@33ba0612.skybroadband.com) (Ping timeout: 248 seconds) |
| 2022-11-04 00:03:39 +0100 | rundown | (~eb0t@33ba12fa.skybroadband.com) |
| 2022-11-04 00:12:52 +0100 | rundown | (~eb0t@33ba12fa.skybroadband.com) (Ping timeout: 248 seconds) |
| 2022-11-04 00:15:10 +0100 | rundown | (~eb0t@33ba53cd.skybroadband.com) |
| 2022-11-04 00:20:04 +0100 | rundown | (~eb0t@33ba53cd.skybroadband.com) (Ping timeout: 252 seconds) |
| 2022-11-04 01:05:52 +0100 | rundown | (~eb0t@33ba2fd5.skybroadband.com) |
| 2022-11-04 01:07:58 +0100 | aliosablack | (~chomwitt@2a02:587:7a0a:6300:1ac0:4dff:fedb:a3f1) |
| 2022-11-04 01:09:21 +0100 | chomwitt | (~chomwitt@2a02:587:dc18:4a00:1ac0:4dff:fedb:a3f1) (Ping timeout: 246 seconds) |
| 2022-11-04 01:15:25 +0100 | rundown | (~eb0t@33ba2fd5.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 01:17:08 +0100 | rundown | (~eb0t@33ba0b37.skybroadband.com) |
| 2022-11-04 01:18:32 +0100 | aliosablack | (~chomwitt@2a02:587:7a0a:6300:1ac0:4dff:fedb:a3f1) (Ping timeout: 276 seconds) |
| 2022-11-04 01:23:25 +0100 | rundown | (~eb0t@33ba0b37.skybroadband.com) (Ping timeout: 255 seconds) |
| 2022-11-04 01:24:37 +0100 | rundown | (~eb0t@33ba1d53.skybroadband.com) |
| 2022-11-04 01:46:27 +0100 | rundown | (~eb0t@33ba1d53.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 01:47:53 +0100 | rundown | (~eb0t@33bacf70.skybroadband.com) |
| 2022-11-04 01:55:57 +0100 | rundown | (~eb0t@33bacf70.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 01:56:08 +0100 | rundown | (~eb0t@33ba3af7.skybroadband.com) |
| 2022-11-04 02:11:09 +0100 | rundown | (~eb0t@33ba3af7.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 02:12:23 +0100 | rundown | (~eb0t@33ba3dc3.skybroadband.com) |
| 2022-11-04 02:18:07 +0100 | rundown | (~eb0t@33ba3dc3.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 02:19:00 +0100 | rundown | (~eb0t@33ba5e3c.skybroadband.com) |
| 2022-11-04 02:25:05 +0100 | rundown | (~eb0t@33ba5e3c.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 02:26:16 +0100 | rundown | (~eb0t@33ba03bf.skybroadband.com) |
| 2022-11-04 02:26:55 +0100 | seanchapel[m] | (~seanchape@2001:470:69fc:105::2:b2e9) |
| 2022-11-04 02:34:25 +0100 | <seanchapel[m]> | Hi, I'm a newbie to xmonad and I'm having two issues. 1) I like to mod + right click to resize a window however for some reason that is toggling floating mode for the window. 2) it seems like when electron apps get notifications that the app freezes for a long time (bspwm also has this issue tho) |
| 2022-11-04 02:36:17 +0100 | <seanchapel[m]> | here is my config incase it's helpful https://seoushi.dynu.net/-/snippets/2 |
| 2022-11-04 02:44:05 +0100 | rundown | (~eb0t@33ba03bf.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 02:45:32 +0100 | rundown | (~eb0t@33ba3cf9.skybroadband.com) |
| 2022-11-04 02:50:25 +0100 | rundown | (~eb0t@33ba3cf9.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 02:51:47 +0100 | rundown | (~eb0t@33b76ee1.skybroadband.com) |
| 2022-11-04 03:05:08 +0100 | rundown | (~eb0t@33b76ee1.skybroadband.com) (Ping timeout: 248 seconds) |
| 2022-11-04 03:07:57 +0100 | rundown | (~eb0t@33bb4c0e.skybroadband.com) |
| 2022-11-04 03:20:49 +0100 | rundown | (~eb0t@33bb4c0e.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 03:22:15 +0100 | rundown | (~eb0t@33bacc6a.skybroadband.com) |
| 2022-11-04 03:30:19 +0100 | rundown | (~eb0t@33bacc6a.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 03:31:31 +0100 | rundown | (~eb0t@33bb5174.skybroadband.com) |
| 2022-11-04 03:38:19 +0100 | c209e6dc-4d76-47 | (~aditya@2601:249:4300:1296:195:dac6:592c:a55a) |
| 2022-11-04 03:51:17 +0100 | rundown | (~eb0t@33bb5174.skybroadband.com) (Ping timeout: 276 seconds) |
| 2022-11-04 03:52:46 +0100 | rundown | (~eb0t@33bb5354.skybroadband.com) |
| 2022-11-04 04:00:51 +0100 | rundown | (~eb0t@33bb5354.skybroadband.com) (Ping timeout: 246 seconds) |
| 2022-11-04 04:03:01 +0100 | rundown | (~eb0t@05453a63.skybroadband.com) |
| 2022-11-04 04:03:16 +0100 | banc- | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds) |
| 2022-11-04 04:06:18 +0100 | mvk | (~mvk@2607:fea8:5ce3:8500::4b68) (Ping timeout: 255 seconds) |
| 2022-11-04 04:24:47 +0100 | td_ | (~td@83.135.9.44) (Ping timeout: 272 seconds) |
| 2022-11-04 04:25:21 +0100 | rundown | (~eb0t@05453a63.skybroadband.com) (Ping timeout: 246 seconds) |
| 2022-11-04 04:25:45 +0100 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-11-04 04:25:55 +0100 | td_ | (~td@83.135.9.48) |
| 2022-11-04 04:27:03 +0100 | <geekosaur> | it's kinda meaningless to resize a tiled window without floating it. unless you want https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-MouseResizableTile.html |
| 2022-11-04 04:27:17 +0100 | rundown | (~eb0t@33bb498f.skybroadband.com) |
| 2022-11-04 04:28:24 +0100 | <geekosaur> | for the second one, I use Matrix sometimes and it doesn'[t seem to freeze for me. do you have a notification daemon of some kind running? a nice minimalistic one is dunst |
| 2022-11-04 04:28:35 +0100 | <geekosaur> | seanchapel[m] ^^ |
| 2022-11-04 04:30:50 +0100 | c209e6dc-4d76-47 | (~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Quit: Konversation terminated!) |
| 2022-11-04 04:34:55 +0100 | rundown | (~eb0t@33bb498f.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 04:36:32 +0100 | rundown | (~eb0t@33ba106f.skybroadband.com) |
| 2022-11-04 04:42:40 +0100 | <seanchapel[m]> | thanks. mouseresizabletile is what I want. I don't have a notif daemon running, I will try that and see if solves the issue. |
| 2022-11-04 04:43:33 +0100 | <seanchapel[m]> | from what I can tell mouse and right click still floats a window by default. I just need to figure out how to override the mouse keybindings now... doing some research |
| 2022-11-04 04:43:40 +0100 | <seanchapel[m]> | s/mouse/mod/ |
| 2022-11-04 04:44:52 +0100 | rundown | (~eb0t@33ba106f.skybroadband.com) (Ping timeout: 248 seconds) |
| 2022-11-04 04:46:48 +0100 | rundown | (~eb0t@33bb4658.skybroadband.com) |
| 2022-11-04 04:49:34 +0100 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
| 2022-11-04 04:52:08 +0100 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) |
| 2022-11-04 04:52:52 +0100 | rundown | (~eb0t@33bb4658.skybroadband.com) (Ping timeout: 248 seconds) |
| 2022-11-04 04:54:04 +0100 | rundown | (~eb0t@33bb3586.skybroadband.com) |
| 2022-11-04 04:59:52 +0100 | rundown | (~eb0t@33bb3586.skybroadband.com) (Ping timeout: 255 seconds) |
| 2022-11-04 05:01:19 +0100 | rundown | (~eb0t@33bb8e50.skybroadband.com) |
| 2022-11-04 05:50:11 +0100 | rundown | (~eb0t@33bb8e50.skybroadband.com) (Read error: Connection reset by peer) |
| 2022-11-04 05:55:35 +0100 | rundown | (~eb0t@33ba29dd.skybroadband.com) |
| 2022-11-04 06:22:10 +0100 | thunderrd | (~thunderrd@183.182.114.141) (Remote host closed the connection) |
| 2022-11-04 07:05:08 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 248 seconds) |
| 2022-11-04 07:06:05 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
| 2022-11-04 07:23:30 +0100 | chomwitt | (~chomwitt@ppp-94-69-177-170.home.otenet.gr) |
| 2022-11-04 07:31:48 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 248 seconds) |
| 2022-11-04 08:35:33 +0100 | seanchapel[m] | seoushi[m] |
| 2022-11-04 08:49:52 +0100 | thunderrd | (~thunderrd@183.182.114.141) |
| 2022-11-04 08:50:20 +0100 | mncheck | (~mncheck@193.224.205.254) |
| 2022-11-04 08:57:09 +0100 | ft | (~ft@80.141.189.89) (Quit: leaving) |
| 2022-11-04 09:02:20 +0100 | m5zs7k | (aquares@web10.mydevil.net) (Ping timeout: 252 seconds) |
| 2022-11-04 09:06:51 +0100 | m5zs7k | (aquares@web10.mydevil.net) |
| 2022-11-04 09:07:15 +0100 | rundown | (~eb0t@33ba29dd.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 09:08:58 +0100 | rundown | (~eb0t@90.194.229.248) |
| 2022-11-04 09:09:12 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 09:21:06 +0100 | cfricke | (~cfricke@user/cfricke) |
| 2022-11-04 09:23:10 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Quit: Ehllie) |
| 2022-11-04 09:23:23 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 09:35:07 +0100 | jludwig | (~justin@li657-110.members.linode.com) (Ping timeout: 272 seconds) |
| 2022-11-04 09:41:27 +0100 | rundown | (~eb0t@90.194.229.248) (Ping timeout: 272 seconds) |
| 2022-11-04 09:42:51 +0100 | rundown | (~eb0t@90.192.218.141) |
| 2022-11-04 09:52:51 +0100 | rundown | (~eb0t@90.192.218.141) (Ping timeout: 272 seconds) |
| 2022-11-04 09:53:07 +0100 | rundown | (~eb0t@33bede82.skybroadband.com) |
| 2022-11-04 09:53:44 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Quit: Ehllie) |
| 2022-11-04 09:53:57 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 09:58:11 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 246 seconds) |
| 2022-11-04 10:05:07 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 10:34:01 +0100 | rundown | (~eb0t@33bede82.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 10:35:23 +0100 | rundown | (~eb0t@33b76a67.skybroadband.com) |
| 2022-11-04 10:42:53 +0100 | rundown | (~eb0t@33b76a67.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 10:44:38 +0100 | rundown | (~eb0t@33beec1c.skybroadband.com) |
| 2022-11-04 10:48:09 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:470d:6245:cbff:fe9f:48b1) |
| 2022-11-04 10:50:01 +0100 | <thyriaen> | I just started up my pc and created 2 workspaces on my main monitor running independentScreens - then when i kept switching from workspace 1 and 2 - something really strange happened - xmonad switched the windows between workspace 1 and 2 between the monitors, however both workspaces "0_1" and "0_2" are supposed to "belong" to screen 1 |
| 2022-11-04 10:50:24 +0100 | <thyriaen> | maybe it is of interest: i didn't have any windows on screen 2 nor did i click there once giving it focus |
| 2022-11-04 10:50:43 +0100 | <thyriaen> | https://paste.tomsmeding.com/tW5WjuR5 this is my xmonad.hs |
| 2022-11-04 10:54:38 +0100 | jludwig | (~justin@li657-110.members.linode.com) |
| 2022-11-04 11:06:58 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 246 seconds) |
| 2022-11-04 11:14:02 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 11:15:18 +0100 | jludwig | (~justin@li657-110.members.linode.com) (Quit: ZNC - https://znc.in) |
| 2022-11-04 11:22:18 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 255 seconds) |
| 2022-11-04 11:23:57 +0100 | rundown | (~eb0t@33beec1c.skybroadband.com) (Ping timeout: 246 seconds) |
| 2022-11-04 11:25:55 +0100 | rundown | (~eb0t@33bee049.skybroadband.com) |
| 2022-11-04 11:31:37 +0100 | <thyriaen> | I have a two pane layout - how can i move a window from the left pane to the right pane and back ? |
| 2022-11-04 11:32:58 +0100 | jludwig | (~justin@li657-110.members.linode.com) |
| 2022-11-04 11:42:25 +0100 | rundown | (~eb0t@33bee049.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 11:44:39 +0100 | rundown | (~eb0t@51.186.31.24) |
| 2022-11-04 11:55:05 +0100 | rundown | (~eb0t@51.186.31.24) (Ping timeout: 268 seconds) |
| 2022-11-04 11:56:56 +0100 | rundown | (~eb0t@33ba0397.skybroadband.com) |
| 2022-11-04 11:59:00 +0100 | chomwitt | (~chomwitt@ppp-94-69-177-170.home.otenet.gr) (Ping timeout: 248 seconds) |
| 2022-11-04 12:25:18 +0100 | rundown | (~eb0t@33ba0397.skybroadband.com) (Ping timeout: 255 seconds) |
| 2022-11-04 12:28:00 +0100 | rundown | (~eb0t@33bb3ffc.skybroadband.com) |
| 2022-11-04 12:30:52 +0100 | rundown | (~eb0t@33bb3ffc.skybroadband.com) (Read error: Connection reset by peer) |
| 2022-11-04 12:35:17 +0100 | rundown | (~eb0t@33bb3ffc.skybroadband.com) |
| 2022-11-04 12:40:41 +0100 | rundown | (~eb0t@33bb3ffc.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 12:41:56 +0100 | rundown | (~eb0t@33ba0b3b.skybroadband.com) |
| 2022-11-04 13:08:26 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 13:11:05 +0100 | rundown | (~eb0t@33ba0b3b.skybroadband.com) (Ping timeout: 272 seconds) |
| 2022-11-04 13:13:50 +0100 | rundown | (~eb0t@33bef03f.skybroadband.com) |
| 2022-11-04 13:19:45 +0100 | rundown | (~eb0t@33bef03f.skybroadband.com) (Ping timeout: 255 seconds) |
| 2022-11-04 13:21:05 +0100 | rundown | (~eb0t@90.192.218.221) |
| 2022-11-04 13:30:54 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Quit: Ehllie) |
| 2022-11-04 13:31:06 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 13:37:22 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2022-11-04 13:37:44 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2022-11-04 13:43:50 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2022-11-04 13:44:09 +0100 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2022-11-04 13:49:25 +0100 | <geekosaur> | thyriaen, you probably want to set up WindowNavigation to move windows between panes |
| 2022-11-04 13:50:18 +0100 | <geekosaur> | as to the other, probably you were supposed to replace W.view with W.greedyView |
| 2022-11-04 14:14:29 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Quit: Ehllie) |
| 2022-11-04 14:14:38 +0100 | Ehllie1 | (~Thunderbi@217-67-208-66.itsa.net.pl) |
| 2022-11-04 14:16:59 +0100 | Ehllie1 | Ehllie |
| 2022-11-04 14:43:01 +0100 | <thyriaen> | if you check my xmonad.sh |
| 2022-11-04 14:43:08 +0100 | <thyriaen> | i already have greedyView geekosaur |
| 2022-11-04 14:44:18 +0100 | <geekosaur> | yeh, I think I had that backwards. greedyView flips things so the ws you're focusing moves to the current monoitor. you want view |
| 2022-11-04 14:44:20 +0100 | <thyriaen> | and i think i already did setup windowNavigatioin |
| 2022-11-04 14:44:49 +0100 | <geekosaur> | then you want to use the bindings for `sendMessage (Move L)` etc. |
| 2022-11-04 14:44:51 +0100 | <thyriaen> | ( but usually it works ) it flipped it only this morning |
| 2022-11-04 14:52:11 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:470d:6245:cbff:fe9f:48b1) (Remote host closed the connection) |
| 2022-11-04 14:53:01 +0100 | chomwitt | (~chomwitt@athedsl-351939.home.otenet.gr) |
| 2022-11-04 15:44:59 +0100 | Ehllie | (~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 272 seconds) |
| 2022-11-04 15:47:08 +0100 | rundown | (~eb0t@90.192.218.221) (Ping timeout: 246 seconds) |
| 2022-11-04 15:49:21 +0100 | rundown | (~eb0t@90.192.219.29) |
| 2022-11-04 16:00:51 +0100 | Heyting | (~Heyting@193.198.16.217) |
| 2022-11-04 16:01:06 +0100 | Ehllie | (~Thunderbi@user-5-173-164-55.play-internet.pl) |
| 2022-11-04 16:02:51 +0100 | Heyting | (~Heyting@193.198.16.217) (Quit: Connection closed) |
| 2022-11-04 16:16:22 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-11-04 16:18:19 +0100 | Ehllie1 | (~Thunderbi@user-5-173-164-55.play-internet.pl) |
| 2022-11-04 16:18:22 +0100 | Ehllie | (~Thunderbi@user-5-173-164-55.play-internet.pl) (Read error: Connection reset by peer) |
| 2022-11-04 16:18:22 +0100 | Ehllie1 | Ehllie |
| 2022-11-04 16:21:55 +0100 | jludwig | (~justin@li657-110.members.linode.com) (Quit: ZNC - https://znc.in) |
| 2022-11-04 16:22:54 +0100 | jludwig | (~justin@li657-110.members.linode.com) |
| 2022-11-04 16:37:33 +0100 | Ehllie | (~Thunderbi@user-5-173-164-55.play-internet.pl) (Read error: Connection reset by peer) |
| 2022-11-04 16:57:29 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-11-04 17:00:05 +0100 | quarkQuark[m] | (~quarkquar@2001:470:69fc:105::2:46e2) (Quit: You have been kicked for being idle) |
| 2022-11-04 17:00:09 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-11-04 17:01:02 +0100 | <jabuxas> | I seem to be having a problem with a game on steam on xmonad, the game works perfectly on xfce and awesome (as far as I can tell, i'm testing on awesome rn and it is working), but on xmonad, the game launches and I can play, but, after 10-15 minutes the game and xmonad crashes and I'm forced to log out and log back in. |
| 2022-11-04 17:01:22 +0100 | <jabuxas> | https://0x0.st/ogEh.txt xmonad config |
| 2022-11-04 17:01:26 +0100 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-11-04 17:11:05 +0100 | <geekosaur> | can you check your session log (usually ~/.xsession-errors but sddm uses ~/.local/share/sddm/xorg-session.log and startx will log to the original virtual console unless redirected) to see if any errors are logged from xmonad? |
| 2022-11-04 17:15:59 +0100 | ft | (~ft@p508dbd59.dip0.t-ipconnect.de) |
| 2022-11-04 17:21:05 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Remote host closed the connection) |
| 2022-11-04 17:22:07 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-11-04 17:26:33 +0100 | <jabuxas> | https://0x0.st/og6v.txt |
| 2022-11-04 17:27:39 +0100 | <jabuxas> | the game crashed right at startup. also the logs don't seem useful, maybe i'm not getting the right ones? |
| 2022-11-04 17:27:53 +0100 | <jabuxas> | my whole xmonad turns unresponsive after this and i'm forced to log out and log back in |
| 2022-11-04 17:28:18 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Remote host closed the connection) |
| 2022-11-04 17:29:17 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2022-11-04 17:36:57 +0100 | <jabuxas> | should I try to go on awesome and see if those `Unknown property in AccoladeProgressId` happens there too? |
| 2022-11-04 17:39:50 +0100 | <geekosaur> | you can check but that looks a little early |
| 2022-11-04 17:39:57 +0100 | tremon | (~tremon@83-84-18-241.cable.dynamic.v4.ziggo.nl) |
| 2022-11-04 17:40:16 +0100 | <geekosaur> | also you appear to have DynamicLog configured somewhat oddly for modern xmonad; I'll have to check your config re that |
| 2022-11-04 17:40:25 +0100 | <geekosaur> | but it's at least not going to block |
| 2022-11-04 17:41:26 +0100 | <geekosaur> | it should not be possible for a user config to cause xmonad to crash, unless it's doing non-xmonad things. I didn't actually look at your config because I was more interested in any error logs, guess that's next |
| 2022-11-04 17:44:14 +0100 | <jabuxas> | the game is crashing xmonad, idk how, I was thinking that maybe it's a core thing that my xmonad.hs is missing but i'm not sure |
| 2022-11-04 17:47:59 +0100 | <geekosaur> | I don't see anything missing |
| 2022-11-04 17:48:56 +0100 | <geekosaur> | I did see why there are DynamicLog outputs in your logfile… why do you have `logHook = dynamicLogWithPP . filterOutWsPP ["NSP"] $ def` ? |
| 2022-11-04 17:49:26 +0100 | <geekosaur> | it won't affect the PPs that are actually used for output, it'll just spit stuff to xmonad's stdout |
| 2022-11-04 17:51:01 +0100 | OpenSource | (~kernel@user/OpenSource) (Quit: ZNC - https://znc.in) |
| 2022-11-04 17:51:17 +0100 | OpenSource | (~kernel@user/OpenSource) |
| 2022-11-04 17:51:28 +0100 | <jabuxas> | I thought that was how I made NSP workspace (which is a scratchpad) gone from my bar. It doesn't actually work because that's probably implemented wrongly as you said, but I can take that off no problem |
| 2022-11-04 17:51:29 +0100 | <geekosaur> | you would want to apply filterOutWsPP to myXmobarPP, not there |
| 2022-11-04 17:52:02 +0100 | <geekosaur> | in any case it's not really doing anything aside from proving that your log is a log 🙂 |
| 2022-11-04 17:52:23 +0100 | <geekosaur> | (that is, that it's capturing xmonad's output) |
| 2022-11-04 17:52:23 +0100 | rundown | (~eb0t@90.192.219.29) (Ping timeout: 276 seconds) |
| 2022-11-04 17:52:58 +0100 | <jabuxas> | oh yeah put it in myxmobarpp now works |
| 2022-11-04 17:53:32 +0100 | <jabuxas> | my friend also seems to be crashing on kde, and i'm crashing on xmonad |
| 2022-11-04 17:53:38 +0100 | rundown | (~eb0t@90.202.12.12) |
| 2022-11-04 17:53:55 +0100 | <jabuxas> | i'm not sure the relationship between that, as I can run fine on awesome and xfce (plus im on gentoo) and he's on arch |
| 2022-11-04 17:55:59 +0100 | OpenSource | (~kernel@user/OpenSource) (Client Quit) |
| 2022-11-04 17:56:04 +0100 | <jabuxas> | I tried running xmonad on xfce but I couldn't get it working without dramastically changing my config, xmobar wasn't showing up, xfce panels were invisible, and 2nd monitor workspaces looked rather odd, I tried that because I thought that maybe it was missing something but as you said, it isn't so that is out of the way |
| 2022-11-04 17:58:59 +0100 | <jabuxas> | I thought maybe the compositor (picom) was crashing the game but that would also not make sense since I run picom on xfce and awesome too (i tried without it just in case and it's the same) |
| 2022-11-04 18:08:24 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:18:12 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 18:18:37 +0100 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.7.1) |
| 2022-11-04 18:18:57 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:20:28 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 18:21:09 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:21:24 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 18:22:03 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:25:01 +0100 | sadmax | (~user@209.205.174.253) (Client Quit) |
| 2022-11-04 18:26:45 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:28:24 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 18:29:12 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:29:50 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 18:30:41 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 18:36:41 +0100 | thunderrd | (~thunderrd@183.182.114.141) (Remote host closed the connection) |
| 2022-11-04 18:38:17 +0100 | thunderrd | (~thunderrd@183.182.114.141) |
| 2022-11-04 18:38:44 +0100 | thunderrd | (~thunderrd@183.182.114.141) (Remote host closed the connection) |
| 2022-11-04 18:39:41 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 19:06:54 +0100 | stackdroid18 | (14094@user/stackdroid) |
| 2022-11-04 19:08:35 +0100 | <jabuxas> | I seem to have figured it out, geekosaur. |
| 2022-11-04 19:08:55 +0100 | <jabuxas> | I took DXVK_ASYNC off of my launch parameters and now, after 1 hour of gameplay, still no crashes. |
| 2022-11-04 19:09:25 +0100 | <jabuxas> | what I would hope to know now is why that is a problem on xmonad and not on other things i've tested |
| 2022-11-04 19:09:47 +0100 | <jabuxas> | i have no problem playing with that off so yeah problem kinda solved |
| 2022-11-04 19:11:03 +0100 | <geekosaur> | possibly we don't initialize the video card when other things do, xmonad being minimal and DXVK appearing to be related to 3D drawing |
| 2022-11-04 19:11:22 +0100 | <geekosaur> | so maybe there's something you can run at session startup |
| 2022-11-04 19:12:23 +0100 | <geekosaur> | (alternately it's conceivable that the DXVK async code doesn't like borders much. we've seen that kind of thing before; nvidia drivers used to have horrible problems there) |
| 2022-11-04 19:13:19 +0100 | <geekosaur> | which may mean it's not xmonad that's crashing but the X server. /var/log/Xorg.0.log usually |
| 2022-11-04 19:13:33 +0100 | <geekosaur> | (a new server would be launched for the greeter) |
| 2022-11-04 19:16:39 +0100 | <geekosaur> | hm, might have to hope it backs up the old log since the greeter's restart of the X server would overwrite it |
| 2022-11-04 19:17:08 +0100 | <geekosaur> | yeh, I have /var/log/Xorg.0.log.old on my ubuntu |
| 2022-11-04 19:17:41 +0100 | <geekosaur> | but you'd have to use a terminal session to grab it, logging in under X would replace it with the greeter server's log |
| 2022-11-04 19:20:16 +0100 | <jabuxas> | if X crashed wouldn't my gui just dissapear automatically? |
| 2022-11-04 19:21:15 +0100 | <jabuxas> | because when the game crashed, my cpu fans would go up and if I opened a terminal for example, my prompt wouldn't appear, my keyboard wouldn't really type anything, usually that's some I/O stuff |
| 2022-11-04 19:22:43 +0100 | <jabuxas> | I do have https://0x0.st/oglx.txt , it *should* be from my last startX (when it crashed) |
| 2022-11-04 19:23:03 +0100 | <geekosaur> | you should have mentioned that |
| 2022-11-04 19:23:36 +0100 | <geekosaur> | in any case that's not an xmonad crash as such, *that* would have dumped you back to the greeter |
| 2022-11-04 19:24:26 +0100 | <geekosaur> | so now I wonder if the game is spinning for some reason |
| 2022-11-04 19:26:16 +0100 | <jabuxas> | my bad |
| 2022-11-04 19:28:05 +0100 | <geekosaur> | I have a still-undiagnosed situation where something is eating all of my memory and OOMing, and xmonad disappears without a log message (strongly suggesting it's xmonad that is OOMing, but I can't see how) |
| 2022-11-04 19:28:33 +0100 | <geekosaur> | but it leaves the rest of my session because I run xmonad under MATE so mate-session is still running |
| 2022-11-04 19:29:12 +0100 | <geekosaur> | was wondering of that might be related, but unless you're running under a session manager xmonad OOMing would kill your session |
| 2022-11-04 19:29:16 +0100 | <geekosaur> | *if that |
| 2022-11-04 19:29:53 +0100 | <geekosaur> | might use top if you can get something to respond (already-open terminal?) to see what's spinning |
| 2022-11-04 19:30:47 +0100 | <jabuxas> | yeah I'll remember to do that, i usually have a terminal open either way |
| 2022-11-04 19:31:29 +0100 | <geekosaur> | but that again might require a session manager if xmonad is what's spinning, since it would presumably ignore switching focus in that situation |
| 2022-11-04 19:32:34 +0100 | <jabuxas> | oh it does respond to focus |
| 2022-11-04 19:32:41 +0100 | <geekosaur> | hm, I can open a terminal without requiring xmonad but if it were still running it'd have to manage it. so still wouldn't help |
| 2022-11-04 19:32:45 +0100 | <geekosaur> | oh goood |
| 2022-11-04 19:33:59 +0100 | <jabuxas> | by session manager do you mean a display manager like sddm or lightdm? |
| 2022-11-04 19:34:20 +0100 | <geekosaur> | no, something like xfce4-session or mate-session |
| 2022-11-04 19:34:32 +0100 | <geekosaur> | or even a minimal one like xsm |
| 2022-11-04 19:34:45 +0100 | <jabuxas> | oh i dont have that |
| 2022-11-04 19:35:31 +0100 | <jabuxas> | well even if it lost focus, i could still switch to a tty and do top there |
| 2022-11-04 19:35:39 +0100 | <geekosaur> | I rely on that to get5 things running again if I manage to crash xmonad, since (1) my session keeps running (2) I can pop a terminal via the mate menu without a window manager being involved, and restart xmonad from there |
| 2022-11-04 19:35:45 +0100 | <jabuxas> | now i am kinda hoping it crashes again so i can figure out what it culd be |
| 2022-11-04 19:36:58 +0100 | <jabuxas> | with the way my config is now, if i were to use xmonad with a DE would I really need to change anything? |
| 2022-11-04 19:37:23 +0100 | <jabuxas> | i looked at xmonad.config.xfce and it just does ewmh stuff, no? |
| 2022-11-04 19:38:29 +0100 | <geekosaur> | also swaps mod-shift-q to the xfce logout dialog and mod-p (or maybe mod-shift-p) to its run dialog |
| 2022-11-04 19:39:16 +0100 | <geekosaur> | xfce's one of the more minimal integrations; mate integration also includes some dbus stuff to tell the session manager that xmonad has started |
| 2022-11-04 19:40:36 +0100 | <geekosaur> | if you did want to log some xmobar-like stuff under xfce, you'd either have to configure xmobar to display somewhere other than where xfce4-panel was or you'd have to build the xfce flavor of xmonad-log-applet and plumb it into your config manually because it uses dbus |
| 2022-11-04 19:43:37 +0100 | <jabuxas> | my xfce panel is on the left of the screen and xmobar on top, but even like that both were invisible, no idea what happened. i might try it out at a later date if i have time |
| 2022-11-04 19:43:44 +0100 | <jabuxas> | for now everything is working |
| 2022-11-04 19:44:24 +0100 | <jabuxas> | ty again geekosaur |
| 2022-11-04 19:51:43 +0100 | darkkaster | (~user@206.62.170.243) |
| 2022-11-04 19:53:25 +0100 | <darkkaster> | I get this error when I start xorg https://termbin.com/omhg |
| 2022-11-04 19:59:32 +0100 | darkkaster | (~user@206.62.170.243) (Quit: ERC 5.4 (IRC client for GNU Emacs 28.2)) |
| 2022-11-04 20:02:01 +0100 | darkkaster | (~user@206.62.170.243) |
| 2022-11-04 20:02:44 +0100 | <geekosaur> | are you just runing xmonad at a terminal? |
| 2022-11-04 20:03:04 +0100 | <geekosaur> | hm, no, that would be an openDisplay error |
| 2022-11-04 20:04:04 +0100 | <geekosaur> | but we only use the required Atoms on startup, and should be creating e.g. the EWMH atoms as needed |
| 2022-11-04 20:04:27 +0100 | <darkkaster> | i run xmonad using xinitrc but redirect the output to a text file |
| 2022-11-04 20:08:27 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds) |
| 2022-11-04 20:12:02 +0100 | <geekosaur> | X_ChangeProperty error… doesn't seem like we should be doing that |
| 2022-11-04 20:12:31 +0100 | <geekosaur> | oh, WM_STATE. but if that atom's not defined (or its type isn't defined) there should be bigger problems than just xmonad failing |
| 2022-11-04 20:12:50 +0100 | sogens | (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-11-04 20:14:00 +0100 | <geekosaur> | sometimes I wish we used the standard error reporter, be nice to have a clue about where / when this was failing |
| 2022-11-04 20:14:11 +0100 | <geekosaur> | then again xmonad should be continuing after this |
| 2022-11-04 20:14:23 +0100 | <geekosaur> | because the error handler we use tries to recover |
| 2022-11-04 20:17:30 +0100 | darkkaster | (~user@206.62.170.243) (Remote host closed the connection) |
| 2022-11-04 20:19:50 +0100 | darkkaster | (~user@206.62.170.243) |
| 2022-11-04 20:22:12 +0100 | darkkaster | (~user@206.62.170.243) (Remote host closed the connection) |
| 2022-11-04 20:48:56 +0100 | Guest47 | (~Guest47@171.79.46.173) |
| 2022-11-04 20:56:32 +0100 | <jabuxas> | is this normal? https://0x0.st/ogUD.png both xmobars consuming ~4% cpu |
| 2022-11-04 21:01:38 +0100 | Guest47 | (~Guest47@171.79.46.173) (Ping timeout: 260 seconds) |
| 2022-11-04 21:12:04 +0100 | geekosaur | has no clue |
| 2022-11-04 21:18:12 +0100 | <jabuxas> | Solid, what do you think? |
| 2022-11-04 21:19:10 +0100 | <geekosaur> | istr that liskin worked a bit on xmobar performance, but I don't know what current "normal" is |
| 2022-11-04 21:55:26 +0100 | td_ | (~td@83.135.9.48) (Read error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number) |
| 2022-11-04 22:00:43 +0100 | td_ | (~td@83.135.9.48) |
| 2022-11-04 22:08:01 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-11-04 22:09:42 +0100 | <jabuxas> | hmm |
| 2022-11-04 22:11:19 +0100 | td_ | (~td@83.135.9.48) (Ping timeout: 272 seconds) |
| 2022-11-04 22:13:01 +0100 | td_ | (~td@83.135.9.48) |
| 2022-11-04 22:37:45 +0100 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 255 seconds) |
| 2022-11-04 22:49:28 +0100 | mojowings[m] | (~mojowings@2001:470:69fc:105::2:b42f) |
| 2022-11-04 22:51:20 +0100 | <mojowings[m]> | I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 22:54:26 +0100 | <mojowings[m]> | * I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 22:54:26 +0100 | <mojowings[m]> | When I set hybrid use of integrated and nvidia (or strict use of nvidia), starting xmonad with startx results in an entirely black screen where I am unable to open terminals. Xmonad is running and does not crash. If I restrict to integrated only, then I can use xmonad as expected. I am happy to investigate anything on my end to facilitate this, but I'm unsure where to start. |
| 2022-11-04 22:55:50 +0100 | <mojowings[m]> | * I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 22:55:50 +0100 | <mojowings[m]> | When I set hybrid use of integrated and nvidia (or strict use of nvidia), starting xmonad with startx (or via the login manager) results in an entirely black screen where I am unable to open terminals. Xmonad is running and does not crash. If I restrict to integrated only, then I can use xmonad as expected. I am happy to investigate anything on my end to facilitate this, but I'm unsure where to start. |
| 2022-11-04 22:59:31 +0100 | <jabuxas> | what distro are you using and how are the drivers installed? |
| 2022-11-04 23:00:35 +0100 | <mojowings[m]> | I am using pop!_os which handles these things for me. |
| 2022-11-04 23:02:07 +0100 | <jabuxas> | oh yeah stupid question of me, totally forgot pop os is from system76 |
| 2022-11-04 23:03:05 +0100 | <jabuxas> | do you have any other wm installed where you can try and launch to see if it works as expected? |
| 2022-11-04 23:03:16 +0100 | <mojowings[m]> | * No worries! I am usually a debian or ubuntu user but pop os is based on ubuntu. Typically xmonad works fine for me on ubuntu so I was surprised by this. |
| 2022-11-04 23:04:54 +0100 | <mojowings[m]> | ahhh no i dont. it does work in integrated only mode. i wish there was a straightforward way to debug this but it probably involves x11 understanding etc... |
| 2022-11-04 23:15:09 +0100 | <geekosaur> | can you post your Xorg.0.log to a pastebin? |
| 2022-11-04 23:15:13 +0100 | <geekosaur> | @where paste |
| 2022-11-04 23:15:13 +0100 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2022-11-04 23:15:35 +0100 | <geekosaur> | should be /var/log/Xorg.0.log |
| 2022-11-04 23:41:05 +0100 | thaumavorio | (~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2022-11-04 23:43:36 +0100 | stackdroid18 | (14094@user/stackdroid) (Quit: hasta la vista... tchau!) |
| 2022-11-04 23:43:59 +0100 | thaumavorio | (~thaumavor@thaumavor.io) |
| 2022-11-04 23:44:26 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 23:47:51 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:48:41 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 23:51:22 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:52:14 +0100 | sogens | (sogens@gateway/vpn/protonvpn/sogens) (Ping timeout: 246 seconds) |
| 2022-11-04 23:53:07 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 23:53:31 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:54:13 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 23:55:09 +0100 | sogens | (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-11-04 23:55:17 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:56:46 +0100 | sadmax | (~user@209.205.174.253) |
| 2022-11-04 23:57:53 +0100 | sadmax | (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:58:45 +0100 | sadmax | (~user@209.205.174.253) |
