| 2022-07-25 00:23:28 +0200 | alternateved | (~user@staticline-31-183-144-54.toya.net.pl) (Remote host closed the connection) |
| 2022-07-25 00:45:31 +0200 | <liskin> | https://packages.qa.debian.org/x/xmonad/news/20220722T175348Z.html \o/ |
| 2022-07-25 01:02:26 +0200 | <geekosaur> | \o/ |
| 2022-07-25 02:31:32 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds) |
| 2022-07-25 02:41:10 +0200 | byorgey | (~byorgey@155.138.238.211) |
| 2022-07-25 02:44:53 +0200 | tremon | (~tremon@83-84-18-241.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |
| 2022-07-25 02:56:53 +0200 | bla | (~bla@79.191.155.111.ipv4.supernova.orange.pl) (Ping timeout: 272 seconds) |
| 2022-07-25 03:00:34 +0200 | bla | (~bla@79.191.36.42.ipv4.supernova.orange.pl) |
| 2022-07-25 03:26:25 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-07-25 03:29:15 +0200 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 260 seconds) |
| 2022-07-25 03:39:03 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-07-25 03:42:08 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-07-25 03:46:26 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-07-25 03:47:59 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-07-25 04:02:37 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-07-25 04:03:18 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 240 seconds) |
| 2022-07-25 04:04:32 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-07-25 04:22:49 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-07-25 04:35:18 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 268 seconds) |
| 2022-07-25 04:50:43 +0200 | td_ | (~td@muedsl-82-207-238-027.citykom.de) (Ping timeout: 268 seconds) |
| 2022-07-25 04:52:13 +0200 | td_ | (~td@94.134.91.242) |
| 2022-07-25 04:54:36 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 276 seconds) |
| 2022-07-25 05:41:24 +0200 | catman | (~catman@user/catman) (Ping timeout: 276 seconds) |
| 2022-07-25 05:43:12 +0200 | catman | (~catman@user/catman) |
| 2022-07-25 07:04:06 +0200 | Buliarous | (~gypsydang@46.232.210.139) (*.net *.split) |
| 2022-07-25 07:04:14 +0200 | Buliarous | (~gypsydang@46.232.210.139) |
| 2022-07-25 07:07:34 +0200 | zawaken | (~zawaken@user/zawaken) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | deebo | (~globe@stonebay32.com) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | ElKowar | (~ElKowar@srv-fin.xware-gmbh.de) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | dminuoso | (~dminuoso@user/dminuoso) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | piele | (~piele@tbonesteak.creativeserver.net) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | brianbnt | (~brianbnt@user/brianbnt) (*.net *.split) |
| 2022-07-25 07:07:34 +0200 | totte | (~totte@h-82-196-112-155.A166.priv.bahnhof.se) (*.net *.split) |
| 2022-07-25 07:07:42 +0200 | deebo | (~globe@stonebay32.com) |
| 2022-07-25 07:07:46 +0200 | piele | (~piele@tbonesteak.creativeserver.net) |
| 2022-07-25 07:07:47 +0200 | totte | (~totte@h-82-196-112-155.A166.priv.bahnhof.se) |
| 2022-07-25 07:08:52 +0200 | brianbnt | (~brianbnt@user/brianbnt) |
| 2022-07-25 07:09:00 +0200 | zawaken | (~zawaken@user/zawaken) |
| 2022-07-25 07:11:23 +0200 | dminuoso | (~dminuoso@user/dminuoso) |
| 2022-07-25 07:12:52 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-07-25 08:03:13 +0200 | <Solid> | nice! |
| 2022-07-25 08:18:39 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:6822:a1ed:e2bc:fba) |
| 2022-07-25 08:35:30 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:6822:a1ed:e2bc:fba) (Ping timeout: 240 seconds) |
| 2022-07-25 08:41:19 +0200 | alternateved | (~user@staticline-31-183-144-54.toya.net.pl) |
| 2022-07-25 08:58:16 +0200 | dschrempf | (~dominik@2a01-036d-0118-b0ba-a1d6-3a5c-933d-2600.pool6.digikabel.hu) |
| 2022-07-25 09:07:53 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:c553:ccab:7bda:db3b) |
| 2022-07-25 09:35:01 +0200 | dschrempf | (~dominik@2a01-036d-0118-b0ba-a1d6-3a5c-933d-2600.pool6.digikabel.hu) (Quit: WeeChat 3.6) |
| 2022-07-25 10:10:25 +0200 | dschrempf | (~dominik@2a01-036d-0118-b0ba-fc6d-2b94-16ee-4aa3.pool6.digikabel.hu) |
| 2022-07-25 11:40:11 +0200 | amenonsen | (~amenonsen@pitta.toroid.org) (Remote host closed the connection) |
| 2022-07-25 11:40:33 +0200 | amenonsen | (~amenonsen@pitta.toroid.org) |
| 2022-07-25 12:47:21 +0200 | dschrempf | (~dominik@2a01-036d-0118-b0ba-fc6d-2b94-16ee-4aa3.pool6.digikabel.hu) (Quit: WeeChat 3.6) |
| 2022-07-25 15:09:30 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:c553:ccab:7bda:db3b) (Ping timeout: 240 seconds) |
| 2022-07-25 15:11:09 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:e514:c9e6:92ac:14d9) |
| 2022-07-25 15:17:25 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:e514:c9e6:92ac:14d9) (Ping timeout: 260 seconds) |
| 2022-07-25 16:40:57 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:175e:8c5b:e001:c3ec) |
| 2022-07-25 18:00:11 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-07-25 18:22:24 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) (Remote host closed the connection) |
| 2022-07-25 18:22:24 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) (Remote host closed the connection) |
| 2022-07-25 18:26:52 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) |
| 2022-07-25 18:27:11 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) |
| 2022-07-25 18:34:27 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) (Remote host closed the connection) |
| 2022-07-25 18:34:27 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) (Remote host closed the connection) |
| 2022-07-25 18:36:19 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) |
| 2022-07-25 18:37:30 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) |
| 2022-07-25 19:11:19 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-07-25 19:17:21 +0200 | elonsroadster[m] | (~elonsroad@2001:470:69fc:105::d121) |
| 2022-07-25 19:18:54 +0200 | <elonsroadster[m]> | liskin: wondering if you can quickly tell me what I need to do to make it so that dialog windows float by default. This hasn't worked for me since you overhauled the manage hook, but I'm feeling lazy and I don't wnat to try and figure out what the new incantation is on my own. I already tried the `isDialog --> doFloat` thing but that doesn't seem to work. Is there something else that I need to do? |
| 2022-07-25 19:21:39 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) (Remote host closed the connection) |
| 2022-07-25 19:21:39 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) (Remote host closed the connection) |
| 2022-07-25 19:22:39 +0200 | samhh | (7569f027cf@2604:bf00:561:2000::e4) |
| 2022-07-25 19:23:12 +0200 | alethkit | (23bd17ddc6@2604:bf00:561:2000::3ce) |
| 2022-07-25 19:23:33 +0200 | <alternateved> | What is wrong with `isDialog --> doFloat`? It works just fine |
| 2022-07-25 19:24:01 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-07-25 19:26:26 +0200 | <geekosaur> | not all dialogs set the EWMH dialog hook. some dialogs use the old style fixed size thing, others rely on `WM_TRANSIENT_FOR` for which there's a different matcher (`transience'`). also see `clientLeader` and its caveat |
| 2022-07-25 19:28:07 +0200 | <geekosaur> | that said, I don't really understand the question (and don't off the top of my head recall an overhaul of the `manageHook`, but I'm not having a very good day today) |
| 2022-07-25 19:29:31 +0200 | <elonsroadster[m]> | geekosaur: this was about a year ago,maybe a bit more, it used to be that (i think maybe) the default manage hook just did all of this automatically. Or maybe it was something like the ewmh config modifier. Not sure i remember exactly, but something changed and floating dialogs has not worked for me since then. |
| 2022-07-25 19:31:17 +0200 | alternateved | (~user@staticline-31-183-144-54.toya.net.pl) (Ping timeout: 245 seconds) |
| 2022-07-25 19:31:36 +0200 | <geekosaur> | hm. I've always had a set of windows for which it's never worked immediately but I consider it a flaw in those applications since they don't set appropriate window properties. otherwise I use the `isDialog` thing and it's always worked |
| 2022-07-25 19:32:30 +0200 | <geekosaur> | EWMH doesn't even touch the `manageHook` (I just doublechecked) |
| 2022-07-25 19:35:14 +0200 | <elonsroadster[m]> | hmmm maybe its pinentry that changed |
| 2022-07-25 19:35:31 +0200 | <elonsroadster[m]> | from what I can tell looking at xprop it doesnt set _NET_WM_WINDOW_TYPE_DIALOG, but I SWEAR That is used to work for me |
| 2022-07-25 19:38:17 +0200 | <geekosaur> | hm, pinentry worked for me until I told it to put my key in my login keyring |
| 2022-07-25 19:40:56 +0200 | <geekosaur> | (then I stopped seeing it, as I intended) |
| 2022-07-25 19:42:24 +0200 | <geekosaur> | (are we talking about the same pinentry, though? you shouldn't be able to run xprop on it…) |
| 2022-07-25 19:45:41 +0200 | <elonsroadster[m]> | why not? its a xwindow |
| 2022-07-25 19:45:47 +0200 | <elonsroadster[m]> | i was definitely able to run xprop on it |
| 2022-07-25 19:45:54 +0200 | <elonsroadster[m]> | for me it actually gets minimized atm |
| 2022-07-25 19:45:57 +0200 | <elonsroadster[m]> | which is very strange |
| 2022-07-25 19:47:35 +0200 | <geekosaur> | it does a grab to isolate itself from other programs that might try to snoop your key |
| 2022-07-25 19:49:11 +0200 | <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 19:51:02 +0200 | <elonsroadster[m]> | hmmm thats not what happens for me |
| 2022-07-25 19:53:12 +0200 | <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 19:53:36 +0200 | <elonsroadster[m]> | im using pinentry gtk |
| 2022-07-25 19:53:56 +0200 | <elonsroadster[m]> | with a totally stock config |
| 2022-07-25 19:54:18 +0200 | <geekosaur> | --no-global-grab, -g |
| 2022-07-25 19:54:18 +0200 | <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 19:54:38 +0200 | <geekosaur> | should be the same for other X11-based pinentry variants |
| 2022-07-25 19:56:38 +0200 | <elonsroadster[m]> | yeah i dont think im using that though |
| 2022-07-25 19:57:33 +0200 | <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 20:15:23 +0200 | <liskin> | pinentry works here out of the box |
| 2022-07-25 20:15:41 +0200 | <liskin> | I presume it just uses the core functinality of fixed size ⇒ float |
| 2022-07-25 20:16:02 +0200 | <liskin> | which can probably be broken by a suitably weird manageHook |
| 2022-07-25 20:17:59 +0200 | <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 20:34:29 +0200 | catman | (~catman@user/catman) (Ping timeout: 244 seconds) |
| 2022-07-25 20:55:17 +0200 | catman | (~catman@user/catman) |
| 2022-07-25 21:09:50 +0200 | Forkk | (~forkk@li926-228.members.linode.com) |
| 2022-07-25 21:18:01 +0200 | tjmciver | (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-25 21:19:17 +0200 | <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 21:29:17 +0200 | <geekosaur> | xmonad shouldn't have any effect on caps lock |
| 2022-07-25 21:44:59 +0200 | catern | (~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407) (Quit: Using Circe, the loveliest of all IRC clients) |
| 2022-07-25 22:02:16 +0200 | <tjmciver> | geekosaur, thanks, I'll look elsewhere then. |
| 2022-07-25 22:03:27 +0200 | <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 22:06:20 +0200 | <tjmciver> | I'm running NixOS so I stronly suspect the issue to be there. |
| 2022-07-25 22:11:12 +0200 | wusticality | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 22:11:45 +0200 | <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 22:11:49 +0200 | <wusticality> | Even tried something like this: |
| 2022-07-25 22:12:08 +0200 | <wusticality> | (sleep 6 && xset r rate 264 48) & |
| 2022-07-25 22:12:20 +0200 | <wusticality> | just curious if there's a better, more reliable way (and also one that works haha) |
| 2022-07-25 22:12:26 +0200 | <wusticality> | I'm assuming it's some kind of timing issue |
| 2022-07-25 22:13:10 +0200 | <geekosaur> | if you run it in a terminal, do you get an error message? |
| 2022-07-25 22:15:24 +0200 | <wusticality> | nope, works just fine if I run it from a terminal |
| 2022-07-25 22:15:40 +0200 | <wusticality> | Tried both from xmonad.hs (via spawnOnce) and in .xinitrc, and neither work |
| 2022-07-25 22:15:50 +0200 | <wusticality> | perhaps xmonad is launching before x has finished booting up? |
| 2022-07-25 22:15:54 +0200 | <wusticality> | that's all i can think |
| 2022-07-25 22:16:00 +0200 | <wusticality> | https://bbs.archlinux.org/viewtopic.php?id=104338 |
| 2022-07-25 22:16:11 +0200 | <wusticality> | that thread seems to say as much, but none of their solutions work for me thus far |
| 2022-07-25 22:18:44 +0200 | <geekosaur> | xmonad would crash in that case |
| 2022-07-25 22:19:00 +0200 | <geekosaur> | the first thing it does is openDisplay |
| 2022-07-25 22:22:21 +0200 | <wusticality> | are you saying xmonad.hs doesn't fire up until x is fully initialized? |
| 2022-07-25 22:23:19 +0200 | wusticality1 | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 22:23:26 +0200 | wusticality | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Leaving) |
| 2022-07-25 22:23:46 +0200 | <geekosaur> | xmonad.hs would crash if X were not fully initialized |
| 2022-07-25 22:24:02 +0200 | <geekosaur> | with an error in openDisplay |
| 2022-07-25 22:24:10 +0200 | <wusticality1> | strange, I wonder why it's not working |
| 2022-07-25 22:24:18 +0200 | <wusticality1> | maybe spawn instead of spawnOnce? |
| 2022-07-25 22:24:20 +0200 | <geekosaur> | possibly something is overriding it |
| 2022-07-25 22:24:52 +0200 | <geekosaur> | wait, you're doing this in your xmonad.hs? although I guess that shouldn't matter |
| 2022-07-25 22:25:44 +0200 | <wusticality1> | well, i was trying it in ~/.xinitrc first |
| 2022-07-25 22:25:46 +0200 | <wusticality1> | but that didn't work |
| 2022-07-25 22:25:56 +0200 | <wusticality1> | that file is definitely being hit though cause I have xnumlock & in there |
| 2022-07-25 22:25:58 +0200 | <wusticality1> | and that works fine |
| 2022-07-25 22:27:15 +0200 | <geekosaur> | so that would suggest something is overriding it. |
| 2022-07-25 22:28:25 +0200 | kevin_ | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 22:28:46 +0200 | kevin_ | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Client Quit) |
| 2022-07-25 22:29:50 +0200 | chomwitt | (~chomwitt@2a02:587:dc00:5a00:175e:8c5b:e001:c3ec) (Ping timeout: 240 seconds) |
| 2022-07-25 22:31:13 +0200 | <wusticality1> | boy, I have no idea what - certainly nothing I've setup |
| 2022-07-25 22:32:32 +0200 | wusticality | (~user@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 22:42:35 +0200 | wusticality1 | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed) |
| 2022-07-25 22:42:35 +0200 | wusticality | (~user@c-67-161-204-49.hsd1.co.comcast.net) (Remote host closed the connection) |
| 2022-07-25 22:52:41 +0200 | wusticality1 | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 22:52:54 +0200 | <wusticality1> | out of mere curiosity, all these commands are x-specific - what happens if you use wayland? |
| 2022-07-25 22:53:06 +0200 | <wusticality1> | hoping there are analogs for that |
| 2022-07-25 23:08:14 +0200 | wusticality1 | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed) |
| 2022-07-25 23:21:17 +0200 | benemorius | (~benemoriu@2001:470:4bb0:919::1:56) (Remote host closed the connection) |
| 2022-07-25 23:21:40 +0200 | benemorius | (~benemoriu@2001:470:4bb0:919::1:56) |
| 2022-07-25 23:21:55 +0200 | <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 23:21:59 +0200 | <geekosaur> | I have no idea. I don't trust Wayland enough to consider it |
| 2022-07-25 23:22:52 +0200 | <geekosaur> | struts come from windows. avoidStruts attempts to apply them, but misusing it can lead to surprises |
| 2022-07-25 23:23:29 +0200 | <tjmciver> | Do I need to use `avoidStrutsOn` instead? |
| 2022-07-25 23:27:20 +0200 | <geekosaur> | can I see your layoutHook? |
| 2022-07-25 23:27:46 +0200 | <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 23:31:33 +0200 | <tjmciver> | My config is pretty sparse: https://gitlab.com/tmciver/home-manager-config/-/blob/master/programs/xmonad/config.hs#L32 |
| 2022-07-25 23:35:50 +0200 | <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 23:36:38 +0200 | <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 23:37:16 +0200 | wusticality1 | (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-25 23:37:55 +0200 | <wusticality1> | tried this, but it also didn't work :( |
| 2022-07-25 23:37:56 +0200 | <wusticality1> | https://wiki.archlinux.org/title/Xorg/Keyboard_configuration#Adjusting_typematic_delay_and_rate |
| 2022-07-25 23:40:31 +0200 | <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 23:41:07 +0200 | <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 23:41:40 +0200 | <tjmciver> | Maybe it's trayer that's causing a strut on that external monitor. |
| 2022-07-25 23:43:05 +0200 | <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 23:44:04 +0200 | <tjmciver> | but I also have "--monitor primary" which I would expect to restrict it to only the primary monitor. |
| 2022-07-25 23:44:05 +0200 | <geekosaur> | those seem okay for a normal 1920x1080 screen. |
| 2022-07-25 23:44:24 +0200 | <wusticality1> | geekosaur: ever use that approach? |
| 2022-07-25 23:45:50 +0200 | <geekosaur> | which approach, changing xmorg.conf? I'd be very worried if that doesn't work |
| 2022-07-25 23:46:49 +0200 | <wusticality1> | specifically, i added a file here: /etc/X11/xorg.conf.d/00-keyboard.conf |
| 2022-07-25 23:47:02 +0200 | <wusticality1> | per the instructions I guess |
| 2022-07-25 23:48:32 +0200 | <geekosaur> | kmight check for an "EE" in Xorg.0.log referencing what you added |
| 2022-07-25 23:48:44 +0200 | <wusticality1> | sec |
| 2022-07-25 23:50:48 +0200 | <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 23:51:23 +0200 | <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 23:51:32 +0200 | <wusticality1> | Which is just odd |