Starting a new thread so as not to mess up latest-kernel (original post #5670). Built 6.4.2 and KDE still has problems. As SCerovec had suggested in the latest-kernel thread (post #5679) I finally found some time to play a bit and tried running kde logged in as a new user while booted to 6.4.2. As a new user KDE appers to run fine so clearly there is something in my KDE user config files that is messed up. So far in trying to figure out what is messed up I renamed the .kde directory (in $HOME) to .kde-save and that had no effect. Not even running KDE on 6.3.12 that I am booted to now. Can anypne suggest what I might try to change to get KDE to run as my user with kernel 6.4.x? Thanks for any help.

I would try backing up and recreating the ~/.config directory as well, as KDE config files are located there as well. If that were successful, either narrow down further which sub-directories are problematic or if it's not an issue, use the new ~/.config directory.

The Plasma5 keeps its data on the folders: ~/.config and ~/.local , also some of its temporary files are kept on ~/.cache

For a "fresh" experience you should (re)move all of these 3 folders from your user account home.

The ~/.kde folder was used exclusively by the KDE4, so its removal has no effect for Plasma5.

2 members found this post helpful.

lol - it's scattered all over the place now.

.kde does have a small amount of files in it too so prob want to delete that.

And also keep an eye on /tmp - I had KDE go crazy on me a few weeks back.

I hadn't changed any settings but it was acting stupid.

I have a .zip file which contains .local, .config, & .kde. I exited KDE to command line and unzipped the backup. It was still acting stupid. I can't remember what I deleted in /tmp but there was garbage there.

Once you've got things the way you want do something like

zip -r dot.kde-settings.zip .local .config .kde

You'll need it eventually.

I'm going back to KDE4. I've found no benefit of using 5 at all. It just pisses me off.

1 members found this post helpful.

At run level 3 I commented out (labeled them as -save) everything in .config and .local that had "plasma" in their name. Also deleted everything with "plasma" in name in .cache. Reboot and still same problem with KDE. xfce runs fine which I am using now with kernel-6.4.2. Maybe my new favorite DE is xfce. Still can't understand why KDE runs great with any kernel-6.3.x and coughs blood with 6.4.x. If I go back to 6.3.x KDE runs fine with no changes at all to the system. All the same plasma files that don't like 6.4.x.

Edit: Forgot to add that when I boot 6.4.x to run level 3 there are two added lines just before the login prompt (that aren't there with 6.3.x) -

Okay, that's kind of odd, and makes me think something else is going on besides KDE and 6.4. (Are there any bug reports on the kernel mailing list about KDE and 6.4? It's not supposed to break user space, the full email I can't quote in a family-friendly area. )

There have been about 3-4 packages added to slackware-current in the past 6 months or so. Are you missing one?

Have you edited files in /etc/rc.d? Like added something in rc.local?

Yes, I check for updates every morning before I change to run level 4. There is a poltergeist somewhere

Honestly, I for one I believe that if when using slackware-current, each time is updated the KDE Frameworks or KDE Plasma, one should start with a clean user home. This way I do and never I had problems like the one described in this thread.

Probably this idea will look disappointing for many, BUT you should NOT use -current for daily drive, right?

Then probably the best thing will be to learn to build your own KDE4 packages.

Because @BrunoLafleur does not offer binary packages for PBSLACKS and regarding myself, considering the place where I live, even I have the intention to maintain the kde4town for the foreseeable future, many things may happen suddenly with ending of me being in impossibility to make these kde4town packages public to the Slackers from this forum.

1 members found this post helpful.

I can handle this part ;-)

2 members found this post helpful.

To me it seems very odd that upgrading a kernel would break a userspace application like fortune.

The fortune command /usr/games/fortune comes from the bsd-games package. Did you for some reason remove that package when upgrading the kernel?

The /usr/games/fortune program should be found as /usr/games should be part of your PATH, it is set by the file /etc/profile.

Try the following:

Shoule give something like:

Then try:

which should give something like:

And finally try:

Which should give something like:

The above is on Slackware 15.0, you might get different time stamps and versions if you are running current.

Once we can understand why a simple program like fortune has stopped working we might get a clue why a complex system like KDE has stopped working.

regards Henrik

But why fortune and some X client were launched "just before the login prompt" of runlevel 3? I could understand it just after giving username and password, because only then a login shell would be launched, and .profile or .bash_profile would try to run fortune and some X program, not able to open display with no X server.

I read the other day that the government tested disconnection from global web. Do you think it's going to happen for real anytime soon?

In fact, they did tests like this since years ago.

Sincerely, I have no idea.