Arch Linux

DeinAlptraum

Member

Registered: 2022-01-21

Posts: 14

[SOLVED] Apps started via krunner have locale / key input problems

Hi there,

I'm running Arch with KDE and I've recently discovered several problems in apps when I launch them via krunner.

So far I've noticed the following:
1. can't type ` or ^ in Telegram (nothing happens)
2. can't type with Japanese keyboard (neither ibus-anthy or ibus-mozc) in various apps, e.g. Kate, Telegram, Anki. It will just use my regular keyboard. Other apps work fine, e.g. Firefox, Discord
3. folders with 'ä', 'ü' or 'ö' in their name are not recognized in Ultrastar Karaoke (after editing out those letters it works)

All of this works correctly if I start the problematic apps directly via the command line.
It also works if I restart krunner from the command line via `krunner --replace`, and then start any of these applications via krunner.

I assume when krunner is started on boot, it doesn't source ~/.zshrc as my console does. At least that would explain why starting things from command line works.
I'd be happy to hear if anyone knows a good way to make krunner source my ~/.zshrc on start up.

If that helps, the only locale-related things I found in my ~/.zshrc were
export LANG=en_US.utf8
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
ibus-daemon -drxR --panel=/usr/lib/kimpanel-ibus-panel

I know I could probably just dirty-hack it by running a script on autostart that sources my ~/.zshrc and then restarts krunner, but I'm hoping there's a cleaner method for that.

Last edited by DeinAlptraum (2022-01-30 12:20:40)

DeinAlptraum

Member

Registered: 2022-01-21

Posts: 14

Re: [SOLVED] Apps started via krunner have locale / key input problems

I feel a bit dumb now, been stuck with these problems for months, but I actually just solved most of them 15 minutes after finally posting here...

Anyway, I just created ~/.xprofile and put the lines I mentioned from my ~/.zshrc in there:

export LANG=en_US.utf8
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus

This fixed problem number 1 and 2.

The only problem that remains is the one with ultrastar where it can't deal with  'ä', 'ü' and 'ö' (and I assume others that I'm not aware of)
No idea where to even start searching with this one, so if anyone has any pointers, I'd be happy to hear them.

Last edited by DeinAlptraum (2022-01-26 22:33:17)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,290

Re: [SOLVED] Apps started via krunner have locale / key input problems

When krunner is "bad":

tr '\0' '\n' < /proc/$(pidof krunner)/environ

And in general

localectl
locale
locale -a
setxkbmap -print -query

How do you start the session? SDDM? startx?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

DeinAlptraum

Member

Registered: 2022-01-21

Posts: 14

Re: [SOLVED] Apps started via krunner have locale / key input problems

I just found the solution to problem No.3

My ~/.config/plasma-localerc looked like this:

[Formats]
LANG=en_DE.UTF-8

This locale does not seem to even exist. I have no idea how it got there in the first place, I do not remember ever editing that file.
(for reference, I have a friend with a fresh Arch + KDE install who had the same problem, so I guess it's indeed a bug)

Anyway, changing this to en_US.UTF-8 fixed problem No.3.
Folders with ä/ö/ü in their names now show up properly even when starting from krunner