Yes, many thanks to @atelszewski as the squared the crash line which later was patched by @LuckyCyborg (or his friend)

Here was Open-Source moment at its best. ;)

I'm happy to give it another go, but I did see the patch being applied. I can't do much before tomorrow afternoon at the earliest, so hopefully, someone else will have a go and either confirm or deny my result.

I actually hope that I have made a mistake somewhere, but since everything was copied and pasted, and I saw a patch being applied before compilation started, I'm not holding my breath.

Please, can someone else have a go?

--
Pete

ZhaoLin1457 posted patch fixed things. So because after your patch KDE crashed the same as before - it seems you didn't apply the patch. Some step(s) seems to be missed in what you did.

Or there's multiple issues and the patch doesn't fix pchristy's issue.

Perhaps these crashes are related to custom settings. Only way to find out for sure is to run on vanilla KDE - with its default settings. I mean the settings of KDE when user runs it the first time.

New installation is not a vanilla kde ? :=)

Of course it is. But how many reporting crashes run vanilla KDE? If you only upgrade KDE your settings are already present in your home directory.

No matter if you have vanilla or chocolate KDE, let's see what fixes and what not fixes the patch described there:

https://www.linuxquestions.org/quest...ml#post6268077

Please take attention to how you name the files and their paths and remember that you need not only the patch, but also a second file, which makes the integration on Plasma5's SlackBuild.

Also, be warned that the kde.SlackBuild installs/upgrades a package after a successful build of it.

To me, vanilla doesn't mean you have personal settings.
unless you add extra stuff to the things provided by the official repository ... it's still vanilla

Point is custom settings may cause KDE do not crash. This maybe why some users do not witness KDE crashes.

Edit: Besides I don't think we can provide own custom patches. The best is to report to upstream. We don't have maintainers for such things.

Edit: For time being use udisksctl or thunar. To mount. Maybe there is applet on slackbuilds.

I clearly agree

And we report, WHAT?

That the panels crashes when you mount an USB stick, on Slackware?

Did you really believe that someone of them uses Slackware? I do not think so.

We should tell them punctually where we hit the crashes.

Don't ask me. Ask them. I am sure they will explain what to do to obtain some valuable crash report. More work - but once you learn it you will know.

I have no intention to become a KDE/Qt programmer.

In other hand, I for one I have nothing to report, because the Plasma5 works perfectly on my boxes.

Perhaps another simple solution is to grab code of last working version and compare with this one. No changes would indicate problem is somewhere else.