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.

I have a problem when i type ´ + E or ´ + A, it should produces É and Á but it is deleted instantaneously. In firefox search bar it works as expect, but in skype or whatsapp it doesnt. My keybord is abnt2. I'm using Archlinux and Firefox 132.0.2 (64-bits) how to I provide info for the plugins I have?

I use Debian testing with XFCE as desktop environment. I have a german keyboard and sometimes use ^ (circumflex). When I hit that key once, the symbol is shown with an underscore. I have to hit it again to get rid of that underscore. I assume this is to get symbols like ⁴ etc., but I don't want that functionality, I never use it. But I don't know where I can turn it off. Can anyone tell me how to turn that off in xfce? At the moment I hit that key four times to show ^^ but that's annoying! edit: as requested: oli@DESKTOP-SJIB21T:~$ locale LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= The keyboard model in use is "Generic PC-Keyboard with 105 keys" and the layout was "use system settings". Now it is "Deutsch (ohne Akzenttasten)", with those settings it works.

I have a Debian 11 box running the Cinnamon DE. My keyboard layout is, per localectl status:

System Locale: LANG=en_GB.UTF-8
       VC Keymap: uk
      X11 Layout: gb
       X11 Model: pc105

while $GTK_IM_MODULE is ibus. My problem is that this setup has *dead keys* enabled and I really don't want that. My question: what must I change to turn dead keys off? Strange observation: I have a second debian-11 machine which runs emacs EXWM as window manager and the exact same keyboard setup (as far as I can see) and here I have no dead keys exactly as I want. Does the desktop environment impact this issue?

My preferred keyboard configuration is US-International. When I use it on MS-Windows and type certain special characters (i.e., ~ ' ") followed by a, o n I get á ó or ñ as I wish. However when I type these characters followed by a letter that doesn't match, I will get that special character followed by the letter. So if I want to type, let's say, "q I can do it by pressing "q. However, if I do the same on Gnome I need to do it like "␣q, otherwise I get an audible bell. Also, if I want to type two single quotes, in Gnome I need to type ' four times, instead of the two times it takes on MS-windows. I know it is a rather minor annoyance, but it does get to me, and I see GNU+Linux as a highly customizable OS, and I'd like to learn more about how do I do such things. Changing to the normal US keyboard is not an option, because I need to use characters such as á ó or ñ for typing in Spanish. --- note: I am using Debian

In short, I am trying to type the acute e (é) character. For some reason, on my office computer (Linux Mint Cinnamon), I cannot write the character as I am used to. The way I would normally do it, is by pressing AltGr\\, release, e. The problem with this system is that the acute character ´ immediately appears, and the e character after it. So instead of é, I get ´e. It is the same for other characters, for instance, if I wanted ñ, I would press AltGr¨, then n. But in reality, I get ~n. Then ~ immediately appears. My keyboard layout is Norwegian.

My Window Manager/Desktop Environment has some applications where the dead keys (e.g.\, ~, ö) are not working by default, when I press then, they sometimes doesn't show at all on key press, sometimes they don't have the expected behavior('\'+ 'e'= è). They do work on some applications though, like here on firefox. How can I make they all work as expected in all applications ?

I am currently working to create a specific greek keyboard layout adapted to French Swiss Keyboard, I create a keyboard layout to be put to /usr/share/X11/xkb/symbols/( https://github.com/grecromand/grecromand/blob/master/linux/grecromand) . I used code `dead_grave. But I would like to create my own dead_xx. It would be dead_sigma which would produce a ς if followed by space or ponctuation mark, and σ` otherwise. I Have understood that dead_key are defined in /usr/share/X11/locale but not more. I have so many question: - WHich file should I modify? Is it possible to create this dead_key without modifiying distributed files, to avoir problem when upgrading my system? - How can I declare this dead_key?

I noticed that on Ubuntu 20.04, some dead key combinations act differently than expected. For instance, dead acute followed by c produces ç, not ć as one might expect. I have found the keyboard layout definitions at https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/ (and submitted some merge requests for unrelated changes), but could not find any definitions for dead key combinations in that repo. These combinations appear to be global (i.e. not bound to a specific layout), as the dead acute behaves the same way on different layouts, e.g. de(deadtilde) and lt(us). Where are the definitions for the dead key mappings on the system? Where is the upstream source repository?

I recently tried Debian Buster with KDE Plasma 5 and I noticed a cool feature which I'd like to have on my current distribution. I use a US international keyboard with dead keys layout and, with Debian, as soon as I press a dead key (such as ` or '): > the diacritic is displayed, along with an indication that the system is waiting for another keystroke to complete the typing sequence. (to quote Wikipedia's Dead key page ) I took a screen recording to let you better understand what I'm talking about: Do you know if this is an exclusively Debian feature? Is there any way I can have it on any other GNU+Linux distribution?

I am trying to have a clean configuration for my keyboards and layout. I want to be able to switch between FR layout and US international layout with dead keys. When I switch using the GUI it works well, except that the dead keys doesn't working within QT applications. In other words, it works for Firefox and other non QT apps, but not for the majority of the programs I use since I am with KDE. Thanks to [this link](https://bugreports.qt.io/browse/QTBUG-25360) I realized that when in a qt terminal, $LANG is always set to ia_FR.UTF-8. If I manually change that (put it in my .bashrc) or by running application prefixing them like this:LANG=en_US.UTF-8 kmail it works. Then, where LANG is defined by the OS? why QT apps and GTK apps seems to not behave the same?

The US International keyboard allows to add diacritics by means of dead keys. Specifically: ` a`` maps to à and 'a maps to á. In X, using the international or the standard US keyboard, I would like instead to set mappings like this: `a `` maps to á and a' maps to à. As you can see, I would like the dead key to be typed after the base letter and also I prefer to swap the acute and grave accent dead keys. (This makes typing much faster and natural for me and, in case the dead key functionality is disabled, words with attached diacritics are more readable). Can you address me to the proper tools/config files to achieve this? In case it is relevant to the answer, my distro is Arch Linux.

I'm on Belgian keyboard (/usr/share/X11/xkb/symbols/be) and when I type AltGrù it produces the dead key "acute accent", it waits for another key, o for example, to produce ó. How can I change which character is produced, such that I can do ´ + o = ɔ or anything I want?

I'm from the Netherlands, using Windows' Dutch US-International keyboard layout, where a fair few characters use dead keys (éèëê, times five for every vowel). On Windows, typing an apostrophe with a lowercase r puts 'r; however, typing the same sequence with the US-International keyboard with dead keys in Mint gives me ŕ. This happens for a lot of characters and it's quite annoying when you don't expect it. Is there a keyboard layout that behaves exactly like the Windows keyboard I'm used to? It could be either native or an installable package, I don't really mind.

When I use any variation of English, US international (with dead keys,altGr dead keys or alternative) on my Linux Mint machine I always encounter this behaviour. When I press one of these keys: ' " and then follow them with a 'non-accentable' character like a [ or a b no output comes out at all. Whereas in Windows US-International it would print [ or b. If I wanted to type this I would have to escape each dead key with a space instead of with any 'non-accentable' character. This is annoying when programming (not really, but I trained with the Windows 'Qwerty International' on typing.io and switching back and forth between the systems is irritating). Is there any way to change that so it works like in Windows?

I use several keyboards layouts on a regular basis. Two of which make use of dead keys for French language. $ cat /etc/default/keyboard XKBLAYOUT=us,fr,fr XKBVARIANT=dvp,bepo,latin9 BACKSPACE=guess This morning, after a sudo apt-get upgrade on Debian 9 (stretch), which may or may not be involved in the problem, dead keys stopped working as dead keys (*i.e.* hitting ^ then e produces ^e instead of ê), which makes typing french quite difficult. The new behaviour is persistent after reboot and affects several applications: - firefox - thunderbird - gnome-terminal - gedit - nautilus But **not** VLC or xterm.. what should I conclude? How do I get my dead keys working again in all applications?

How can I configure kmscon to use dead keys? I already have xkb-layout=br in /etc/kmscon/kmscon.conf, but the dead keys don’t work. (' + e gives me e instead of é). The layout seems to have been loaded, since the ç key works. Is it a bug in kmscon or am I missing something?

After setxkbmap fr, dead keys do not work under konsole and yakuake (typing the dead key ^ immediately prints a ^, rather than wait for the next character), while they work in xterm. The font I'm using supports them, and it is possible to input them e.g. in vim using digraphs. Looking for a fix, thanks.

There are ways to configure dead keys in Linux to mimic the behavior they have in Windows ? This document describe how it works in Windows:US-Int'l Keyboard Layout to Type Accented Characters The difference between Linux and Windows dead keys is highlighted in bold: > When you press the APOSTROPHE (') key, QUOTATION MARK (") key, ACCENT GRAVE (`) key, TILDE (~) key, ACCENT CIRCUMFLEX key, or CARET (^) key, nothing appears on the screen until you press the a second key. If you press one of the letters designated as eligible to receive an accent mark, the accented version of the letter appears. **If you press an ineligible key, two separate characters appear.** In Linux when you press a second key not eligible to receive a accent, the first key pressed is lost. This reduce the typing productivity, a lot.

I'm using XIM to have the compose key take into account my ~/.XCompose file (it's the only input method that takes it into account, all the others I tried use hard-coded tables). However, it is breaking the dead keys in GTK and QT application: If in charmap (GTK) I press ^ a, it just prints a. The ^ key is recognized though, as it makes the caret stop blinking while I'm pressing it. In kate (QT), it prints ^a instead (two separate characters). **How can I make dead keys work when using XIM?** --- Here are the relevant environment variables: $ env | grep '\(IM\|XMODIFIERS\)' ECORE_IMF_MODULE=xim QT_IM_MODULE=xim GTK_IM_MODULE=xim XMODIFIERS=@im=none And here is the output of xev when pressing ^ a: KeyPress event, serial 37, synthetic NO, window 0x1a00001, root 0xd9, subw 0x0, time 29204065, (131,637), root:(135,656), state 0x10, keycode 34 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x1a00001, root 0xd9, subw 0x0, time 29204135, (131,637), root:(135,656), state 0x10, keycode 34 (keysym 0xfe52, dead_circumflex), same_screen YES, XLookupString gives 1 bytes: (5e) "^" XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x1a00001, root 0xd9, subw 0x0, time 29204545, (131,637), root:(135,656), state 0x10, keycode 24 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (61) "a" XmbLookupString gives 1 bytes: (61) "a" XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x1a00001, root 0xd9, subw 0x0, time 29204614, (131,637), root:(135,656), state 0x10, keycode 24 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (61) "a" XFilterEvent returns: False