| 2023-03-19 00:41:53 +0100 | noex | (~null@user/noex) |
| 2023-03-19 00:41:58 +0100 | hightower3 | (~hightower@166-57.dsl.iskon.hr) |
| 2023-03-19 00:44:19 +0100 | hightower2 | (~hightower@141-136-194-244.dsl.iskon.hr) (Ping timeout: 246 seconds) |
| 2023-03-19 01:10:23 +0100 | noex | (~null@user/noex) (Quit: :q!) |
| 2023-03-19 01:55:09 +0100 | chomwitt | (~chomwitt@ppp-94-67-217-45.home.otenet.gr) (Ping timeout: 250 seconds) |
| 2023-03-19 02:16:03 +0100 | Guest18 | (~Guest18@node-1w7jr9yaj7srjfo5i42ldx870.ipv6.telus.net) |
| 2023-03-19 04:03:28 +0100 | banc | (~banc@154.47.24.197) (Ping timeout: 246 seconds) |
| 2023-03-19 04:05:50 +0100 | kora9 | (uid591798@user/Kora9) (Quit: Connection closed for inactivity) |
| 2023-03-19 04:17:28 +0100 | td_ | (~td@i5387093F.versanet.de) (Ping timeout: 246 seconds) |
| 2023-03-19 04:19:34 +0100 | td_ | (~td@i5387093A.versanet.de) |
| 2023-03-19 04:22:59 +0100 | banc | (~banc@154.47.24.197) |
| 2023-03-19 04:41:59 +0100 | hightower4 | (~hightower@13-222.dsl.iskon.hr) |
| 2023-03-19 04:45:16 +0100 | hightower3 | (~hightower@166-57.dsl.iskon.hr) (Ping timeout: 276 seconds) |
| 2023-03-19 05:17:22 +0100 | catman | (~catman@user/catman) |
| 2023-03-19 05:24:35 +0100 | catman | (~catman@user/catman) (Ping timeout: 246 seconds) |
| 2023-03-19 07:28:50 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Quit: leaving) |
| 2023-03-19 07:32:27 +0100 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
| 2023-03-19 08:46:44 +0100 | dge | (~jeromelan@221-22-190-109.dsl.ovh.fr) |
| 2023-03-19 08:53:55 +0100 | <dge> | Hi, can someone explain me or sent to me a link that show me how to test XMonad config (maybe with Xephyr or anything else) ? I would like to try XMonad and Haskell language to replace maybe my AWesome WM. I did install xmonad from his git repo and compil with a xmonad.hs config file very basic. When i start a session from SDDM, i have an "ok" button in the middle and everything seems to be like frozen (have to reboot next). So i want to test |
| 2023-03-19 08:53:55 +0100 | <dge> | it before to apply a config and be able to read some error log or something helpfull to fix my first problem. |
| 2023-03-19 08:56:47 +0100 | <dge> | (also, just tell me if you can read my message, because i testing also my irc connection) |
| 2023-03-19 09:09:19 +0100 | <[Leary]> | dge: Have you tried the default keybinds? Mod+? to show help with xmessage, Mod+Shift+Enter for an xterm, etc. |
| 2023-03-19 09:20:30 +0100 | <dge> | yes, i did try all of them. I also used the mod4 key instead of Alt key to access the default one. At run time, i tryed both Alt and mod4 ones with many combi (like terminal start, help message, and so on). No one worked, but looks like freeze at start. No error message from compil config file. |
| 2023-03-19 09:25:02 +0100 | <[Leary]> | And you're sure you have xmessage and xterm on your system? |
| 2023-03-19 09:33:11 +0100 | <dge> | i use alacritty and did config terminal to be alacritty at terminal call key binding. i don't have "xmessage" installed, and not find any in kind of ubuntu repos (pop_os the same). |
| 2023-03-19 09:33:39 +0100 | <dge> | but my question was on "how to test xmonad" (like... with Xephyr maybe) ? |
| 2023-03-19 09:33:56 +0100 | <dge> | and get error message back to be able to fix things myself maybe. |
| 2023-03-19 09:39:13 +0100 | <[Leary]> | Yes, and there are ways, but it's usually easier to test in action. It's a long time since I've used Xephyr for this and I don't recall the details. They might be in the xmonad-test repo if it still exists, but it's almost certainly out of date. In any case, it looks like x11-utils will give you xmessage, which should show you the errors. |
| 2023-03-19 09:52:14 +0100 | <dge> | "easier" ? To reboot at each freeze time and get no error message ? You are thinkingit is easier to practice tests this way ? Or is it esier for YOU only due to no help time for Xephyr ? I ay prefer to wait for someone that can help me to install and use a real test process than to reboot all the time with nothing to look at for error. |
| 2023-03-19 09:53:05 +0100 | <dge> | but, thank you for your ppurpose and your time, i do appreciate it. |
| 2023-03-19 09:54:30 +0100 | <[Leary]> | Normally you should be able to just exit to your login/display manager instead, so it shouldn't be such a hassle. |
| 2023-03-19 09:55:43 +0100 | <[Leary]> | I suspect an issue with whatever script is trying to start xmonad, but the other possibility is that your config does compile to a loop. If so, you may be able to kill it via tty. |
| 2023-03-19 09:56:14 +0100 | <[Leary]> | Though it would be best to just erase the config and try the defaults first. |
| 2023-03-19 10:00:00 +0100 | <[Leary]> | Your session logs may also have something to say, though I couldn't tell you where to look for them; it's different on every distro. |
| 2023-03-19 10:18:11 +0100 | <dge> | So, each time i will increase my config file, line by line i will reboot... that is, for you, not a hassle loosing tie instead of runing test from a xephyr session ? Ok. have a good day man, i have no time for that. |
| 2023-03-19 11:11:27 +0100 | <liskin> | dge: instead of rebooting, you should be able to use Ctrl-Alt-F1/F2/… to switch to another console and kill the nonresponsive session |
| 2023-03-19 11:11:46 +0100 | <liskin> | actually you can run multiple X sessions this way as well and switch between them |
| 2023-03-19 11:12:01 +0100 | <liskin> | it might be easier (admittedly not as convenient) than running Xephyr |
| 2023-03-19 11:12:44 +0100 | <liskin> | using Xephyr involves some xauth hassle that I don't remember (it's in bash history on my other laptop, but I won't have time to open that one until tomorrow) |
| 2023-03-19 11:14:39 +0100 | <liskin> | also, you might want to disable DontZap temporarily and use Ctrl-Alt-Backspace to kill the X: https://unix.stackexchange.com/questions/375/how-to-enable-killing-xorg-with-ctrlaltbackspace |
| 2023-03-19 11:15:14 +0100 | <liskin> | (it's a bad idea to leave that on as then pranksters can come and kill your session, but then if they have physical access you've lost anyway, so… meh) |
| 2023-03-19 11:42:06 +0100 | chomwitt | (~chomwitt@2a02:587:7a12:e700:1ac0:4dff:fedb:a3f1) |
| 2023-03-19 12:59:45 +0100 | thunderrd | (~thunderrd@183.182.111.130) |
| 2023-03-19 13:23:08 +0100 | <dge> | Why no tjust make it simple and use Xephyr ? Ask yourself why... |
| 2023-03-19 13:23:32 +0100 | <dge> | What is the most simple and clean ? |
| 2023-03-19 13:23:48 +0100 | <dge> | please... let's be factual. |
| 2023-03-19 13:49:40 +0100 | <geekosaur> | xephyr doesn't seem that hard for me? is this a fedora thing? or just that I use `startx -- :1` with a `.xserverrc` to launch it? |
| 2023-03-19 13:50:23 +0100 | <Solid[m]> | Yes, I just have something like |
| 2023-03-19 13:50:23 +0100 | <Solid[m]> | Xephyr -br -ac -noreset -screen 800x600 :1 & |
| 2023-03-19 13:50:23 +0100 | <Solid[m]> | DISPLAY=:1 xmonad |
| 2023-03-19 13:50:23 +0100 | <Solid[m]> | in a script |
| 2023-03-19 13:51:12 +0100 | <Solid[m]> | but dge do note that compilation errors will not trash your xmonad executable, you will still be running the old version |
| 2023-03-19 13:51:17 +0100 | <geekosaur> | but I have a full sandboxing setup so I can test user configs |
| 2023-03-19 13:51:43 +0100 | <Solid[m]> | so this kind of stuff might not be as useful as you think it will |
| 2023-03-19 13:51:50 +0100 | <geekosaur> | (that's how I debugged the join point bug and the windowNavigation thing among others) |
| 2023-03-19 15:31:24 +0100 | VarikValefor[m] | (~varikvale@2001:470:69fc:105::a5d) (Ping timeout: 265 seconds) |
| 2023-03-19 15:31:53 +0100 | geekosaur[m] | (~geekosaur@xmonad/geekosaur) (Ping timeout: 265 seconds) |
| 2023-03-19 15:33:04 +0100 | lisk1n | (~liskin@xmonad/liskin) |
| 2023-03-19 15:34:17 +0100 | liskin | (~liskin@xmonad/liskin) (Ping timeout: 265 seconds) |
| 2023-03-19 15:43:33 +0100 | VarikValefor[m] | (~varikvale@2001:470:69fc:105::a5d) |
| 2023-03-19 15:48:01 +0100 | geekosaur[m] | (~geekosaur@xmonad/geekosaur) |
| 2023-03-19 16:09:07 +0100 | qbt | (~qbt@user/edun) |
| 2023-03-19 16:50:00 +0100 | chomwitt | (~chomwitt@2a02:587:7a12:e700:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds) |
| 2023-03-19 17:03:06 +0100 | qbt | (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2023-03-19 17:41:13 +0100 | <geekosaur> | dge, re xmessage on debian |
| 2023-03-19 17:41:16 +0100 | <geekosaur> | skkukuk «xmonad:skkukuk» ⁅xmonad-bsa⁆ Z$ dpkg -S /usr/bin/xmessage |
| 2023-03-19 17:41:16 +0100 | <geekosaur> | x11-utils: /usr/bin/xmessage |
| 2023-03-19 17:41:39 +0100 | <geekosaur> | should be able to get that from apt-cache as well |
| 2023-03-19 17:42:10 +0100 | <geekosaur> | debian/ubuntu/probably popos |
| 2023-03-19 17:50:16 +0100 | <geekosaur> | also there are certainly ways for an xmonad config to break things completely; the simplest is to set the `handleEventHook` to `return (All False)` or equivalent |
| 2023-03-19 18:32:36 +0100 | jabuxas | (~jabuxas@user/jabuxas) (Ping timeout: 255 seconds) |
| 2023-03-19 18:34:20 +0100 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-03-19 19:15:23 +0100 | <dge> | i was afk... Xephyr is new to me, but i was thinking (and it seems i'm wrong) that XMonad lovers used it for test XMonad config, as AwesomeWM users use awmtt, who is a kind of Xephyr helper to test rc.lua config file for Awesome). |
| 2023-03-19 19:15:55 +0100 | <dge> | I'm under Pop!_OS who is an Ubuntu-22.04 distro. |
| 2023-03-19 19:16:32 +0100 | <dge> | I was using GDM3 but just installed and use now SDDM (lighter and good enaugh to me). |
| 2023-03-19 19:16:58 +0100 | <dge> | @Solid[m], thank you, i'm going to try this. |
| 2023-03-19 19:16:59 +0100 | <lambdabot> | Unknown command, try @list |
| 2023-03-19 19:18:06 +0100 | <geekosaur> | I think xmonad users just mod-q and hope for the best 🙂 |
| 2023-03-19 19:18:27 +0100 | <geekosaur> | I mean, usually if it compiles it works |
| 2023-03-19 19:18:34 +0100 | <dge> | Solid[m], yes, thank you. Sure, i dio use ~/.cache/xmonad/xmonad-x86_64-linux compiled version |
| 2023-03-19 19:18:55 +0100 | <geekosaur> | not guaranteed but the compiler really does catch most mistakes |
| 2023-03-19 19:19:49 +0100 | <dge> | geekosaur, i was thinking the same but... i'm very newby with that and also Haskell. So... i'm trying to win a bit of time by increase my capacity of testing faster because i know i will make a lot of error but still will customize and learn from them. |
| 2023-03-19 19:20:35 +0100 | <dge> | I also failed to find any Google best Haskell lovers users practice to config and test XMonad. |
| 2023-03-19 19:22:12 +0100 | <dge> | geekosaur, about xmessage, yes, it is inside my x11-utils package. So i have it installed. |
| 2023-03-19 19:31:22 +0100 | <dge> | sandboxing setup is something that should be a very good idea. I arrived to start xmonad on Xephyr (thanks geekosaur) but yeah... no error and Awesome still get my key bindings and not Xephyr, so untestable this way ! Maybe also a VM to run can be nice... |
| 2023-03-19 20:38:46 +0100 | abhixec | (~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2023-03-19 20:47:29 +0100 | <dge> | even through a VM, and following the official install method with default config, and default session, it failed with no error printed and it run the Gnome session. even from startx or from default xsession or what ever... |
| 2023-03-19 20:48:35 +0100 | <geekosaur> | if it's running the gnome session then it's not even attempting xmonad |
| 2023-03-19 20:48:49 +0100 | <geekosaur> | there's no fallback mechanism in X11 startup |
| 2023-03-19 20:58:27 +0100 | <dge> | not from startx, but from sddm |
| 2023-03-19 20:59:08 +0100 | <dge> | it looks like i missed something on xmonad.hs config file maybe |
| 2023-03-19 20:59:23 +0100 | <geekosaur> | @where paste |
| 2023-03-19 20:59:23 +0100 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2023-03-19 21:03:51 +0100 | <dge> | ok, i get a compilation error after to try from stack recompile.... due to version between ghc and stack (8.10 for ghc and 9.2.7 from stack) that is bad. I have to upgrade stack, but missing space on VM disk (crying)... |
| 2023-03-19 21:33:23 +0100 | dge | (~jeromelan@221-22-190-109.dsl.ovh.fr) (Ping timeout: 246 seconds) |
| 2023-03-19 22:35:51 +0100 | Guest1886 | (~Guest18@node-1w7jr9yaj7srjfo5i42ldx870.ipv6.telus.net) |
| 2023-03-19 22:43:10 +0100 | <Guest1886> | Having trouble with an app stealing keyboard focus. Reproduced this with a minimal xmonad config (i.e. just `import XMonad; main = xmonad def`). Repro: with the minimal config launch Godot4 (stable), and switch to a terminal with `modmask+j` then resize window with `modmap+h` and observe that keystrokes go to the Godot4 window even though the |
| 2023-03-19 22:43:11 +0100 | <Guest1886> | terminal's borders are highlighted. I'm running latest ArchLinux: |
| 2023-03-19 22:43:58 +0100 | <Guest1886> | libx11 1.8.4-1 |
| 2023-03-19 22:43:59 +0100 | <Guest1886> | xmonad 0.17.1-87 |
| 2023-03-19 22:43:59 +0100 | <Guest1886> | xmonad-contrib 0.17.1-86 |
| 2023-03-19 22:44:00 +0100 | lisk1n | liskin |
| 2023-03-19 22:44:23 +0100 | <geekosaur> | you're saying the xmonad keys are going to the app? |
| 2023-03-19 22:44:34 +0100 | <Guest1886> | all keys are going to the app |
| 2023-03-19 22:44:43 +0100 | <geekosaur> | that requires it to have done a key grab, which we can't prevent |
| 2023-03-19 22:44:50 +0100 | <Guest1886> | xmonad keys still work |
| 2023-03-19 22:44:54 +0100 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2023-03-19 22:45:00 +0100 | <geekosaur> | oh |
| 2023-03-19 22:45:31 +0100 | <Guest1886> | It doesn't happen in e.g. Ubuntu 22.04 (with alt-tab) |
| 2023-03-19 22:46:28 +0100 | <Guest1886> | i.e. with Ubuntu's stock window mgr and desktop |
| 2023-03-19 22:47:02 +0100 | <geekosaur> | have you tried it with xmonad on ubuntu? or with a different window manager on arch? |
| 2023-03-19 22:47:36 +0100 | <geekosaur> | we've had problems with arch's packaging of Haskell stuff (and in particular xmonad) but this would be somewhat weird |
| 2023-03-19 22:48:45 +0100 | <Guest1886> | I tried xfce and lxde on arch and saw the issue randomly on lxde (alt-tabbing) but not on xfce. I'm trying xmonad in Ubuntu next |
| 2023-03-19 22:50:54 +0100 | <Guest1886> | This is a related issue for Godot https://github.com/godotengine/godot/issues/74587 but it isn't really getting any attention leading me to think that not many people are seeing it. So I'm not sure what software has the issue. |
| 2023-03-19 22:53:02 +0100 | <Guest1886> | As above, I reproduced with min config but I noticed that the problem is much more aggressive with my full config, notably with bluetile (i.e. grabs keyboard more often and much harder/nearly impossible to get keyboard focus back even when clicking mouse on intended window) |
| 2023-03-19 22:53:11 +0100 | <geekosaur> | sounds like that's actually two issues, an earlier Windows-specific one and a more recent one that repros in lxde and i3 |
| 2023-03-19 22:53:18 +0100 | <geekosaur> | and, apparently, xmonad |
| 2023-03-19 22:53:55 +0100 | <geekosaur> | the i3 reproduction is 3 days old |
| 2023-03-19 22:54:18 +0100 | <geekosaur> | which means just before the weekend so probably nobody sees it until tomorrow 🙂 |
| 2023-03-19 22:55:17 +0100 | <Guest1886> | yes, I was thinking more of a general issue originally with the windows problem but since it didn't show up in Ubuntu (stock WM) or Arch XFCE it seems like the windows issue might be unrelated and that the i3 and xmonad issues *might* be caused by similar implementations (??) |
| 2023-03-19 22:55:56 +0100 | <geekosaur> | well, we're both tiling, but that doesn |
| 2023-03-19 22:55:59 +0100 | <geekosaur> | 't explain LXDE |
| 2023-03-19 22:56:30 +0100 | <geekosaur> | I'd be curious as to whether it also happens with LXQt (same environment different implementation) |
| 2023-03-19 22:57:12 +0100 | <Guest1886> | I'll test LXQt in Arch too |
| 2023-03-19 22:57:15 +0100 | <geekosaur> | in any case it sounds like it's stealing focus |
| 2023-03-19 22:59:09 +0100 | <Guest1886> | So I don't know much about X11 implementation but it sounds like client windows can choose to steal focus, overriding any focus controls implemented in window managers? |
| 2023-03-19 22:59:23 +0100 | <geekosaur> | (LXDE is Gtk based, LXQt is part of a long term move from Gtk to Qt) |
| 2023-03-19 22:59:30 +0100 | <geekosaur> | yes |
| 2023-03-19 22:59:42 +0100 | <geekosaur> | it's strongly frowned upon |
| 2023-03-19 22:59:51 +0100 | <Guest1886> | gotcha |
| 2023-03-19 23:00:43 +0100 | <geekosaur> | but the same API is used for a program to set focus to an internal widget so they can't simply remove it |
| 2023-03-19 23:07:45 +0100 | <Guest1886> | btw I found running `watch -n0.1 xdotool getwindowfocus getwindowname` useful for debugging this |
| 2023-03-19 23:08:50 +0100 | <Guest1886> | just prints the currently focused window and the bug can be seen when it prints the Godot window name while xmonad is highlighting a different window |
| 2023-03-19 23:09:36 +0100 | Guest1886 | (~Guest18@node-1w7jr9yaj7srjfo5i42ldx870.ipv6.telus.net) (Quit: Client closed) |
| 2023-03-19 23:09:36 +0100 | Guest18 | (~Guest18@node-1w7jr9yaj7srjfo5i42ldx870.ipv6.telus.net) (Quit: Client closed) |
| 2023-03-19 23:27:25 +0100 | Guest1886 | (~Guest1886@node-1w7jr9yaj7srjfo5i42ldx870.ipv6.telus.net) |
| 2023-03-19 23:28:11 +0100 | <Guest1886> | LXQt on Arch behaved the same as LXDE did |
| 2023-03-19 23:30:20 +0100 | <Guest1886> | However there is a difference between what LXDE/Qt are doing and what XMonad is doing. LXDE/Qt keep correct window highlighting but XMonad doesn't |
| 2023-03-19 23:32:15 +0100 | <Guest1886> | i.e. in the video ( https://github.com/godotengine/godot/issues/74587#issuecomment-1466538062 ) at 15 seconds you can see alt-tab to terminal fails but the Godot window keeps the highlighting. But when in XMonad the terminal I wan't to type in gets highlighted but the keystrokes keep going to Godot |
| 2023-03-19 23:33:20 +0100 | <geekosaur> | hm. normally xmonad should get the focus change event and update the borders |
| 2023-03-19 23:35:23 +0100 | <Guest1886> | Yes that's what's making think that at least part of the prob is in XMonad |
| 2023-03-19 23:45:39 +0100 | <geekosaur> | https://paste.tomsmeding.com/Cx907lfH |
| 2023-03-19 23:46:21 +0100 | <geekosaur> | then check the session log when this is happening. it should show either or both of FocusChangeEvent or CrossingEvent happening |
| 2023-03-19 23:46:38 +0100 | <geekosaur> | (probably FocusChangeEvent since the mouse isn't causing it_ |
| 2023-03-19 23:46:41 +0100 | <geekosaur> | ) |
| 2023-03-19 23:48:02 +0100 | <Guest1886> | Will do |
| 2023-03-19 23:48:43 +0100 | <Guest1886> | Also just confirmed bug occurs in Ubuntu 22.04.2 |
| 2023-03-19 23:49:07 +0100 | <Guest1886> | xmonad 0.15 |
| 2023-03-19 23:49:11 +0100 | <Guest1886> | totally default |
| 2023-03-19 23:51:25 +0100 | <geekosaur> | the other alternative is you'll see a whole bunch of them, which would mean xmonad is indeed trying to track it but it's fighting with godot4 and you can't see the focus changes because they're happening too quickly |
| 2023-03-19 23:52:04 +0100 | <geekosaur> | although in that case this might slow things down just enough to make them visible |
| 2023-03-19 23:57:03 +0100 | <geekosaur> | one other thing to try is to enable EwmhDesktops and see if it still happens. for backward compatibility reasons we don't support EWMH by default, only ICCCM |
| 2023-03-19 23:57:17 +0100 | <Guest1886> | xmonad.hs:6:30: error: |
| 2023-03-19 23:57:18 +0100 | <Guest1886> | • Data constructor not in scope: |
| 2023-03-19 23:57:18 +0100 | <Guest1886> | All :: Bool -> base-4.15.1.0:Data.Semigroup.Internal.All |
| 2023-03-19 23:57:19 +0100 | <Guest1886> | • Perhaps you meant variable ‘all’ (imported from Prelude) |
| 2023-03-19 23:57:19 +0100 | <Guest1886> | | |
| 2023-03-19 23:57:20 +0100 | <Guest1886> | 6 | debugFocusEvents _ = return (All True) |
| 2023-03-19 23:57:20 +0100 | <Guest1886> | | ^^^ |
| 2023-03-19 23:57:21 +0100 | <Guest1886> | Please check the file for errors. |
| 2023-03-19 23:57:31 +0100 | <Guest1886> | Tried `import Data.Semigroup.Internal` also |
| 2023-03-19 23:57:38 +0100 | <geekosaur> | but this breaks a number of modern programs (for example, LibreOffice will get into a focus loop without EWMH) |
| 2023-03-19 23:57:48 +0100 | <geekosaur> | oh, sorry, need to import Data.Monoid, forgot that |
| 2023-03-19 23:58:00 +0100 | <Guest1886> | yeah I normally use EWMH and still saw the bug |
| 2023-03-19 23:58:15 +0100 | <geekosaur> | https://paste.tomsmeding.com/cmdAN7aB |