For the sake of getting this issue fixed by the KDE devs, why are you refusing to just try and create a new user on that system? It is just a method to rule certain things out.
There are a lot of Plasma users over here, including myself, who don’t have that issue.
Again, without sharing any logs, nobody, including the KDE devs, can help you.
2 Likes
They have shared the logs here
But yes we can not help unless what is being suggested is tried
Okay, so
I’ve created a new gist for logs: https://gist.github.com/ThursdayTG/088eb9f80e7d63db920ad5042d5fbef7 (I’ve prefaced each file with a number in chronological order, primarily because of the excessive length of eos-log-tool.logs)
- eos-log-tool.logs now is a file that contains absolutely everything that eos-logs-tool offers, I hope that isn’t too inconvenient
- I’ve got the output of Konsole in there as well (konsole.txt), notably after I’ve installed drkonqi, a KDE program that is meant to be helpful for cases like these, namely via creating crash logs
- speaking of drkonqi, I’ve included its logs of the two instances of Kate I’ve ran, although that will probably be more relevant to KDE devs specifically
What I’ve done is reinstall EndeavourOS from scratch on my laptop again, try to run kate (from Konsole) and go to Settings > Configure Kate ... as per usual, then I tried to run kate --new-session, which did absolutely nothing (kate: Unknown option 'new-session'), and then I’ve set up a new user and ran kate from there, which seemingly didn’t change anything whatsoever.
I don’t know if this needs to be mentioned, but kate-20220520-003253.kcrash is the one from the first user, and kate-20220520-003456.kcrash is the one from the second user.
Also, to explain why I didn’t try to run this with a new user: I simply did not (and still mostly do not) understand why that would be relevant when Kate segfaults from a complete fresh install, primarily because I do not understand how that would be in any way at all different.
*Oh btw, I’ve also tried to see what happens if I install EOS in a VM on my main machine where Kate does work. In that VM, Kate died to the same thing as well. I didn’t bother with logs in that case, though, partly because I’m not sure whether logs of a basic VM would be any useful.
Are you keeping the same /home/.config file?
I have no issue with kate.
Started from the terminal.
Started from the menu.
I also have zero issues with it and I use it daily, I’ve also installed in a VM and no issues there either.
2 Likes
@ThursdayTG
Are you using Wayland?
I am getting this particular problem with complete fresh installs without modifying anything at all whatsoever.
And as I said, Kate still does work just fine on my main system, and also the system I have currently installed on my school’s computer, each installation being a few months old. And Kate runs on the latest stable release on both of these systems. This issue somehow only seems to appear on completely fresh installs of entire OSs.
That is interesting.
Just to make sure, you have tried to open the “Configure Kate …” menu in your VM, right? Because it’s only at that point where I’ve seen Kate go wrong lately. Apart from that, it is still perfectly usable for me.
Negative - never have used it, and I probably never will use it until it is the default of whatever distro(s) I’m using. The only distro I’ve ever tried that I know uses Wayland by default is Fedora, and I’m not even actively using that.
Well i don’t believe the issue has anything to do with the ISO. We have lots of users that do not have any problem with kate. 
2 Likes
Ok I was just able to crash kate on a fresh install in a VM
2 Likes
Same here. Selecting “Configure Kate” crashes, same as OP reports.
1 Like
What I did after installing was open kate and kate crashed.
I then updated the sytem and tried again same result.
I then went through the settings and changed them to how i had it set on my machine and i was able to open it
If it was the first thing you did (starting kate etc) on a totally a fresh install, it wouldn’t make sense to create a second new user. The first one is already new. So no relevance.
I have a feeling it will be either the theme or the animation,
I’m going to do it again but go through and change each setting one by one til I find the culprit
1 Like
What is it you are configuring on kate. That is something i have not done.
1 Like
@pebcak
What does this mean? I lost face? 
2 Likes
Launching Kate via terminal gave messages about missing hunspell, aspell, hspell, and voikko. So I installed them:
sudo pacman -S hunspell hunspell-en_us aspell hspell libvoikko
Kate no longer segfaults, and the terminal output is clean.
2 Likes
I had to maximize the window. But after maximizing if i returned it to its original size i was able to open it
Everybody konfigures kate.
Mine makes me Koffee in the morning!
1 Like
I did a fresh install on a laptop yesterday and Kate is working fine.
2 Likes