You are not logged in.
localectl now shows this after setting the keymap:
System Locale: LANG=fr_FR.UTF-8
VC Keymap: us
X11 Layout: us
X11 Model: pc105+inet
X11 Options: terminate:ctrl_alt_bksp
Still the same issue...
Offline
According per wiki try deleting ~/.config/plasma-locale-settings.sh
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
Sadly, I already saw this in the wiki
Just removed it again, rebooted, with no succes.
Offline
Ugjka,
look what I just found. I never thought it could be KDE Plasma related.
https://forum.kde.org/viewtopic.php?f=66&t=125083
Edit: It doesn't look like eaxctly the same but close.
Last edited by johan.cb (2017-08-20 17:35:48)
Offline
Edit: something wrong
Last edited by ugjka (2017-08-20 17:50:10)
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
We actually may have goten closer.
Now my AltGr key which I used to append accents to letters is not working anymore. But I don't get any "question mark character".
Offline
Well I don't know seems like localectl condenses everything to LANG=fr_FR.utf8 when I try
localectl set-locale LANG=fr_FR.utf8 LANGUAGE=fr_FR.utf8 LC_ADDRESS=fr_FR.utf8 LC_COLLATE=fr_FR.utf8 LC_CTYPE=fr_FR.utf8 LC_IDENTIFICATION=fr_FR.utf8 LC_MEASUREMENT=fr_FR.utf8 LC_MESSAGES=fr_FR.utf8 LC_MONETARY=fr_FR.utf8 LC_NAME=fr_FR.utf8 LC_NUMERIC=fr_FR.utf8 LC_PAPER=fr_FR.utf8 LC_TELEPHONE=fr_FR.utf8 LC_TIME=fr_FR.utf8
the previous command was incorrect
Last edited by ugjka (2017-08-20 17:59:13)
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
Back to the same result, now I have the question mark character again.
Thanks for your help by the way!
Offline
Ok try something weird
localectl set-locale LANG=C LANGUAGE=fr_FR.utf8 LC_ADDRESS=fr_FR.utf8 LC_COLLATE=fr_FR.utf8 LC_CTYPE=fr_FR.utf8 LC_IDENTIFICATION=fr_FR.utf8 LC_MEASUREMENT=fr_FR.utf8 LC_MESSAGES=fr_FR.utf8 LC_MONETARY=fr_FR.utf8 LC_NAME=fr_FR.utf8 LC_NUMERIC=fr_FR.utf8 LC_PAPER=fr_FR.utf8 LC_TELEPHONE=fr_FR.utf8 LC_TIME=fr_FR.utf8
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
Still the same sadly
Offline
I'm lost, hopefully someone smarter will chime in
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
Just a sanity check, but what is your keyboard layout in current DE?
I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.
Offline
Thank you very much for your help Ugjka!
I have three keyboard layout:
-FR (France)
-DE (Germany)
-US (English, Macintosh)*
*the layout I am using at the moment. But I have the same issue with the other two.
Last edited by johan.cb (2017-08-20 18:47:36)
Offline
More information:
I think my bug it Qt 5 related. Qt 4 and GTK applications don't show this issue. Qt 4 designer behaves like it should, like VLC for example too but Qt 5 Designer fails.
If you guys could help me confirm this, I will report it upstream.
Offline
Thank you very much for your help Ugjka!
I have three keyboard layout:
-FR (France)
-DE (Germany)
-US (English, Macintosh)**the layout I am using at the moment. But I have the same issue with the other two.
Last thoughts what happens if you uncomment also de_DE and en_US locales in locale.gen?
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
Hello ugjka,
no change.
I reported the bug upstream in the hope it is Qt related. I will update this thread if I get more input.
https://bugreports.qt.io/browse/QTBUG-62627
Last edited by johan.cb (2017-08-21 20:41:20)
Offline
If you change the user's ~/.xinitrc back to starting the default twm + xclock + xterms that should eliminate qt as a factor.
Offline
This topic was the solution : https://bbs.archlinux.org/viewtopic.php?id=214763
Removing .cache solved the issue on both my systems.
Thank you all for your help. Marking as solved.
Offline