After upgrading my Tumbleweed from snapshot 20191124 to snapshot 20191202 (I skipped several snapshots in between), my input method, fcitx, goes wrong. The letters and numbers on the candidate-words panel are displayed in code instead of symbols as shown in following picture. https://i.imgur.com/SMM6DCH.png
I tried to create a new user and switched to it. The problem is the same. But if I boot from the old read-only snapshot created by BtrFS, the problem goes away.
Any idea what is the problem and how to correct it? Is this a bug or just something go wrong while I upgrading the system?
Thank you for the hint, Paul. I know a little about font. The same symbols in other parts of the system are displayed normal. I have no idea what font should be provided for the pop-up menu of fcitx but alphanumeric symbols should be included in most of the fonts available in a system. Am I right? The symbols I have not commented out are numbers and ‘.’.
Yes, I would certainly expect all (text) fonts to contain the basic alphanumeric symbols.
I can’t really suggest anything useful.
Does fcitx have any setup options where you’re able to choose a font? Maybe try a different one if it does.
You didn’t skip too many snapshots. Take a look at (YaST2) “Software Management -> Extras -> Show History” to see what updates took place, perhaps find a clue there as to what package update may have caused the issue.
It seems that fcitx is hosted over on github, you could raise an issue there, even if it’s not a bug per se you might get a pointer as to the likely cause.
try changing the global default font for gtk applications:
(KDE) System Settings -> Application Style -> GNOME/GTK Application Style - Font
“noto sans” is a good choice, even if currently set to that, change to another, apply, then change back to not sans, apply. (KDE will rewrite the gtk font config)…
Inspired by the previous suggestion, I checked the fonts preference in my system. Surprisingly, I found that “Nimbus Sans L” was set as the top priority. I had set “Open Sans” as the top priority for my user account at least. That’s for sure. And I have checked my ~/.config/fontconfig/fonts.conf. “Open Sans” is at the top.
Then I checked the root. “Nimbus Sans L” was also set as the top priority. I don’t understand and don’t know how to demote it so I disabled this font family in the Font Management. Now, the problem solved, although, I still don’t know what caused it.
Well, me neither :\ … but, all is working again, so a reasonable outcome.
As an aside, I don’t have any “~/.config/fontconfig/fonts.conf” files on my systems here, so not only do I not know what modified yours, I’ve no idea what created it…
That was created by myself under the inspiration of an online article for customising fonts for current user but keeping system default configuration intact.
