When I boot up my system (I'm using Ubuntu 20.04), the keyboard isn't detected. The only way to have it working is to suspend the system and wake it up back. Then the keyboard is fully functioning. I tried using different acpi_osi kernel parameters without success. The same happens with differents Live USB. The keyboard works in BIOS though. My laptop model is Clevo PB71DF2-G and I fresh installed Ubuntu on it. Everything else works as expected. Does anyone have a solution ?

I'm trying to get my keyboard to use the us layout with variation altr-intl and no deadkeys. Somehow my xorg-keyboard-config does not take effect. I looked up the config here arch-wiki but there seems to be a mistake in my config which I was unable to find. My current (not working) config looks like this: /etc/X11/xorg.conf.d/00-keyboard.conf # Written by systemd-localed(8), read by systemd-localed and Xorg. It's # probably wise not to edit this file manually. Use localectl(1) to # instruct systemd-localed to update it. Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "us" Option "XkbModel" "pc105" Option "XkbVariant" "altgr-intl" Option "XkbOptions" "nodeadkeys" EndSection I get it to work by using the following command but as you might know this is not persistent: setxkbmap -layout us -variant altgr-intl -option nodeadkeys I don't want this command to end up in my xprofile file or such. I would prefere to do it in xorg as I did with my trackpad, mouse ect. The keyboard I'm using is a keychron k2 connected by cable. Here is the output of xinput, in case the keyboard doesn't get identified correclty: xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Synaptics TM3053-003 id=11 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)] ⎜ ↳ Keytron Keychron K2 id=15 [slave pointer (2)] ⎜ ↳ Logitech Wireless Mouse id=17 [slave pointer (2)] ⎜ ↳ Logitech Wireless Keyboard PID:4023 id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=10 [slave keyboard (3)] ↳ Keytron Keychron K2 id=13 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=14 [slave keyboard (3)] ↳ Keytron Keychron K2 id=16 [slave keyboard (3)] ↳ Logitech Wireless Keyboard PID:4023 id=19 [slave keyboard (3)] I tried to identify the keyboard by using "MatchIsProduct" "Keytron Keychron K2" without any luck either. I'm running manjaro i3 community edition. The keyboard settings set in the manjaro-settings are also the wanted layout so I don't think that these settings would mess up my xorg config. I'm trying this on a thinkpad T550. With the current config I get the us keyboard without deadkeys but the altgr-intl variant is not active.

Ctrl+S stops all output to the terminal which can be restarted with Ctrl+Q. But, why does Ctrl+S exist in the first place? What problem was trying to be solved by putting that control sequence in place?

In my current (Fedora 37) XFCE setup, I have sticky keys and all other accessibility features disabled. However Stickey keys are still on, and my Alt-Gr key randomly becomes stuck when I need to enter a couple special characters in a row. I have two problems: I don't know how to "un-stick" that stuck key, other than switching to another keyboard layout with ibus. Even though I have all sticky-key features disabled, they still appear to be enabled, even though xbset q shows them as off.

Accessibility Features (AccessX) = Off
Sticky-Keys = Off

Is there a way how I can permanently, once and for all, disable accessibility features, as in perhaps uninstall a library, etc?

I'm trying to flash my DZ60RGB V2 keyboard on Arch Linux. I installed qmk package setup qmk_toolbox using qmk setup command. In the process it warned me about missing udev rules which I added when setting up ⚠ Missing or outdated udev rules for 'atmel-dfu' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'kiibohd' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'stm32' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'bootloadhid' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'usbasploader' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'massdrop' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'caterina' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. After that compiled default keymap successfully and flashed while in the Bootloader mode. $ qmk compile -kb dztech/dz60rgb/v2 -km default $ qmk flash -kb dztech/dz60rgb/v2 -km default QMK Firmware 0.13.34 Making dztech/dz60rgb/v2 with keymap default and target flash avr-gcc (GCC) 11.2.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Size before: text data bss dec hex filename 0 26626 0 26626 6802 .build/dztech_dz60rgb_v2_default.hex Copying dztech_dz60rgb_v2_default.hex to qmk_firmware folder [OK] Checking file size of dztech_dz60rgb_v2_default.hex [OK] * The firmware size is fine - 26626/28672 (92%, 2046 bytes free) Bootloader not found. Trying again every 0.5s (Ctrl+C to cancel).....^Cmake[1] : *** [tmk_core/avr.mk:331: flash] Interrupt I also tried to erase through dfu-programmer which failed again. $ dfu-programmer atmega32u4 erase dfu-programmer: no device present. I tried using sudo but the result was the same. I tried the same thing on Ubuntu 21.04 which result in the same error. How ever via identifies the keyboard as DZ60RGB V2 and I can make key changes fine. Edit: lsusb identifies the keyboard as followr Bus 001 Device 010: ID 445a:1121 DZTECH DZ60RGB When it is connected in Bootloader mode, the device is is shown as follows. Bus 001 Device 011: ID 03eb:2045 Atmel Corp. LUFA Mass Storage Demo Application

Is there a utility that allows to graphically display the current keyboard layout? This can be useful, for example, when writing in a foreign language and having the physical keyboard only indicating the local language (positioning of symbols, etc.). I would like to get a display similar to the following:

I've tried everything mentioned on the answers mentioned in the following post: https://unix.stackexchange.com/questions/255509/bluetooth-pairing-on-dual-boot-of-windows-linux-mint-ubuntu-stop-having-to-p But I've made no progress. A few details about my system: Keyboard: Logitech K380 (Bluetooth) Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Windows 10 (Latest edition as of writing this post) After changing my keys in linux to the ones from windows, the keyboard connects for a fraction of a second, before disconnecting, and I'm unable to understand why. My keyboard has 3 profiles that I can switch from and I tried all combinations of profile choice in windows and linux. I've spent quite a few hours on this and any help would be appreciated. Please let me know if I am missing any details that might help.

My keyboard has a mind of its own and it's driving me crazy. I'm convinced it's not *entirely* a hardware problem, hence this question. Computer is a low-end laptop, fairly recent model. A group of exactly 7 keys (9 0 o p l . UP_ARROW) will spontaneously stop responding for (seemingly) random periods. Sometimes I can wake them up by holding one down for a few seconds, at which point they all begin to function again. After "waking", the keys will often be hypersensitive (type "p" and get "ppp") or only function independently and not in combination (CTRL-p will be ignored). After one reboot the whole problem disappeared completely for two months. So it seems there's at least a software component to it - and therefore the potential for a workaround. An [almost identical issue](https://forum-en.msi.com/index.php?threads/the-keys-on-my-keyboard-randomly-stop-working-does-anyone-know-how-to-fix-this-issue.387039/) has been reported for MSI laptops. Replacing the keyboard would be either extremely tricky or very expensive. I've sometimes been resorting to a USB keyboard but it's a total PITA. Any ideas for workarounds if not a magic solution?

I injured my hand so that typing is now difficult. I have a touchscreen monitor on my laptop and am running Debian. Is there an on-screen keyboard which has swipe capabilities like the Google Keyboard on my android device? I know of Florence Keyboard and several alternatives , but they don't seem to have swiping.

I've been working with a keyboard to remap certain keys and create macros etc. I understand that the keyboard (via USB, I'm talking about a desktop computer with a USB HID keyboard) provides a scancode that is dependent on the keyboard's hardware, is mapped to keycodes based on the rules made up from various hwdb resources. Those keycodes are then interpreted by the operating system. I find that evtest gives the best results directly from the keyboard since it contains the keyboards scancodes, keycodes and key symbols all in one neat little output. To make it cleaner I usually grep the output to be even tidier: sudo evtest | grep -B1 "value 1" However, the codes as used by xmodmap and various applications are those as output (and *if* output) y xev. I don't have a nice grep for xev, I just filter by keyboard events: xev -event keyboard This questions I have are * Do keyboards exist where MIN_KEYCODE is set to something other than 8? * From the linked question, I see that MIN_KEYCODE is hard coded on line 72 of https://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/tree/src/evdev.c * Why is there a difference in the keycodes as produced by xev vs evtest I'm sure someone will suggest it is because the first 8 codes are reserved, but that should be irrelevant, shouldn't it? The keycode, reserved or not, should it not be output as a raw code than a value which is transposed (whether by arbitrary or fixed value) and can lead to errors? I really am just trying to understand the difference as to why some programs output and why some system require input that are out by 8 and how to ratify that inconsistency in my mind.

I would like to have a way of switching the audio output device (internal speakers/headphones to bluetooth speakers etc) by keyboard actions (which I usually can do without searching, finding and putting my glasses on my nose). Plasma tray elements can be activated with shortcuts, and thus I can connect, disconnect, switch between bluetooth devices by keyboard, because when the drop-down menu is visible, selection with arrow-keys and Enter to activate does the trick. But that doesn't work when trying to switch between audio devices themselves. I can bring forth the audio volume tray element with a shortcut: but further interaction by keyboard is limited to volume level. There is a widget called [audio device switcher](https://store.kde.org/p/1195707/) which brings the options more to the front, but its shortcut does nothing. Overall, it lacks keyboard interaction. The closest thing to what I want is to simply disable bluetooth by the first method *IF* that device is the one that is currently playing...

I'm running Firefox on Ubuntu 24.04 with the KDE desktop environment under X11 (not Wayland). Firefox works normally for several days without issues. However, suddenly, it stops responding to keyboard input in a peculiar way: keystrokes are registered, but they are delayed by 17 seconds before appearing. This delay only affects Firefox - other applications like Konsole, gedit, Brave, and VLC respond to keyboard input normally without any lag. These are affected: * Address field * Copies in Print dialog * Text field in Gmail These are not affected: * Page-Up/Down in scrolling * CTRL-Page-Up/Down (change tab) * CTRL-P (open print dialog) * Esc (Cancel print dialog) The system is otherwise stable, and restarting Firefox resolves the issue temporarily. The problem may reappear hours or days later, seemingly at random. I haven’t noticed any specific triggers yet. ibus restart does not fix it. Has anyone experienced this issue or have insights into what might cause Firefox to exhibit this delayed keyboard input behavior under these conditions? Are there logs or debugging steps I could use to narrow down the cause? OS: Ubuntu 24.04 DE: KDE (using X11, not Wayland) Firefox: Mozilla Firefox 135.0.1

I am working on a system that runs chromium in a docker container, and the docker container is running on a linux system. The screen attached is a touch screen. I have heard numerous customer complains about our onscreen keyboard so I would like to change it's configuration, appearance and functionality if possible. However to do this, I need to know what keyboard is being used/displayed. **How can I identify which of the various linux on screen / touch screen keyboards is being used?** I was looking through a list I found and I coudln't find any that look like the keyboard our system uses: - Are there files or other places I should check on the system? - How can I tell where the keyboard is coming from? (Chromium? Docker container? Base Linux system?) ---------- More information about the system: - The system is rather minimal, there is no traditional desktop environment that I could find - It seems to use X11, where there is an X server container running and the chromium container is a client - After installing proper deps/libs inside the display server container, I was able to run xeyes and xclock and it showed up on the display. - When you first SSH to the device, running cat /etc/issue reads carlOS (Containerized Application Realtime Linux Operating System) 1.0.0 - When you exec into the container running chromium, running cat /etc/issue reads Debian GNU/Linux 12 - When you exec into the display server container, running cat /etc/issue reads Ubuntu 22.04.2 LTS Things I've tried: - Chromium container

# echo $DESKTOP_SESSION

# ls /usr/bin/*session
/usr/bin/dbus-run-session
# HardInfo
sh: 4: HardInfo: not found
# ps -A | egrep -i "gnome|kde|mate|cinnamon|lxde|xfce|jwm"
# env | grep XDG_CURRENT_DESKTOP
# echo $XDG_CURRENT_DESKTOP
# lsb_release -a
sh: 67: lsb_release: not found

- display server container

# echo $DESKTOP_SESSION

# ls /usr/bin/*session
/usr/bin/dbus-run-session
# HardInfo
sh: 3: HardInfo: not found
# ps -A | egrep -i "gnome|kde|mate|cinnamon|lxde|xfce|jwm"
# env | grep XDG_CURRENT_DESKTOP
# echo $XDG_CURRENT_DESKTOP

# lsb_release -a
sh: 7: lsb_release: not found

For around 2-3 weeks I have the problem with Fedora 42 on my Dell Precision 5530 that my Ctrl keystroke is not registered. I did not change recently any keyboard configuration. For example when I try to copy text by pressing Ctrl + C repeatedly in a text editor it replaced my text with ccccc. After several attempts it works. Same applies for undo Ctrl + Z or pasting Ctrl + v. I have this with any combinattion using the Ctrl button. The problem is that this happens randomly every hour or even more often with my built-in keyboard, with my external home keyboard and the bluetooth keyboard. This happens in X11 and in Wayland. My home keyboard is also connected via a KVM switch on my PC that is also running Fedora 42 and I don't have any problem there. I'm not sure if this problem also occurs with other keys Alt or Shift but I am using Ctrl heavely as a developer using IntelliJ. I have this problem in any application besides my IDE. I tried checking keyrelease registration on hardware level but it makes it very difficult since I can' t reproduce it on command. I used this command: xev | grep -i keyrelease -A5 Why does my Ctrl randomly not work? Fedora release 42 (Adams) NAME="Fedora Linux" VERSION="42 (Workstation Edition)" RELEASE_TYPE=stable ID=fedora VERSION_ID=42 VERSION_CODENAME="" PLATFORM_ID="platform:f42" PRETTY_NAME="Fedora Linux 42 (Workstation Edition)" ANSI_COLOR="0;38;2;60;110;180" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:42" DEFAULT_HOSTNAME="fedora" HOME_URL="https://fedoraproject.org/ " DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f42/system-administrators-guide/ " SUPPORT_URL="https://ask.fedoraproject.org/ " BUG_REPORT_URL="https://bugzilla.redhat.com/ " REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=42 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=42 SUPPORT_END=2026-05-13 VARIANT="Workstation Edition" VARIANT_ID=workstation Fedora release 42 (Adams) Fedora release 42 (Adams)

I have copied my keyboard config(.Xmodmap file) from arch to kali. It is sourced in .xsessions and some keys work fine. However some keys are not good, for example I use the first letter row of the keyboard with AltGr to write numbers. But Now using AltGr with a does not write 1 however using it with e writes 3. Also when I press the alt-space it is intended to swap the languages of input however it takes 3 presses to get to the language and in between is either random characters or the layout that I want when I press AltGr ( the first letter line becomes numbers but without me pressing AltGr) Here for example why is 3 working and 1 not: keycode 24 = a A Arabic_dad Arabic_fatha 1 AE NoSymbol U2066 keycode 25 = z Z Arabic_sad Arabic_fathatan 2 less NoSymbol U2067 keycode 26 = e E Arabic_theh Arabic_damma 3 cent NoSymbol U2068

On my Ubuntu 20.04 (problem persists since 16.04) Sony VAIO laptop if I close the lid, wait till the yellow led to blink and then turn the laptop on again, awakes everything but keyboard, which turns on it's backlight after first keypress but doesn't react to anything, so does the touchpad. So I get almost fully working system, but completely unusuable. My problem is that I don't even know where to search for problem origin. I don't know how the laptop power and keyboard management works in Ubuntu, not on systemd or SysV level, nor on kernel level. So, no logs for you, my friends, until you ask for any. =) How can I solve this very annoying issue please?

I'm having a frustrating issue with Electron-based applications while using Wayland. The Delete key on the numpad, which is supposed to remove characters to the right of the cursor, does not function as expected. However, it works correctly when NumLock is enabled — outputting decimal (.) characters. I have verified that the keyboard is not the issue because the same Electron applications function properly under X11 sessions, and also the rest of the applications that I used run fine under Wayland without any keyboard-related problems. I'm using Arch Linux with GNOME. This is some relevant information about my system:

$ uname -a
Linux uplink 6.12.34-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 19 Jun 2025 15:05:14 +0000 x86_64 GNU/Linux

$ echo $XDG_SESSION_TYPE
wayland

$ localectl
System Locale: LANG=en_US.UTF-8
    VC Keymap: (unset)         
   X11 Layout: (unset)

$ setxkbmap -print -query
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
rules:      evdev
model:      pc105
layout:     us

$ gsettings get "org.gnome.desktop.input-sources" "sources"
[('xkb', 'us'), ('xkb', 'es')]

$ gsettings get "org.gnome.desktop.input-sources" "xkb-options"
['numpad:microsoft']

Again, the issue is present in all Electron-based applications that I use, so it's consistent in that sense 😬 Has anyone else encountered this issue with Electron applications on Wayland? Are there any known workarounds or fixes for this problem?

After updating from Ubuntu 16.04 to 18.04, the login screen automatically changes to only accepting the password via clicking a virtual onscreen keyboard.  It is very inconvenient and annoying having to switch between several virtual screens simply to input a password.  I have searched online on how to disable this inconvenient feature of onscreen keyboard, but haven't found a good solution.  Any expert here has a green thumb for this issue? What I tried: * settings → universal access → screen keyboard: \ Setting the screen keyboard to "off" does not solve the above mentioned problem.

I am using an Acer Swift One laptop with Windows 10. The keyboard is a standard German keyboard. I downloaded bash today from git-scm.com/download/win and tried some commands. For some reason bash shows k instead of ~ when pressing the tilde key. Any help or advice on what I'm doing wrong?

The Volume Scroll Wheel I am talking about in the title of the question is indicated on the image below. The wheel's functionality is the following: when you ***scroll up - volume increases***; ***scroll down - volume decreases***. When you ***press it - volume mutes and non-mutes***. I want to change its functionality to the one ***that mouse wheel has - scroll through content***. What I've tried already is trying to accomplish this in Lofree Key Mapper software, but failed, as there was no options to change the wheel's functionality. And overall as I understand you cannot change the wheel's functionality because the Lofree Flow Lite's keyboard manual says that this wheel is the *Volume Scroll Wheel*, implying that its functionality cannot be changed. And by the way, the Key Mapper software is for Win/Mac only. So my musings brought me to realization that if I cannot change the wheel's functionality in the keyboard itself, maybe I could try *changing how my OS will interpret signals my keyboard send to the CPU*. Now, I do not completely understand how a keyboard and a CPU interact, but I do realize that when you press a key, keyboard send a scancode (a sequence of numbers that identifies each key). These scancodes are mapped to keycodes later. Each keycode corresponds to a function that defines how a program should react on a keypress. I also understand that there are many so-called "stopping points" (however, I'm unsure what is meant by a stopping point) between the moment a key is pressed and the moment the CPU registers it. So maybe I could interfere this process in the following way: 1. I scroll the keyboard's wheel; 2. The keyboard sends the scancode to increase/decrease the volume to the CPU; 3. I intercept the scancode and change its value to 'scrolling the page' (i.e. to the functionality of a mouse wheel); 4. The CPU gain the instruction to scroll a page, not to increase/decrease volume. Now I understand that my knowledge and explanation are quite superficial, but I hope you get what I meant and will provide any suggestions. Thanks in advance.