Hi,

I'm running Slackware64-current and after an upgrade-all yesterday, 2017-12-05, I cannot start Konsole or Dolphin after connecting to wifi network.
I get the error message (translated from swedish) "KDEInit cannot start '/usr/bin/konsole'." when trying to start Konsole.
Dolphin just will not start and once the screen saver is on I cannot return to desktop, everything stays black.
Dmesg shows me konsole[2319]: segfault at e0 ip 00007f967960c69a sp 00007ffe1ccf1400 error in libkdeui.so.5.14.38[7f96792a1000+43f000].

Any ideas?

Do you mean that you are still able start to them before connecting to the network? That would be interesting, unusual.

This is standard Slackware, right, no plasma5 or other customisations?

How did you install Slackware64-current? That is, did you do a fresh install from a -current iso or did you upgrade from 14.2 using slackpkg or manually?
Are you, when upgrading, also using slackpkg install-new and slackpkg clean-system?

Hi,

I can start the applications before I connect to the wifi, and they run after I have connected. But I cannot start new instances of them.

It's a standard slackware as far as I know, I haven't done anything to customize KDE.

I upgraded the system manually, by changing the mirror to current and running all the appropriate commands, which I don't remember now since I have only done this once.

I'm not sure I understand your last question but when I upgrade-all I don't run slackpkg install-new and slackpkg clean-system. I think I did so when upgrading to current.

If you want to be following -current, you need to be running install-new and clean-system. -current is Slackware's development branch. It can add and take things away and upgraded programs may rely on those new programs or need the old programs removed to prevent conflicts.

If this sounds like too much work, you would probably be better sticking with the latest stable release of Slackware, which is 14.2 right now. This will continue to have patches released as security issues get found and fixed.

You are absolutely right, and I thank you for your help. I read the manual for slackpkg and tried to do just that after your advice, but it still didn't solve the problem, so I'm switching back to non-current slackware, by reinstalling everything.
The reason I went to current was actually a mistake from my side, and I have no problems following the extra steps that are necessary to be in current. But I feel that I have not knowledge enough to be in current.
I'll leave that work for you experts.

Thanks again for all your answers.