koffeinfriedhof wrote:I'm very patient with other peoples problems

Did you try pressing ~ and then space in case you activated the dead key stuff? (Sorry, but sometimes the simple things are an idea).

Besides my custom geometry and keyboard layout, did you notice differences between my output and yours? I need more input

Yup, can't make any of the special characters like ẽ either. it results in a space and a normal key, so " e" instead of "ẽ"

I think i found what the problem is. I didnt map en_SE to a compose file in /usr/share/X11/locales. I appended "iso8859-1/Compose: en_SE.UTF-8" to the bottom of /usr/share/X11/locales/compose.dir, but now it fails to parse iso885n-1/Compose

Code: Select all

xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:39:34: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:40:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:41:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:42:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:43:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:44:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:45:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:46:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:47:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:48:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: too many errors
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: failed to parse file


Hi!

I have not much more ideas here. I didn't need to set up anything besides the already mentioned things. Do you have a compose key defined and use it?

I had the same problem when I enabled the accented/alternative character input. It's this smartphone like feature when you longpress a letter, a small window with character options pops up. In order for that to work I had to set the QT_IM_MODULE in /etc/environment. It worked but a bunch of characters didn't. ~ was one of them. I removed the module. Btw, Flemish/Belgian azerty layout. Anywho, came across this: https://bugs.kde.org/show_bug.cgi?id=411729