Thank you for the history and for your explanation!
I’ll try to process it, so I’ll hopefully apply it properly in the future!
KDE/Plasma often seem to have their own way of configuring things, different and independent from “standards”.
I know nothing of it - I can’t help you - I don’t use it, except that I have it present in a VM
OK @Nachlese thank you for the good will!
I’ll await input from somebody with deep knowledge of this distribution who can figure out why it’s working fine in Firefox and not any more in the console window or Telegram desktop or LibreOffice Writer (and BTW the latter has been installed the official way, while Firefox and Telegram desktop come directly from their respective websites and haven’t been system-wide installed here, I’ve just extracted their respective trees and I’m calling each one’s executable… and that’s NOT the point apparently given that the keyboard layout works fine with Firefox and NOT with Telegram desktop).
It honestly looks like a bug to me, after having gone through settings and reboots various times.
I mean: whatever files still need to be changed should have been changed. It was fine before, I reverted those settings, it didn’t go back to being fine 
But of course I might be missing something.
[EDIT:] the symbol used for the home folder on the command line is not working either 
The only ostensible difference here is that Firefox is gtk-based while the other applications you’ve listed are all qt-based (as is the Plasma desktop itself). qt and gtk each have their own way of accepting and processing keyboard input.
Linux doesn’t generally have issues with keyboards - but the great variety poses challenges as to select the correct variant.
Use the input text box on the keyboard configuration to deduce whether the expected result is produced.
Select the keyboard matching you expected locale and output.
Different keyboard types exist where the only difference is how to handle dead keys.
You should really go over your configuration - especially since you are using Plasma.
What symbol? The ~ is a symbol which resides on dead key - depending on your layout.
With a Danish Keyboard the symbol takes three keys alt-gr~ then release and complete with singlespace
Thanks for replying!
The only ostensible difference here is that Firefox is
gtk-based while the other applications you’ve listed are allqt-based (as is the Plasma desktop itself).qtandgtkeach have their own way of accepting and processing keyboard input.
How interesting.
Is there a pacman command or other command I could issue to FORCE QT into rewrite its configuration, adopting again the current global system settings of keyboard layout?
Linux doesn’t generally have issues with keyboards - but the great variety poses challenges as to select the correct variant.
No problem at all here in choosing, as I mentioned the keyboard was working perfectly fine before I switched the global language to Spanish Argentina and back to English US.
The correct layout with this keyboard is always Spanish, sometimes called Spanish - Spain, here in the Manjaro Settings Manager it’s called Spanish default, in the KDE Plasma settings it’s called Spanish period.
Use the input text box on the keyboard configuration to deduce whether the expected result is produced.
In the test area of the “Keyboard - System Settings” dialogue the dead keys are NOT working at the moment, they WERE working just fine BEFORE the problem started.
What symbol? The ~ is a symbol which resides on dead key - depending on your layout.
With a Danish Keyboard the symbol takes three keys alt-gr~ then release and complete with singlespace
Exactly that symbol. When the keyboard was working fine, I was getting it exactly the way you described.
Now I can get it by choosing the layout “Spanish (dead tilde)” but it does not require that sequence, the symbol is actually NOT a dead key despite the layout name, it appears with no need of the further singlespace (and the accents dead keys do not work anyways so that layout is not a useful workaround).
[EDIT:] “Spanish (dead tilde)” is working 100% fine here in Firefox, except that this layout name should rather be "Spanish (NO dead tilde).
THIS behavior would be the ideal one, it’s actually the one I’ve been getting for ages with “Spanish - Spain” under Ubuntu + Gnome and with Raspberry PI OS 64 with its default desktop/windows manager (sorry I can’t remember the name right now).
Testing in Firefox:
àèìòù áéíóú ü ï ê
ÀÈÌÒÙ ÁÉÍÓÚ Ü Ï Ê
and the home symbol ~ appears right away with no need for the extra space.
With this keyboard, I mean with this hardware, you don’t need the dead ~ because this layout includes the Ñ key (with/without shift => Ñ ñ). Unless of course you need to write in some language which superposes the ~ character to other characters than N/n.
/etc/X11/xorg.conf.d/00-keyboard.conf
Apparently, this Aug 2021 issue also mentions a necessity to manually edit that file:
(Is this a weak point in Plasma KDE + Manjaro?)
¿Have you tried the “Dead keys” option in the keyboard part of Manjaro Settings Manager? (The one where you have “Default”) You want dead keys…
Another 2021 very interesting thread:
ouch I can’t post the link on this platform (why? I’m clearly not a spammer)
Do I really need to post a picture of the URL? Oh sure I can’t embed media items either!
@admin Can I please be enabled to share URLs and pictures (just as I did in my very first post here)?
EDIT: the URL is (with no spaces) bbs DOT archlinux DOT org SLASH viewtopic.php QUESTIONMARK id=265821
¿Have you tried the “Dead keys” option in the keyboard part of Manjaro Settings Manager? (The one where you have “Default”) You want dead keys…
Thank you. Let me check that out I might have missed it.
The 3rd picture in my very first post here shows how I see the Manjaro Settings Manager, I’m not seeing any specific checkbox or radio-buttons selection about dead keys, just the layout names…
I can’t post pictures any more but I think it is still looking the same, except for the fact that at present the selected layout is “Spanish (dead tilde)” which - as discussed in my earlier post today - should rather be called “Spanish (NO dead tilde)”.
EDIT: if you are referring to the layout called “Spanish (no dead keys)” the answer is YES, I did try with it as well but that’s actually named correctly, meaning NO dead keys anywhere, in gtk apps either.
(BTW, I’ve installed gedit which must be gtk based because it’s reflecting the correct keyboard layout, so I’m able to stay in Manjaro making tests about this problem and still be using Telegram etc., although it’s a bit annoying having to switch all the time to write in gedit and then copy&paste elsewhere. On the contrary, kate must be qt based and the layout is not working with it.)
Finally some sense in the forum software.
This is not an image gallery but a technical forum - searchable and images a not search friendly by any measure.
That said - depending on whether you are using Xorg or Wayland the configurations are read from different places.
I am using Plasma and yes gedit (Gnome Editor) is GTK and Kate (KDE advanced Text Editor) is Qt based.
With Xorg you have a file /etc/X11/xorg.conf.d/00-keyboard.conf which to my knowledge has no effect on Wayland. Exactly where Wayland gets the keyboard from - I am not sure - never had the issue - but I think it is pulled from /etc/vconsole.conf.
This is not an image gallery but a technical forum - searchable and images a not search friendly by any measure.
That’s a limitation.
ABSENCE of images is not searchable either and does not provide any additional information.
I’m not talking about images of kitties or landscapes, I’m talking about screen snapshots of the GUI.
You would get here by searching words, then find the additional information.
The images I was able to include in my first post above here DO provide additional information. I made the effort to include them because most of the other threads I had visited, on this and other platforms, did contain screen snapshots.
And I did not post images without adding meaningful text.
Also, I shared AS TEXT anything which was sharable as such.
(I discussed the URL picture only because I was unable to include the text of one URL locating a related thread on another platform, I finally disguised the URL text.)
You could add guidelines for this forum usage, e.g.:
Please prioritize sharing text over sharing images, whenever it’s doable and it makes sense, e.g.
to share the content of a file or to share a command, and resort to images when it’s potentially useful additional information, e.g. the current state of a settings dialogue or any part of the GUI which might be meaningful to the eyes of other users.
[…] depending on whether you are using Xorg or Wayland […]
echo $XDG_SESSION_TYPE
x11
cat /etc/vconsole.conf 14s
# Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed
# and systemd-vconsole-setup(8). Use localectl(1) to update this file.
KEYMAP=es
XKBLAYOUT=es
XKBMODEL=pc105
XKBVARIANT=deadtilde
cat /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
# update this file.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es"
Option "XkbModel" "pc105"
Option "XkbVariant" "deadtilde"
EndSection
Both look fine as far as I can tell (except for the above mentioned fact that this variant name should rather be “NOdeadtilde”).
So you have a configuration which have a special configuration for X11 and another for Wayland.
That is implied by the X-variant.
I suggest you remove the xkbvariant manually for you configuration files. Then restart your system.
Please look at the excerpt from Manjaro Linux wiki Forum Rules How To Post
Do not post images or screenshots as part of your topic. The forum is a technical forum not an image gallery.
(Sorry I’ve edited my previous post, this page had been relatively low traffic so far, with some time before any answer, and I took the risk to improve my answer while possibly having somebody online on the page.)
So you have a configuration which have a special configuration for X11 and another for Wayland.
Sorry, I don’t understand your reply, I’m reading the same configuration in both of the files which content I’ve just shared, which is:
es, pc105, deadtilde.
The problem is QT, somehow it’s not getting the system configuration.
All GTK software is working fine.
Tried, no result, then I tried with the three files
sudo nano /etc/default/keyboard \
/etc/X11/xorg.conf.d/00-keyboard.conf \
/etc/vconsole.conf
No result, dead keys still perfectly fine in gtk software and not working in qt software.
Also tried locale-gen again, no result.
I’m relaunching the same question.
Basically: changing the system language from en US UTF-8 to es AR UTF-8 and back did not bring back QT to the previously correct way to read the dead keys from the keyboard.
I’d have a few more questions / suggestions about Manjaro with KDE Plasma…
… but I might as well decide to install a fresh new system on this disk, Manjaro with Gnome or another Arch-based distribution. I’ll notify here in case.
Whoever wants to dig in this bug can probably reproduce it anyways on any updated Manjaro KDE Plasma installation.
I’ve just seen this part, noted. I was right now looking at quite a few related threads on this same platform which do include snapshots (that I find useful).
I’d again suggest to this community to reconsider that rule, I’ve made my points in my previous answer about that, I’m not going to reiterate the same concepts (nor to post here anything that in my opinion would be appropriate to document with snapshots).
Regards.
Let me add one more point:
Technical books and web pages are full of pictures.
(I’ve answered above to the second part of your statement.)
Please just consider this as a possibly constructive contribution, I have no spare time/energies for unnecessary polemic on “small” matters. Your platform, your rules, and I have the option to adjust or leave.