| 2023-01-27 00:10:22 +0100 | thyriaen | (~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1) (Remote host closed the connection) |
| 2023-01-27 00:29:25 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |
| 2023-01-27 00:47:17 +0100 | scrungus | (~scrungus@bras-base-aurron9127w-grc-54-70-24-71-72.dsl.bell.ca) |
| 2023-01-27 00:49:52 +0100 | <scrungus> | Hi, I'm guessing you guys get a lot of questions from newbies but I'm having a weird issue that I just can't seem to figure out. |
| 2023-01-27 00:49:52 +0100 | <scrungus> | I have three monitors and by default xmonad behaves fine (but my monitors are out of order) but after I use xrandr to put my monitors in the right order, the workspace that's on my center monitor is only put into focus when my mouse is on another monitor. It's either the right or left one depending on what I set as my primary monitor. |
| 2023-01-27 00:50:25 +0100 | <scrungus> | I'm not sure if this is specifically an xmonad issue but I haven't found anyone who's described the same thing online. |
| 2023-01-27 00:51:53 +0100 | <geekosaur> | if you haven't changed the default bindings then only the primary monitor should ever have focus |
| 2023-01-27 00:53:24 +0100 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyView_with_view |
| 2023-01-27 00:55:55 +0100 | <scrungus> | I've read that, I don't think it's related to my issue. I can switch to the workspace I want but I just can't use my mouse in it because if my mouse moves to the workspace it focuses on a workspace on a different monitor |
| 2023-01-27 00:56:20 +0100 | <scrungus> | So I can use applications that require a mouse on a workspace that's on the monitor that's behaving strangely |
| 2023-01-27 00:56:28 +0100 | <geekosaur> | that… seems wrong. do you have a config? |
| 2023-01-27 00:57:52 +0100 | <geekosaur> | @where paste |
| 2023-01-27 00:57:52 +0100 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2023-01-27 00:57:58 +0100 | <scrungus> | I was just following the quickstart guide on the website. I setup the bar but I didn't change anything related to the bahaviour of workspaces I don't think |
| 2023-01-27 00:57:59 +0100 | <scrungus> | Okay |
| 2023-01-27 01:03:39 +0100 | <scrungus> | https://paste.tomsmeding.com/ghE9cgri |
| 2023-01-27 01:04:00 +0100 | <scrungus> | This is my xmonad.hs and xinitrc |
| 2023-01-27 01:04:28 +0100 | <scrungus> | Sorry if I just did something really dumb and didn't realize :p |
| 2023-01-27 01:08:09 +0100 | <geekosaur> | looks fine to me including the xrandr settings (weird things can happen if you get the screen offsets wrong) |
| 2023-01-27 01:08:37 +0100 | <geekosaur> | I had been wondering f you perhaps XMonad.Actions.Warp set up and possibly misconfigured |
| 2023-01-27 01:09:07 +0100 | <scrungus> | I don't know what that is so I don't think so. I hadn't really started configuring much yet since I wanted to get this sorted out first |
| 2023-01-27 01:09:40 +0100 | <scrungus> | I've just been troubleshooting. |
| 2023-01-27 01:10:19 +0100 | <scrungus> | I actually used arandr to generate my xrandr config so I might try doing it manually to make sure it wasn't doing thing wrong in a way that I didn't realise |
| 2023-01-27 01:11:49 +0100 | <scrungus> | I thought I would check here to see if it was a problem other people had ran into before. I'm guessing it has to be xrandr or something else sending slightly weird values for my monitors to xmonad that's confusing it |
| 2023-01-27 01:12:35 +0100 | <geekosaur> | I think you'd have to have overlapping values for it to do that, but I checked the xrandr config and it's not overlapping |
| 2023-01-27 01:13:56 +0100 | <geekosaur> | arandr shouldn't be capable of outputting overlapping or gapped xrandr configurations anyway; I'd have recommended using it if you had written the xrandr config yourself |
| 2023-01-27 01:14:25 +0100 | <scrungus> | Yeah that's true. I probably took the less error-prone path already in that regard |
| 2023-01-27 01:15:04 +0100 | <scrungus> | I might try unplugging some of my monitors at a time to see if I can diagnose anything else about the issue.The weird thing is how it seems to work fine when they're out of order. By which I mean how xmonad behaves is how I would expect |
| 2023-01-27 01:15:20 +0100 | <geekosaur> | hrm |
| 2023-01-27 01:15:40 +0100 | <geekosaur> | that sounds like we missed a rescreen somehow |
| 2023-01-27 01:15:50 +0100 | <geekosaur> | does mod-n do anything? |
| 2023-01-27 01:16:14 +0100 | <scrungus> | No it doesn't |
| 2023-01-27 01:16:24 +0100 | <scrungus> | What is it supposed to do? I'm not super familiar with the keybindings |
| 2023-01-27 01:16:30 +0100 | <geekosaur> | …wait, we can't have missed it, you rearrange the screens before starting xmonad and we should get the current xrandr setup |
| 2023-01-27 01:16:36 +0100 | <geekosaur> | it does a forced rescreen |
| 2023-01-27 01:16:39 +0100 | <scrungus> | Oh I see |
| 2023-01-27 01:17:27 +0100 | <scrungus> | Yeah that's the weird part. It really seems like xmonad is still partially relying on the old default value or something but that shouldn't be possible |
| 2023-01-27 01:17:40 +0100 | <scrungus> | And I've just been using startx |
| 2023-01-27 01:17:49 +0100 | <geekosaur> | unless the video driver is doing something screwy, which has been known to happen |
| 2023-01-27 01:18:01 +0100 | <scrungus> | That's possible. |
| 2023-01-27 01:18:17 +0100 | <geekosaur> | okay, if you used stack to set up xmonad, run `stack ghci`. otherwise, run `ghci` |
| 2023-01-27 01:18:32 +0100 | <scrungus> | Okay |
| 2023-01-27 01:18:40 +0100 | <geekosaur> | at the prompt, enter: openDisplay "" >>= getCleanedScreenInfo |
| 2023-01-27 01:19:24 +0100 | <geekosaur> | this should print a list of rectangles |
| 2023-01-27 01:19:46 +0100 | <scrungus> | Hm, "variable not in scope" |
| 2023-01-27 01:19:56 +0100 | <scrungus> | That's probably not good :p |
| 2023-01-27 01:20:04 +0100 | <geekosaur> | hm. are you in your xmonad config directory? |
| 2023-01-27 01:20:37 +0100 | <geekosaur> | you'll need to be for this to work |
| 2023-01-27 01:20:58 +0100 | <scrungus> | Okay I wasn't but I switched to it and it's saying the same thing |
| 2023-01-27 01:21:00 +0100 | <geekosaur> | it's possible you need to do `import XMonad` first |
| 2023-01-27 01:21:05 +0100 | <scrungus> | Oh probably |
| 2023-01-27 01:21:13 +0100 | <scrungus> | So those are xmonad functions right? |
| 2023-01-27 01:21:29 +0100 | <scrungus> | Okay it worked |
| 2023-01-27 01:21:55 +0100 | <scrungus> | ghci> openDisplay "" >>= getCleanedScreenInfo |
| 2023-01-27 01:21:56 +0100 | <scrungus> | [Rectangle {rect_x = 3840, rect_y = 0, rect_width = 1920, rect_height = 1080},Rectangle {rect_x = 1920, rect_y = 0, rect_width = 1920, rect_height = 1080},Rectangle {rect_x = 0, rect_y = 0, rect_width = 1920, rect_height = 1080}] |
| 2023-01-27 01:21:56 +0100 | <scrungus> | ghci> |
| 2023-01-27 01:22:01 +0100 | <geekosaur> | okay, so the rectangles in order should reflect what you have in the xrandr command |
| 2023-01-27 01:22:53 +0100 | <scrungus> | What is "rect_x = 3840" referring to? |
| 2023-01-27 01:23:36 +0100 | <geekosaur> | the "x" part of the `--pos` parameter, which is `x`x`y` |
| 2023-01-27 01:24:46 +0100 | <scrungus> | I guess tit's not the same order |
| 2023-01-27 01:24:50 +0100 | <scrungus> | it's* |
| 2023-01-27 01:24:56 +0100 | <geekosaur> | looks to me like the rectangles are sorted by reverse x offset |
| 2023-01-27 01:25:07 +0100 | <geekosaur> | which is odd |
| 2023-01-27 01:25:42 +0100 | <scrungus> | Why would that happen then? |
| 2023-01-27 01:26:34 +0100 | <geekosaur> | that's almost always the video driver's fault; it's supposed to report them in xrandr order |
| 2023-01-27 01:26:48 +0100 | <scrungus> | So I should look into my video drivers? |
| 2023-01-27 01:27:04 +0100 | <geekosaur> | https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Screens_are_in_wrong_order might help, although it's a bit of work and won't help with the mouse. the PhysicalScreens module might work better here |
| 2023-01-27 01:27:24 +0100 | <geekosaur> | it sounds like it, yes |
| 2023-01-27 01:27:36 +0100 | <scrungus> | Would the physical screens module be able negate this issue you think? |
| 2023-01-27 01:28:26 +0100 | <geekosaur> | it lets you rearrange the screen rectangles as xmonad sees them, instead of just remapping the screen-focusing keys like the first link I gave you. so it should work |
| 2023-01-27 01:29:19 +0100 | <scrungus> | Well thank you so much for helping me out! |
| 2023-01-27 01:29:28 +0100 | <scrungus> | I'm always worried about being annoying when I ask for help with stuff |
| 2023-01-27 01:29:44 +0100 | <geekosaur> | no problem, it's what we're here for |
| 2023-01-27 01:31:06 +0100 | <scrungus> | My path here was actually that I started learning Haskell and I found out about xmonad and I was kind of surprised and wanted to use it. I've used tiling WMs before but not a dynamic one so it's been interesting |
| 2023-01-27 01:34:48 +0100 | scrungus | (~scrungus@bras-base-aurron9127w-grc-54-70-24-71-72.dsl.bell.ca) (Quit: Client closed) |
| 2023-01-27 01:54:34 +0100 | td_ | (~td@i53870925.versanet.de) (Ping timeout: 260 seconds) |
| 2023-01-27 01:56:06 +0100 | td_ | (~td@i53870931.versanet.de) |
| 2023-01-27 01:57:16 +0100 | yaslam | (~yaslam@user/yaslam) |
| 2023-01-27 01:57:36 +0100 | yaslam | (~yaslam@user/yaslam) () |
| 2023-01-27 04:02:55 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 248 seconds) |
| 2023-01-27 04:18:04 +0100 | td_ | (~td@i53870931.versanet.de) (Ping timeout: 260 seconds) |
| 2023-01-27 04:19:35 +0100 | td_ | (~td@i53870938.versanet.de) |
| 2023-01-27 04:24:23 +0100 | banc | (banc@gateway/vpn/protonvpn/banc) |
| 2023-01-27 04:33:56 +0100 | ghormoon | (~ghormoon@ghorland.net) (Ping timeout: 268 seconds) |
| 2023-01-27 05:02:54 +0100 | ghormoon | (~ghormoon@ghorland.net) |
| 2023-01-27 07:27:55 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 252 seconds) |
| 2023-01-27 08:24:34 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-27 09:40:17 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-01-27 10:25:03 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 252 seconds) |
| 2023-01-27 10:30:37 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
| 2023-01-27 12:10:23 +0100 | qbt | (~qbt@user/edun) (Ping timeout: 248 seconds) |
| 2023-01-27 13:57:50 +0100 | qbt | (~qbt@user/edun) |
| 2023-01-27 14:00:35 +0100 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2023-01-27 15:26:42 +0100 | telser_ | (~quassel@user/telser) |
| 2023-01-27 15:27:12 +0100 | telser | (~quassel@user/telser) (Ping timeout: 248 seconds) |
| 2023-01-27 15:54:26 +0100 | ft | (~ft@p4fc2a257.dip0.t-ipconnect.de) |
| 2023-01-27 17:00:04 +0100 | uhoreg | (~uhoreg@2001:470:69fc:105::35f) (Quit: You have been kicked for being idle) |
| 2023-01-27 17:00:08 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-01-27 17:05:30 +0100 | fjMSX | (~hypni2p@89-179-32-81.broadband.corbina.ru) (Quit: Уш'лЪЬ їз єтой IRC сетї) |
| 2023-01-27 17:15:52 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 3.6) |
| 2023-01-27 17:32:10 +0100 | ml| | (~ml|@user/ml/x-5298235) |
| 2023-01-27 17:32:46 +0100 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2023-01-27 18:12:43 +0100 | ectospasm | (~ectospasm@user/ectospasm) (Ping timeout: 248 seconds) |
| 2023-01-27 18:16:10 +0100 | ectospasm | (~ectospasm@user/ectospasm) |
| 2023-01-27 18:46:04 +0100 | qbt | (~qbt@user/edun) (Ping timeout: 252 seconds) |
| 2023-01-27 20:35:28 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) |
| 2023-01-27 20:46:44 +0100 | <xmonadtrack> | New xmonad-contrib branch created: pull/796 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/796 |
| 2023-01-27 20:46:59 +0100 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-01-27 21:21:52 +0100 | telser_ | (~quassel@user/telser) (Ping timeout: 248 seconds) |
| 2023-01-27 21:22:22 +0100 | telser | (~quassel@user/telser) |
| 2023-01-27 21:54:28 +0100 | tremon | (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |