Logs: liberachat/#xmonad
| 2022-07-25 17:45:54 | <elonsroadster[m]> | for me it actually gets minimized atm |
| 2022-07-25 17:45:57 | <elonsroadster[m]> | which is very strange |
| 2022-07-25 17:47:35 | <geekosaur> | it does a grab to isolate itself from other programs that might try to snoop your key |
| 2022-07-25 17:49:11 | <geekosaur> | while the intended effect is to prevent other programs from snooping key events, it also means all key events get sent to it, so you shouldn't be able to focus another window and run xprop |
| 2022-07-25 17:51:02 | <elonsroadster[m]> | hmmm thats not what happens for me |
| 2022-07-25 17:53:12 | <geekosaur> | it does have an option to drop its grab on focusing another window, intended for debugging; maybe yours is configured that way. (bad thing though, it's unsafe) |
| 2022-07-25 17:53:36 | <elonsroadster[m]> | im using pinentry gtk |
| 2022-07-25 17:53:56 | <elonsroadster[m]> | with a totally stock config |
| 2022-07-25 17:54:18 | <geekosaur> | --no-global-grab, -g |
| 2022-07-25 17:54:18 | <geekosaur> | Grab the keyboard only when the window is focused. Use this option if you are debugging software using pinentry-gnome3; otherwise you may not be able to to access your X session anymore (unless you have other means to connect to the machine to kill pinentry-gnome3). |
| 2022-07-25 17:54:38 | <geekosaur> | should be the same for other X11-based pinentry variants |
| 2022-07-25 17:56:38 | <elonsroadster[m]> | yeah i dont think im using that though |
| 2022-07-25 17:57:33 | <geekosaur> | I think pinentry-gtk has a similar option, because it's nearly useless without it. (it is about *security*, not merely about popping a dialog for a program in the background) |
| 2022-07-25 18:15:23 | <liskin> | pinentry works here out of the box |
| 2022-07-25 18:15:41 | <liskin> | I presume it just uses the core functinality of fixed size ⇒ float |
| 2022-07-25 18:16:02 | <liskin> | which can probably be broken by a suitably weird manageHook |
| 2022-07-25 18:17:59 | <liskin> | (I can check with Xephyr and the non-contrib "xmonad def" but I'm fairly busy with life in general so I'd rather postpone it until someone suggests it's actually broken) |
| 2022-07-25 18:34:29 | × | catman quits (~catman@user/catman) (Ping timeout: 244 seconds) |
| 2022-07-25 18:55:17 | → | catman joins (~catman@user/catman) |
| 2022-07-25 19:09:50 | → | Forkk joins (~forkk@li926-228.members.linode.com) |
| 2022-07-25 19:18:01 | → | tjmciver joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-25 19:19:17 | <tjmciver> | Hello. My caps lock key stopped working recently. It may have been when going from xmonad 0.15 to 0.17. Is that expected? Am I supposed to set up an explicit key binding for it? |
| 2022-07-25 19:29:17 | <geekosaur> | xmonad shouldn't have any effect on caps lock |
| 2022-07-25 19:44:59 | × | catern quits (~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407) (Quit: Using Circe, the loveliest of all IRC clients) |
| 2022-07-25 20:02:16 | <tjmciver> | geekosaur, thanks, I'll look elsewhere then. |
| 2022-07-25 20:03:27 | <geekosaur> | only thing I can think of is some keyboard configuration is no longer being loaded, possibly see if your distro desupported xmodmap and you have to use Xkb now or something |
| 2022-07-25 20:06:20 | <tjmciver> | I'm running NixOS so I stronly suspect the issue to be there. |
| 2022-07-25 20:11:12 | → | wusticality joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 20:11:45 | <wusticality> | hey folks, I'm trying to use xset to bump my keyboard repeat speed on startup, but it never seems to work when running it from my ~/.xinitrc |
| 2022-07-25 20:11:49 | <wusticality> | Even tried something like this: |
| 2022-07-25 20:12:08 | <wusticality> | (sleep 6 && xset r rate 264 48) & |
| 2022-07-25 20:12:20 | <wusticality> | just curious if there's a better, more reliable way (and also one that works haha) |
| 2022-07-25 20:12:26 | <wusticality> | I'm assuming it's some kind of timing issue |
| 2022-07-25 20:13:10 | <geekosaur> | if you run it in a terminal, do you get an error message? |
| 2022-07-25 20:15:24 | <wusticality> | nope, works just fine if I run it from a terminal |
| 2022-07-25 20:15:40 | <wusticality> | Tried both from xmonad.hs (via spawnOnce) and in .xinitrc, and neither work |
| 2022-07-25 20:15:50 | <wusticality> | perhaps xmonad is launching before x has finished booting up? |
| 2022-07-25 20:15:54 | <wusticality> | that's all i can think |
| 2022-07-25 20:16:00 | <wusticality> | https://bbs.archlinux.org/viewtopic.php?id=104338 |
| 2022-07-25 20:16:11 | <wusticality> | that thread seems to say as much, but none of their solutions work for me thus far |
| 2022-07-25 20:18:44 | <geekosaur> | xmonad would crash in that case |
| 2022-07-25 20:19:00 | <geekosaur> | the first thing it does is openDisplay |
| 2022-07-25 20:22:21 | <wusticality> | are you saying xmonad.hs doesn't fire up until x is fully initialized? |
| 2022-07-25 20:23:19 | → | wusticality1 joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 20:23:26 | × | wusticality quits (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Leaving) |
| 2022-07-25 20:23:46 | <geekosaur> | xmonad.hs would crash if X were not fully initialized |
| 2022-07-25 20:24:02 | <geekosaur> | with an error in openDisplay |
| 2022-07-25 20:24:10 | <wusticality1> | strange, I wonder why it's not working |
| 2022-07-25 20:24:18 | <wusticality1> | maybe spawn instead of spawnOnce? |
| 2022-07-25 20:24:20 | <geekosaur> | possibly something is overriding it |
| 2022-07-25 20:24:52 | <geekosaur> | wait, you're doing this in your xmonad.hs? although I guess that shouldn't matter |
| 2022-07-25 20:25:44 | <wusticality1> | well, i was trying it in ~/.xinitrc first |
| 2022-07-25 20:25:46 | <wusticality1> | but that didn't work |
| 2022-07-25 20:25:56 | <wusticality1> | that file is definitely being hit though cause I have xnumlock & in there |
| 2022-07-25 20:25:58 | <wusticality1> | and that works fine |
| 2022-07-25 20:27:15 | <geekosaur> | so that would suggest something is overriding it. |
| 2022-07-25 20:28:25 | → | kevin_ joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 20:28:46 | × | kevin_ quits (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Client Quit) |
| 2022-07-25 20:29:50 | × | chomwitt quits (~chomwitt@2a02:587:dc00:5a00:175e:8c5b:e001:c3ec) (Ping timeout: 240 seconds) |
| 2022-07-25 20:31:13 | <wusticality1> | boy, I have no idea what - certainly nothing I've setup |
| 2022-07-25 20:32:32 | → | wusticality joins (~user@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 20:42:35 | × | wusticality1 quits (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed) |
| 2022-07-25 20:42:35 | × | wusticality quits (~user@c-67-161-204-49.hsd1.co.comcast.net) (Remote host closed the connection) |
| 2022-07-25 20:52:41 | → | wusticality1 joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 20:52:54 | <wusticality1> | out of mere curiosity, all these commands are x-specific - what happens if you use wayland? |
| 2022-07-25 20:53:06 | <wusticality1> | hoping there are analogs for that |
| 2022-07-25 21:08:14 | × | wusticality1 quits (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed) |
| 2022-07-25 21:21:17 | × | benemorius quits (~benemoriu@2001:470:4bb0:919::1:56) (Remote host closed the connection) |
| 2022-07-25 21:21:40 | → | benemorius joins (~benemoriu@2001:470:4bb0:919::1:56) |
| 2022-07-25 21:21:55 | <tjmciver> | Hi. I'm looking for some pointers on correctly using `avoidStruts`. Currently, it works correctly for my laptop screen where I have xmobar, but I also get a "strut" on one of my two external monitors. I have been manually toggling it off but I want to prevent that in the config. Also, I have no strut on my second external monitor and cannot toggle it so I'm confused about how xmonad is deciding what to do here. |
| 2022-07-25 21:21:59 | <geekosaur> | I have no idea. I don't trust Wayland enough to consider it |
| 2022-07-25 21:22:52 | <geekosaur> | struts come from windows. avoidStruts attempts to apply them, but misusing it can lead to surprises |
| 2022-07-25 21:23:29 | <tjmciver> | Do I need to use `avoidStrutsOn` instead? |
| 2022-07-25 21:27:20 | <geekosaur> | can I see your layoutHook? |
| 2022-07-25 21:27:46 | <geekosaur> | (I use avoidStrutsOn but that's to have them default off on one workspace while allowing me to toggle them on at times) |
| 2022-07-25 21:31:33 | <tjmciver> | My config is pretty sparse: https://gitlab.com/tmciver/home-manager-config/-/blob/master/programs/xmonad/config.hs#L32 |
| 2022-07-25 21:35:50 | <geekosaur> | avoidStruts on the outside should be good. I wonder if xsmobar knows about multiple monitors (if it doesn't then it's liable to allocate a strut across the whole root window) |
| 2022-07-25 21:36:38 | <geekosaur> | you might use `xprop _NET_WM_STRUT_PARTIAL` in a terminal, then click on xmobar and paste the result here (it'll be a bunch of numbers) |
| 2022-07-25 21:37:16 | → | wusticality1 joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 21:37:55 | <wusticality1> | tried this, but it also didn't work :( |
| 2022-07-25 21:37:56 | <wusticality1> | https://wiki.archlinux.org/title/Xorg/Keyboard_configuration#Adjusting_typematic_delay_and_rate |
| 2022-07-25 21:40:31 | <tjmciver> | Running that and clicking xmobar gives "_NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 1099, 0, 0, 0, 0, 0, 0, 1727, 0, 0" but . . . |
| 2022-07-25 21:41:07 | <tjmciver> | I also have trayer in the top right on my laptop screen and doing the same for that gives "_NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 19, 0, 0, 0, 0, 0, 1728, 1919, 0, 0" FWIW. |
| 2022-07-25 21:41:40 | <tjmciver> | Maybe it's trayer that's causing a strut on that external monitor. |
| 2022-07-25 21:43:05 | <tjmciver> | Also, some of the args I'm passing to trayer are "--SetDockType true", "--SetPartialStrut true" and "--expand true", in case one of them may be the cause. |
| 2022-07-25 21:44:04 | <tjmciver> | but I also have "--monitor primary" which I would expect to restrict it to only the primary monitor. |
| 2022-07-25 21:44:05 | <geekosaur> | those seem okay for a normal 1920x1080 screen. |
| 2022-07-25 21:44:24 | <wusticality1> | geekosaur: ever use that approach? |
| 2022-07-25 21:45:50 | <geekosaur> | which approach, changing xmorg.conf? I'd be very worried if that doesn't work |
| 2022-07-25 21:46:49 | <wusticality1> | specifically, i added a file here: /etc/X11/xorg.conf.d/00-keyboard.conf |
| 2022-07-25 21:47:02 | <wusticality1> | per the instructions I guess |
| 2022-07-25 21:48:32 | <geekosaur> | kmight check for an "EE" in Xorg.0.log referencing what you added |
| 2022-07-25 21:48:44 | <wusticality1> | sec |
| 2022-07-25 21:50:48 | <wusticality1> | Only thing I'm seeing in that file is this: "[ 34.042] (EE) systemd-logind: failed to release device: Device not taken" |
| 2022-07-25 21:51:23 | <wusticality1> | However, in Xorg.1.log, I see this line at the end: "[ 44.897] (EE) event2 - SteelSeries SteelSeries Apex Pro: client bug: event processing lagging behind by 26ms, your system is too slow" |
| 2022-07-25 21:51:32 | <wusticality1> | Which is just odd |
| 2022-07-25 22:01:22 | <wusticality1> | I wonder if 00-keyboard.conf is the wrong name - it's not clear to me if xorg will just load the first one it sees |
| 2022-07-25 22:02:56 | <wusticality1> | Oh interesting, this line is in the log: `[ 36.804] (**) Option "AutoRepeat" "264 48"` |
| 2022-07-25 22:03:08 | <wusticality1> | strange, i wonder why it's not working, looks like it was loaded |
| 2022-07-25 22:03:22 | <wusticality1> | unless there are separate settings for X and the console? |
All times are in UTC.