Logs: liberachat/#xmonad
| 2022-05-01 03:00:19 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-05-01 03:02:00 | → | c209e6dc-4d76-47 joins (~aditya@2601:249:4300:1296:195:dac6:592c:a55a) |
| 2022-05-01 03:02:15 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-05-01 03:19:35 | × | c209e6dc-4d76-47 quits (~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Quit: Konversation terminated!) |
| 2022-05-01 03:27:02 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::aa1d) |
| 2022-05-01 03:37:36 | × | steve__ quits (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 276 seconds) |
| 2022-05-01 04:17:42 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds) |
| 2022-05-01 04:33:31 | → | steve__ joins (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-05-01 05:07:22 | → | Ether17 joins (~Ether17@45.248.151.250) |
| 2022-05-01 05:18:03 | × | Ether17 quits (~Ether17@45.248.151.250) (Quit: Client closed) |
| 2022-05-01 05:54:09 | → | Ether17 joins (~Ether17@45.248.151.250) |
| 2022-05-01 05:54:32 | × | Ether17 quits (~Ether17@45.248.151.250) (Client Quit) |
| 2022-05-01 07:20:34 | → | gauge joins (~gauge@user/gauge) |
| 2022-05-01 07:52:24 | × | mvk quits (~mvk@2607:fea8:5ce3:8500::aa1d) (Ping timeout: 248 seconds) |
| 2022-05-01 09:00:11 | × | jmac123[m] quits (~jmac123ma@2001:470:69fc:105::1:eaf0) (Quit: You have been kicked for being idle) |
| 2022-05-01 09:00:12 | × | robinhood0018[m] quits (~robinhood@2001:470:69fc:105::1:4dca) (Quit: You have been kicked for being idle) |
| 2022-05-01 09:00:15 | × | ctx[m] quits (~ctxkungfu@2001:470:69fc:105::1:95dd) (Quit: You have been kicked for being idle) |
| 2022-05-01 09:44:32 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 272 seconds) |
| 2022-05-01 09:48:32 | × | Xioulious quits (~yourname@193.32.249.137) (Quit: leaving) |
| 2022-05-01 09:54:07 | → | abastro joins (~abab9579@192.249.26.173) |
| 2022-05-01 11:18:10 | × | abastro quits (~abab9579@192.249.26.173) (Remote host closed the connection) |
| 2022-05-01 11:35:01 | × | td_ quits (~td@94.134.91.80) (Ping timeout: 256 seconds) |
| 2022-05-01 11:36:31 | → | td_ joins (~td@94.134.91.69) |
| 2022-05-01 11:46:48 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-05-01 13:12:24 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 248 seconds) |
| 2022-05-01 13:33:16 | → | Xioulious joins (~yourname@193.32.249.137) |
| 2022-05-01 13:36:14 | <Xioulious> | i've got a piece of code that makes it so with multiplescreens, when i move my mouse to a different screen that has an empty workspace, that screen/workspace gets focussed, this works as it should.. but then when i try to do the float and move with my mouse (the default modkey+buton1) and move the window to an other screen it often freaks out (starts jumping around) and sometimes goes invisible.. not |
| 2022-05-01 13:36:20 | <Xioulious> | sure whats wrong with my code, could anyone take a look at it? |
| 2022-05-01 13:36:36 | <Xioulious> | move a window* |
| 2022-05-01 13:38:15 | <geekosaur> | you should probably pastebin the code so someone can look at it, rather than asking to ask |
| 2022-05-01 13:38:19 | <geekosaur> | @where paste |
| 2022-05-01 13:38:19 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2022-05-01 13:38:48 | <geekosaur> | I don't know how long I'll be around today, I'm waiting on my sister as usual for a Sunday |
| 2022-05-01 13:41:50 | <Xioulious> | should i put my full xmonad.hs there or just the piece of code thats bugging out? guessing the xmonad.hs might be easier? |
| 2022-05-01 13:41:54 | <geekosaur> | aaaand there she is |
| 2022-05-01 13:42:04 | <geekosaur> | yes, seeing how it integrates in is often helpful |
| 2022-05-01 13:42:17 | <Xioulious> | haha, enjoy your day with your sis! |
| 2022-05-01 13:42:20 | <Xioulious> | ok, will do |
| 2022-05-01 13:42:27 | <geekosaur> | \might want to use gist in that case. (many of us host our xmonad.hs-s on github or gitlab to make this easier) |
| 2022-05-01 13:42:45 | <geekosaur> | well, I hae around an hour; she just texted me |
| 2022-05-01 13:43:18 | <geekosaur> | *have |
| 2022-05-01 13:43:27 | <Xioulious> | yeah i already got my xmonad.hs on my gitlab, though i do get some errors in my xsession-error file which could be helpfull |
| 2022-05-01 13:46:42 | <Xioulious> | https://paste.tomsmeding.com/T6dIGYxa thats the stack.yaml and the error log, https://gitlab.com/Shadu/dotfiles/-/blob/main/.config/xmonad/xmonad.hs is the xmonad.hs |
| 2022-05-01 13:48:26 | <Xioulious> | if i comment out the multiScreenFocusHook then it doesnt happen, but ofc then it wont focus on an empty workspace automatically |
| 2022-05-01 13:49:16 | <geekosaur> | it never rains but it pours :) I wonder if this is the one we hit yesterday (BadValue on request 91/XLookupColor) |
| 2022-05-01 13:50:23 | <Xioulious> | yeah, during normal use that error also pops up sometimes, but when i do that specific thing then it just floods it |
| 2022-05-01 13:51:05 | <geekosaur> | and there's WindowNavigation, which might be the cause |
| 2022-05-01 13:53:32 | <Xioulious> | hmm then i wonder about something, the person i got that script from didnt really encounter the problem, but i didnt take their layout setup.. let me check if they use windownavigation |
| 2022-05-01 13:54:39 | <Xioulious> | nope, they aren't using it |
| 2022-05-01 13:58:11 | <geekosaur> | that is likely to be the cause of the errors in the log, from our debugging over the past several hours of someone else's config |
| 2022-05-01 13:58:51 | <geekosaur> | but I suspect your dragging problem is because you have both draggingVisualizer and multiScreenFocusHook and they're fighting each other |
| 2022-05-01 13:58:59 | <Xioulious> | the freaking out still occurs even if i comment out the windownavigation import and the part in the layout |
| 2022-05-01 14:00:30 | <Xioulious> | for some reason it seems to want to stretch the window downwards, atleast the size of the window changes when it does that |
| 2022-05-01 14:02:27 | <Xioulious> | also seems to only do it when i drag a window to an empty workspace |
| 2022-05-01 14:04:20 | <Xioulious> | got some better errors this time, but thats with a firefox crash: https://paste.tomsmeding.com/WOW4bhC2 |
| 2022-05-01 14:11:24 | <geekosaur> | the getWindowAttributes errors are sadly normal. BadAlloc looks bad, though |
| 2022-05-01 14:11:47 | <geekosaur> | what happens if you disable DraggingVisualizer? |
| 2022-05-01 14:12:51 | <Xioulious> | still the same behavior |
| 2022-05-01 14:13:15 | <geekosaur> | okay, so it's not a conflict there |
| 2022-05-01 14:20:18 | <Xioulious> | if i do the same but with a thunar window, it also freaks out, but i dont get the badalloc error, so am thinking the badalloc is an error on firefox side? |
| 2022-05-01 14:20:47 | <geekosaur> | except it's xmonad reporting it (note the start of the line) |
| 2022-05-01 14:21:02 | <Xioulious> | it also doesnt add any errors to the xsession-error file in the case of thunar |
| 2022-05-01 14:21:34 | <geekosaur> | ConfigureWindow |
| 2022-05-01 14:21:41 | <Xioulious> | true, just thought that if there are some x11 errors that arent caused by xmonad but by a program running that xmonad would be reporting it or something |
| 2022-05-01 14:22:07 | <geekosaur> | no, xmonad wouldn't receive those errors |
| 2022-05-01 14:22:27 | <geekosaur> | ConfigureWindow error would match with your remark about the window resizing |
| 2022-05-01 14:26:23 | <Xioulious> | could that have something to do with having 2 different resolutions? (monitor 1 being 1920x1200, monitor 2 being 1920x1080) |
| 2022-05-01 14:26:57 | × | thunderrd quits (~thunderrd@183.182.110.239) (Remote host closed the connection) |
| 2022-05-01 14:27:55 | <geekosaur> | yes. xmonad stores relative sizes (see RationalRect) and will resize (in your case, downward) when you move a window to a different monitor |
| 2022-05-01 14:28:02 | → | thunderrd joins (~thunderrd@183.182.110.239) |
| 2022-05-01 14:28:37 | <geekosaur> | I think your hook needs to verify that it is not inside a window at the time |
| 2022-05-01 14:29:57 | <geekosaur> | it's not enough to check that there are no windows "on the screen" because the window you're moving won't be registered as on that screen until its origin is there |
| 2022-05-01 14:30:15 | <geekosaur> | that is, its (0,0) |
| 2022-05-01 14:30:22 | <geekosaur> | upper left corner |
| 2022-05-01 14:30:34 | <geekosaur> | and may not be actually moved until the drag stops |
| 2022-05-01 14:32:03 | <Xioulious> | so the hook for the focus thing should only activate when the cursor itself isnt over a window instead of checking if the screen has any windows |
| 2022-05-01 14:32:49 | <geekosaur> | right, because "screen has any windows" will be incorrect mid-drag |
| 2022-05-01 14:34:35 | <geekosaur> | queryPointer should inform you both of the pointer location and what window it's currently in |
| 2022-05-01 14:35:04 | <Xioulious> | and then the hook will try to focus the workspace but then when i drag some more i throw the focus back to the window and it will constantly jump between those 2 and things freak out, sounds logical yeah, now to figure out how to implement it |
| 2022-05-01 14:37:58 | → | cfricke joins (~cfricke@user/cfricke) |
| 2022-05-01 14:38:28 | <geekosaur> | https://hackage.haskell.org/package/X11-1.10.2/docs/Graphics-X11-Xlib-Misc.html#v:queryPointer https://tronche.com/gui/x/xlib/window-information/XQueryPointer.html |
| 2022-05-01 14:38:53 | <geekosaur> | the Haskell wrapper is pretty raw, it maps directly to the Xlib call |
| 2022-05-01 14:39:16 | <geekosaur> | so you can just check if the returned window ID (not root window ID) is 0 |
| 2022-05-01 14:40:26 | <abastro[m]> | Interesting how such direct translation is possible |
| 2022-05-01 14:40:29 | <Xioulious> | okay, let me make a note of that, time to learn some haskell |
| 2022-05-01 14:43:56 | <Xioulious> | also another bug that im having, though its with xmobar, is when I have my TV that is connected to my pc turned on but disabled through xrandr (or well, nvidia settings) and my 2 monitors go into standby, when i wake the monitors back up the xmobars are stretched across both screens |
| 2022-05-01 14:44:52 | <geekosaur> | that would imply that xrandr information is wrong. I think we've seen that a few times with nvidia |
| 2022-05-01 14:45:33 | <geekosaur> | sometimes affects xmonad as well, the xrandr information is inconsistent and different programs use different parts of it |
| 2022-05-01 14:46:12 | <abastro[m]> | X & multiscreen? |
| 2022-05-01 14:46:56 | <Xioulious> | so when that occurs i should check what xrandr is saying? i usually just do a recompile and restart of xmonad and that fixes it, but rather have it not occur ofc |
| 2022-05-01 14:46:58 | <geekosaur> | multiscreen is a horrid hack, it's amazing that it works we well as it does |
| 2022-05-01 14:47:53 | <abastro[m]> | I am glad I only have this laptop with single screen |
| 2022-05-01 14:47:56 | <geekosaur> | X supports multiscreen natively but assumes every screen has its own framebuffer so windows can't be moved between them or etc., because that's how things worked in the 1980s |
| 2022-05-01 14:48:37 | <Xioulious> | mhm, seems with nvidia it just makes 1 big screen and divides it up in 2 spaces |
| 2022-05-01 14:49:38 | <abastro[m]> | Linux distros do not usually depend on X, right |
| 2022-05-01 14:49:43 | <geekosaur> | that's how the multiscreen hack works,m yes. not just nvidia |
| 2022-05-01 14:50:18 | <geekosaur> | it means different monitor resolutions don't work right, and various other shortcomings |
| 2022-05-01 14:50:35 | <abastro[m]> | Nvidia? |
| 2022-05-01 14:50:58 | <geekosaur> | alll the big linux distros still depend on X. we're expecting it to still be supported through 2030 because of contractual obligations on Red Hat's commercial offerings |
| 2022-05-01 14:51:06 | <Xioulious> | that also causes the issues of different refreshrates, sadly wayland isnt ready yet for daily use for me, but xmonad feels way more comfy than i3 so far |
All times are in UTC.