application launcher: double alphabet

Help
1

Hello KDE peeps! first time poster, but have been using kde plasma for a couple of years.

in application launcher - all applications, some new apps go under their letter ( firefox goes under f), but some apps are going under a 2nd of the same letter. example being ‘kitty’ isnt grouped with kate and konqueror, but its under a 2nd “K” that come after Xterm, and so on.

how do i get all apps to be listed under just 1 alphabet?

OS is freebsd. kde plasma is 6.6.4

2

a kind redditor pointed out that the 2nd alphabet at the bottom are lower-case. so ive found the cause, now off to find the solution.

3

Not sure I know what you’re talking about, could you share a screenshot?

4

Ok I found what you’re talking about, here’s a post on reddit from a year ago, what’s interesting is that users are saying that it was fixed since 6.2.5?

It might be a locale issue:

Could you please use locale command in your terminal and share the result?

Relevant reddit post :

5

ive just newly installed 15.1-rc1, and used the kde installer script.

locale
LANG=C.UTF-8
LC_CTYPE="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_TIME="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_ALL=
6

As I suspected you have the C.UTF-8.

In my research of the problem I have found that having C.UTF-8 might be causing the problem since it’s treating ‘A’ and ‘a’ as different. You’ll have to specifically set a locale like en_US.UTF-8.

7

thanks for the reply. i wonder if locale could/should be prompted for during the install process?

8

isn’t that one of the first questions the installer asks?

your location and language?

9

oh shoot i guess it does. ill have to pay closer attention to get it correct.

10

Never had the occasion to install FreeBSD but judging by the fact that it’s UNIX based then setting the locale should have been one of the first things to do, no?

11

im fairly sure i got asked about language and keyboard during install, i just clicked through without considering i might not have got the locale correct.

12

In any case, did changing the locale fix the problem?

13

yes it did, thank you all!