keyboard unresponsive while kinto is active - can't get install to work #684
Comments
|
|
Hi Josh! Thanks for your reply. Looks like the config.py is missing (see below). The xkeysnail github page provides an example config.py but this appears to be for emacs shortcuts and I'm guessing that kinto is supposed to have its own config. Not sure if I should just grab the example config. There's no config.py in the kinto github repo. Any suggestion? |
|
Linux/kinto.py It's in the repo. |
|
Oh sweet! I'll give this a shot when I'm back from vacation! I'll let you
know how it goes.
Thanks,
Buzuddha
…On Sat, Aug 27, 2022, 19:20 Zach Johnson ***@***.***> wrote:
@buzuddha <https://github.com/buzuddha> I was having the same issue on
Ubuntu 22.04 when using Wayland vs Xorg. To resolve it I followed these
steps:
1. Uninstal Kinto
2. Disable Wayland in /etc/gdm3/custom.conf (source
<https://askubuntu.com/questions/1410256/how-do-i-use-x-instead-of-wayland-on-22-04>
)
3. Reboot
4. Run xhost +SI:localuser:root (source
<https://github.com/mooz/xkeysnail#usage>)
5. Re-install Kinto
—
Reply to this email directly, view it on GitHub
<#684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJTISHO77X6QIKWSKPAY6LDV3LZILANCNFSM5X5TWDDQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hmmmm.. typically you can click on a gear icon or something on the login screen to switch to X11 mode. I may need to rework the installer - it’s not supposed to install on Wayland at all & tells users that when it properly detects wayland running. Something has changed though or maybe xwayland interferes.. I dunno. |
|
So I'm back to linux and want to actually get this working. I've gone through a fresh install of arch and am in Gnome but logged in with the x11 session via the gear in gdm. The install fails but xkeysnail opens and disables the entire keyboard Install Type: Bare Metal Logs and status if relevant xkbScreenshots Additional context This part to mee seems like the first issue that presents itself. I've googled but not much clarity on how to fix this. |
|
Looked into hellozach's advice. In /etc/gdm/custom.conf The other post cites errors I'm not seeing. But if I run The bottom is me mashing keys that don't do anything. By closing the terminal the keyboard works again.
|
Yes, closing the terminal ends the This part is technically not a problem, it's been there a long time: No one seems to know anything about why Some others have been able to follow the instructions here to get a working Kinto config: |
|
Thanks RedBearAK. I'm halfway through the keyszer instructions but am stumped. What does this mean? "need to drop the two files attached to this PR in your Kinto config folder" What is a PR? Where might these be attached? |
|
The page where the comment thread is located is a “Pull Request” that would change 2 files. At the top of the thread you’ll see something that says “Files changed (2)”. Go there and you would see the two files. But then you would have to figure out how to download the raw files. Instead, I’d recommend grabbing the newer version of my config from a comment further down the thread. But one of the include files in the zip may have two extensions “.py.py” that you may need to fix. |
|
Hi @RedBearAK, thanks for the explanation, I'm not so well versed. Ok so I pulled the toshy.zip and put everything in the correct spot. Sidenote, I had to manually load the uinput module for keyszer to start. This still killed my keyboard. In fact it killed mouse input too! I could see key presses/mouse clicks in the terminal, and see remaps indicated, but nothing happening. The first time I ran it, I realized I didn't have an F16 so had to hard reset. Ack! |
I’m not sure what this means. What exactly was the problem starting keyszer, and what exactly did you do? I’ve never had much luck with The config doesn’t detect the distro name, but that should just mean no distro-specific keymaps would activate. So that shouldn’t be any problem. Wondering exactly how you set up your permissions. It’s not recommended as best practice but have you tried running keyszer as root via xhost +SI:localuser:root |
This persisted after reboots. Anyhow, bummer that arch based distros are having issues. I can't seem to run it as sudo... I get this in the pip install So I had to add ~/.local/bin to the $PATH, but when I run via sudo, I get this error, even though I can see is there something about having installed via pip with the |
|
Arch tends to be pretty different from the Debian-based (Ubuntu) or Red Hat-based (Fedora) distros most desktop users are on. But Manjaro also seems to have its own special problems sometimes that don't always affect other Arch distros, from what I've seen. I've never had to do anything to make You should probably google up some explanations of how the If you do add to the path, you want to include the original path variable contents to avoid losing all the paths that exist: export PATH="$HOME/.local/bin:$PATH" This would put your local bin path at the beginning of the entire path string, but retain the existing You don't generally want to change root's path variable (although if you don't change the "rc" file for root, this won't be persistent, so don't worry about that, it will return to normal once you log out of the shell/terminal). The problem with root not knowing where /home/hugh/.local/bin/keyszer -w -v -c ~/.config/kinto/toshy.pyYou can You may want to google some Arch wiki information about |
|
Ack! Thanks for the very clear explanation! I think you're probably right about the permissions. I'll take this over to the Arch forum and see if they can help. I'll let you know what I find. If I can get it to work I'll try to put together a little write up. |
|
Okay! I was able to get xkeysnail working (but not keyszer) on arch! Will do a fresh install just to confirm the solution was in fact the one I thought it was. Will report back when I've confirmed. May not have time this weekend though. TBD! Yay! Mac shortcuts, a teams app and MS office in the browser! I can now use this computer as the main driver for work! |
|
@buzuddha what did you end up doing to get it to work? |
|
actually looks like I figured out a solution for myself. I got into this mess because I first accidentally ran the installer in wayland and it failed. I then logged out and logged back in with x11 and installed and then ran into all the problems in this issue. So for anyone else with this issue: try deleting the installer with something like -> |
|
I did thanks to Seth from the Arch forums. Seth is amazing. The main thing was to be sure to log in to gnome via xorg. Then after the install add the following two files:
and 2) then also run:
Then reboot. When the xkeysnail dialog comes up, initially it says inactive. If you click the menu and try restart, everything should work. |
|
This fixed it for me mooz/xkeysnail#164 (comment)
|
Just a reminder for everyone having this issue, "upgrading" |
Describe the bug
A complete install using either the method results in an unresponsive keyboard, perhaps related to xkeysnail.
Expected behavior
Install kinto.sh without error and have the bomb mac shortcuts so I can actually get work done.
Install Type: Bare Metal
Distro: 5.18.1-arch1-1
DE: Gnome
Branch: ?
Commit: b38c1a1
Logs and status if relevant
Additional context
Not exactly sure what I can do here. I've tried to enable xkeysnail, but doesn't seem to have an effect. Can't see keyswap. Happy for any ideas!
Thanks!
The text was updated successfully, but these errors were encountered: