".readahead
" is “Normal” – about 75K on my 13.2 system, about 170K on my Leap system; - "core
" is a crash dump file – something crashed – a software developer can analyse “core” files to determine what caused the “something” to crash.
Unfortunately, if the crashed application is unknown then, the “core” file is completely useless – delete it;
"global.conf
" – not present on 13.2 – also not present on my Leap system – no idea as to why it’s appeared on your Leap system; - "klauncherT21452.1.slave-socket=
" – not present on 13.2 – but, also present on my Leap system – 3 copies.
After stopping the Display Manager (init 3) I did an “unlink” (root permissions) on each of them and the slave sockets didn’t reappear when the Display Manager was restarted.
Of those files, I only see “.readahead”. It has a date about the time that I last rebooted. Yours is far older, and that suggests that it is no longer being used. You can maybe try deleting it.
I don’t have a core file around to test , but in my experience you can use
file core
and that will often tell you the name of the command that crashed.
I moved them all to a temporary directory and rebooted. The were not recreated and I can’t see any related errors in journal. I guess they were leftovers.
So wicked crashed on Oct 25th. That may have been an older version of wicked, before you updated to the latest Leap 42.1 release.
Personally, I would probably ignore this if it hasn’t happened more recently. That is to say, I would not report a bug for it. And then I would probably remove that core file, since it is only useful for bug analysis.