[19:43] <lubuntu> You'll never take me alive, copper!
[19:51] <krotera[m]> Might anyone have any idea why, in the key bindings GUI (the `Global Actions Manager`), I can set ANY combo of keys for a command *EXCEPT* for `Win + E`?
[19:51] <wxl> yes
[19:52] <wxl> https://manual.lubuntu.me/stable/F/keyboard_shortcuts.html
[19:53] <krotera[m]> > if the W(indows) key opens the LXQT application menu (equivilant of the windows start menu) in Global-keys, Openbox commands like window resizing (W + arrow keys) will not work correctly.
[19:53] <krotera[m]> Huh.
[19:54] <krotera[m]> But other `Win` combos work just fine. D: And I think I had `Win + E` set up before, but now I can't set it again. I guess "not work correctly" must mean "work sporadically".
[19:54] <krotera[m]>  * > if the W(indows) key opens the LXQT application menu (equivilant of the windows start menu) in Global-keys, Openbox commands like window resizing (W + arrow keys) will not work correctly.
[19:54] <krotera[m]> Huh.
[19:54] <krotera[m]> (`Win`, by itself, does indeed open the application launcher.)
[19:55] <wxl> in that case, nope.
[19:55] <wxl> what version are you on?
[19:55] <krotera[m]> Ubuntu 20.04 focal, 5.8.0-43-generic
[19:56] <kc2bez[m]> What did you bind `Win + E` to?
[19:56] <krotera[m]> Before, I bound it to `dolphin`, a file manager. Then I unbound it. Now, I can't bind anything to `Win + E`.
[19:57] <krotera[m]> `Win + Q` works just fine.
[19:57]  * krotera[m] uploaded an image: image.png (27KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/UKOhcPJdsCJLmQcMkFDtzneZ/image.png >
[19:57] <krotera[m]> I guess I should call it `Meta` instead of `Win`. But `Meta + E`, in particular, will not register at all in the red-boxed element. xD
[19:58] <krotera[m]>  * I guess I should call it `Meta` instead of `Win`. But `Meta + E`, in particular, will not appear at all in the red-boxed element when I press it. xD
[19:59] <krotera[m]>  * I guess I should call it `Meta` instead of `Win`. But `Meta + E`, in particular, will not appear at all in the red-boxed element when I press it. xD
[19:59] <krotera[m]> `Q`, `W`, `R`, `T`, `A`, `S`, `D`, all work. Just not `E`.
[20:01] <wxl> try removing that entry and creating a new one
[20:01] <krotera[m]>  * I guess I should call it `Meta` instead of `Win`. But `Meta + E`, in particular, **will not appear at all** in the red-boxed element when I press it. xD
[20:01] <krotera[m]> `Q`, `W`, `R`, `T`, `A`, `S`, `D`, all work. Just not `E`.
[20:02] <wxl> i certainly can't reproduce THAT behavior, though (where it won't take the keystroke)
[20:03] <krotera[m]> Did. The countdown in the red-boxed element just keeps going on `Meta + E`, as if I'm not pressing it.
[20:03] <lubot> [telegram] <teward001> is Meta+E mapped already elsewhere?
[20:03] <krotera[m]> <lubot "[telegram] <teward001> is Meta+E"> No
[20:04] <krotera[m]> Is there some way to open the Global Actions Manager with command line output, to spot any errors? : o
[20:04] <wxl> of course
[20:06] <krotera[m]> `xprop | grep WM_CLASS` reveals the Global Actions Manager GUI to be `lxqt-config-globalkeyshortcuts`, and that works. : D
[20:07] <krotera[m]> But sadly no errors print out when it's not accepting `Meta + E`. xD
[20:07] <krotera[m]>  * `xprop | grep WM_CLASS` and clicking the Global Actions Manager GUI reveals its command to be `lxqt-config-globalkeyshortcuts`, and that works. : D
[20:08] <krotera[m]>  * `xprop | grep WM_CLASS` and clicking the Global Actions Manager GUI reveals its command to be `lxqt-config-globalkeyshortcuts`, and launching it that way works. : D
[20:08] <wxl> you may want to try to run the actual daemon: /usr/bin/lxqt-globalkeysd
[20:08] <wxl> (which means you'll have to kill it first)
[20:11]  * krotera[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/cTdaffmeyWoMQgGpGThYawUW/message.txt >
[20:11]  * krotera[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/wXaNGlsIElDBRTBeJyGWHmZN/message.txt >
[20:12] <wxl> clearly not
[20:12] <krotera[m]> I only know how to interface with daemons via `systemctl`. D:
[20:13] <wxl> um
[20:14] <wxl> killall globalkeysd && globalkeysd
[20:14]  * krotera[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/ymzAGxSJiUSdkWcYlgAOxnGz/message.txt >
[20:15] <wxl> kill $(pgrep globalkeysd)
[20:15] <wxl> and if that still produces nothing, it's not running and that may well be your problem right there. you can further confirm with e.g. `ps aux | grep globalkeysd`
[20:18] <krotera[m]> `$(pgrep globalkeysd)` produces nothing, but `ps aux` did reveal `/usr/bin/lxqt-globalkeysd` running with a PID which I killed.
[20:18] <krotera[m]> There's also a `--color=auto globalkeysd` running which rotates its PID on every `ps aux` command. xD
[20:18]  * krotera[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/RjyQoKkPOiSbxWVEhtJDsSAz/message.txt >
[20:19] <krotera[m]>  * `$(pgrep globalkeysd)` produces nothing, but `ps aux` did reveal `/usr/bin/lxqt-globalkeysd` running with a PID which I killed.
[20:19] <krotera[m]> There's also a `--color=auto globalkeysd` running which changes its PID on every `ps aux` command. xD
[20:19] <wxl> UGH i meant lxqt-globalkeysd
[20:20]  * krotera[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/iOIOhsRxxBFpTBiOEYNztPys/message.txt >
[20:20] <krotera[m]> : D
[20:20] <krotera[m]> I guess the daemon's restarted, but the Global Actions Manager has the same problem. Still accepts everything else except for `Meta + E`.
[20:21] <wxl> can't reproduce so
[20:21] <wxl> of course you have dolphin so what other quirks does your system have relative to stock lubuntu?
[20:25] <krotera[m]> A few, I guess. :v I have many things installed, like Dropbox, Chrome, yakuake, etc. Modified my `~/.bashrc`. That's a hard question to answer comprehensively.
[20:26] <wxl> well, something there must be causing the conflict
[20:26] <krotera[m]> I also replaced `xscreensaver` with `xautolock` since `xscreensaver` was locking all except for one of my monitors. 😂
[20:27] <wxl> oh i'd file a bug against that. as a general rule, `xscreensaver` is the one and only solution for locking that actually works
[20:27] <wxl> which is why we are pretty adamant about not using anything else
[20:27] <krotera[m]> Apparently not. :v
[20:27] <wxl> you miss my point
[20:28] <wxl> there have been a ton of security bugs against other lockers
[20:31]  * krotera[m] uploaded an image: locker.png (1708KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/tXnPAewSlidZaiHGYYiPocNs/locker.png >
[20:31] <krotera[m]> There's a picture I took of it. xD
[20:31] <wxl> like i said, file a bug
[20:32] <krotera[m]> I filed a bug on Launchpad, but they told me to file it upstream. Do I do that https://www.jwz.org/xscreensaver/bugs.html ?
[20:32] <wxl> where's this launchpad bug?
[20:33] <krotera[m]> Well, it's private since it's security-related.
[20:33] <wxl> and?
[20:33] <wxl>  1. share the url and no one without privledges will be able to see it
[20:33] <krotera[m]>  * Well, it's private since it's security-related.
[20:33] <krotera[m]> https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1916003
[20:33] <ubottu> Error: launchpad bug 1916003 not found
[20:34] <wxl>  2. is there even any info on there that should be private?
[20:34] <wxl> yeah that bug doesn't even exist
[20:36] <wxl> guiverc: ^ didn't you see something like this with e.g. bug 1814490 ?
[20:36] <ubottu> bug 1814490 in xscreensaver (Ubuntu) "lubuntu 19.04/19.10 xscreensaver runs on single display, other display continues normally" [Undecided,New] https://launchpad.net/bugs/1814490
[20:36] <wxl> anyways, yep, that's upstream
[20:36]  * krotera[m] uploaded an image: image.png (75KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/JyDKeEtdZabKQDdqTJdJlpgd/image.png >
[20:36] <krotera[m]> <wxl "yeah that bug doesn't even exist"> Same URL I posted : o
[20:37] <wxl> very strange. i should have access to all of the private bugs but oh well
[20:38] <wxl> if it's not already resolved (5.45 is out upstream), then reporting it upstream would be the way to go
[20:39] <wxl> there were a bunch of bug fixes in 5.44 and 5.45
[20:40] <krotera[m]> Cool. ¦ p
[20:42] <krotera[m]> LXQt feels a little rough around the edges. It's incredibly smooth, graphically, though. 🤩 On no other DE do windows drag around as smoothly as they do on Windows (and you drag them a lot since ostensibly Openbox doesn't support window snapping/tiling).
[20:43] <wxl> xscreensaver has nothing to do with LXQt
[20:43] <wxl> and your problem with Meta-E is yours alone
[20:43] <wxl> but if you've got some other reason to say that…
[20:43] <wxl> (also Openbox has nothing to do with LXQt, either)
[20:44] <krotera[m]> That's true. xD I guess I should say Lubuntu, as a whole.
[20:44] <wxl> well you can always contribute and help make it better
[20:47] <krotera[m]> I would like that, but I probably need to be a little smarter first. : p
[20:47] <krotera[m]> Anyway, I appreciate the help.
[20:47] <wxl> i think you're selling yourself a little short
[20:47] <wxl> there's ALWAYS places people can help
[21:51] <guiverc> wxl, sorry didn't see the bug you mentioned, but 1814490 occurs when screens are positioned relative to one another in specific locations (with attached.clicked).  I expect that'll go with 0.16  (I don't look for it anymore, just slightly alter screen positions when it occurs)
[21:53] <wxl> guiverc: well tl;dr the issue was xscreensaver not locking on all screens
[21:54] <wxl> not sure about positioning and the person made a private bug report and promptly ran away sooooooo
[21:55] <guiverc> sorry I'm very distracted.. yep that occurs and I hope it'll be gone with 0.16, but I'm convinced it occurs with screens relatively positioned to one another.. I've got ~4 like bugs that all occur together (the screensaver can occur on it's own.. so it's a little different, but change screen position & it stops occurring too)
[21:56] <wxl> i wonder if it's something that occurs on other destop environments
[22:07] <guiverc> not that I've experienced.. it occurs on multiple boxes for me (most folks don't have one screen above another; but I've six screens on desk (2 high x 3)  & use 2x per box so vertical seemed easier
=== neo is now known as Guest90598