Running 42.1 with KDE desktop. When I look in my root directory with dolphin there are a stack of files which I do not understand like this:-
klauncherXM4550.1.slave-socket
Where do they come from, what are they for and can I delete them, if so how?
Budgei2
I’m running 42.2, and not seeing anything like that.
The timestamp on my root directory is Nov 16th, so nothing was written to it more recently than that.
I have mounted my 42.1 root directory to check. The only weird file that I find there is named “.readahead”. I don’t know what put that there, but I assume that I could delete it.
Google and you’ll see what readahead is
ls -l
and show us the full list?
I get these regularly in my home folder. I delete them periodically and have not noticed any ill-affects.
Please show information:
ls -l /
so we can see that it is there and who is the owner, etc., etc.
Can you check if these are generated when you run File manager - Super User Mode or Terminal - Super User Mode?
It could be this issue: https://bugs.kde.org/show_bug.cgi?id=356098
I think you’re right, but we won’t know until the OP has posted the output requested. On my TW install I noticed these files a couple of months ago ( IIRC september ).
Matbe better
ls -l /root
But indeed SHOW something, The only way to avoid confusion and tell facts.
Hi Henk,
Sorry about delay. Been real busy for a while. Here is fuller picture:-
alastair@ibmserver2:/> ls -l
total 0
drwxr-xr-x 1 root root 1776 Dec 6 15:54 bin
drwxr-xr-x 1 root root 1014 Nov 3 15:10 boot
drwxrwxr-x 4 root root 52 Feb 22 2016 data
drwxr-xr-x 19 root root 4080 Nov 28 10:13 dev
drwxr-xr-x 1 root root 5320 Dec 7 15:08 etc
drwxr-xr-x 3 root root 22 Mar 11 2016 home
srwxr-xr-x 1 root root 0 Feb 20 2016 klauncherT10088.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 22 2016 klauncherT11116.1.slave-socket
srwxr-xr-x 1 root root 0 Nov 21 18:13 klauncherT11983.1.slave-socket
srwxr-xr-x 1 root root 0 Dec 7 00:01 klauncherT17374.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 21 2016 klauncherT19388.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 21 2016 klauncherT19490.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 21 2016 klauncherT19703.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 21 2016 klauncherT19814.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 21 2016 klauncherT24174.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 22 2016 klauncherT24618.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 18 2016 klauncherT25877.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 26 2016 klauncherT27105.1.slave-socket
srwxr-xr-x 1 root root 0 Aug 28 00:05 klauncherT27133.1.slave-socket
srwxr-xr-x 1 root root 0 Nov 20 23:54 klauncherT28469.1.slave-socket
srwxr-xr-x 1 root root 0 Nov 21 00:04 klauncherT28647.1.slave-socket
srwxr-xr-x 1 root root 0 Nov 21 00:17 klauncherT28859.1.slave-socket
srwxr-xr-x 1 root root 0 May 3 2016 klauncherT29777.1.slave-socket
srwxr-xr-x 1 root root 0 Mar 8 2016 klauncherT30915.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 22 2016 klauncherT31450.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 20 2016 klauncherXM4303.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 20 2016 klauncherXM4550.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 14 2016 klauncherXM7186.1.slave-socket
srwxr-xr-x 1 root root 0 Feb 20 2016 klauncherXM7402.1.slave-socket
srwxr-xr-x 1 root root 0 Sep 4 23:23 klauncherXM8163.1.slave-socket
srwxr-xr-x 1 root root 0 Dec 3 16:42 klauncherXM8974.1.slave-socket
srwxr-xr-x 1 root root 0 Jul 20 18:33 klauncherXM9734.1.slave-socket
drwxr-xr-x 1 root root 2822 Nov 18 18:47 lib
drwxr-xr-x 1 root root 5330 Dec 1 16:51 lib64
drwxr-xr-x 1 root root 0 Sep 30 2015 mnt
drwxr-xr-x 1 root root 0 Sep 30 2015 opt
dr-xr-xr-x 300 root root 0 Nov 28 10:07 proc
drwx------ 1 root root 228 Dec 7 10:23 root
drwxr-xr-x 32 root root 940 Dec 6 16:42 run
drwxr-xr-x 1 root root 4818 Dec 2 23:35 sbin
drwxr-xr-x 1 root root 0 Sep 30 2015 selinux
drwxr-xr-x 1 root root 34 Feb 19 2016 srv
dr-xr-xr-x 12 root root 0 Dec 3 15:08 sys
drwxrwxrwt 1 root root 13818 Dec 7 15:11 tmp
drwxr-xr-x 1 root root 130 Jan 12 2016 usr
drwxr-xr-x 1 root root 124 May 21 2016 var
alastair@ibmserver2:/>
Will now try Knurpht suggestion as I think he has it.
Hi and thanks for this. Seems like you are correct. I deleted them all and then ran Dolphin in Super-User mode and here is my root directory now:-
alastair@ibmserver2:/> ls -l
total 0
drwxr-xr-x 1 root root 1776 Dec 6 15:54 bin
drwxr-xr-x 1 root root 1014 Nov 3 15:10 boot
drwxrwxr-x 4 root root 52 Feb 22 2016 data
drwxr-xr-x 19 root root 4080 Nov 28 10:13 dev
drwxr-xr-x 1 root root 5320 Dec 7 15:08 etc
drwxr-xr-x 3 root root 22 Mar 11 2016 home
srw------- 1 root root 0 Dec 7 15:19 kdeinit5__0
srwxr-xr-x 1 root root 0 Dec 7 15:19 klauncherT24249.1.slave-socket
drwxr-xr-x 1 root root 2822 Nov 18 18:47 lib
drwxr-xr-x 1 root root 5330 Dec 1 16:51 lib64
drwxr-xr-x 1 root root 0 Sep 30 2015 mnt
drwxr-xr-x 1 root root 0 Sep 30 2015 opt
dr-xr-xr-x 285 root root 0 Nov 28 10:07 proc
drwx------ 1 root root 228 Dec 7 15:19 root
drwxr-xr-x 32 root root 940 Dec 6 16:42 run
drwxr-xr-x 1 root root 4818 Dec 2 23:35 sbin
drwxr-xr-x 1 root root 0 Sep 30 2015 selinux
drwxr-xr-x 1 root root 34 Feb 19 2016 srv
dr-xr-xr-x 12 root root 0 Dec 3 15:08 sys
drwxrwxrwt 1 root root 13818 Dec 7 15:19 tmp
drwxr-xr-x 1 root root 130 Jan 12 2016 usr
drwxr-xr-x 1 root root 124 May 21 2016 var
alastair@ibmserver2:/>
There is a new file of the subject type with current time and date so that confirms it to me.
What I am not sure about is that even if these files were written into the tmp directory they would still be persistent. I wonder why only some people have this problem.
Anyhow thanks for the answer to my question. I will not spend any more time on it as it is no big deal. Hopefully the bug will be fixed in due course.
Regards,
Budge
Actually that should only happen if you run things as root, and it’s a long standing bug in KDE that has been fixed recently (by openSUSE, btw 
), in time for the 42.2 release IIRC.
In earlier times (KDE4) the files just didn’t go to / directly but were “hidden” somewhere (e.g. /.config) .
This is fantastic news, I just checked and they don’t appear on up to date Tumbleweed. Great work, whoever fixed that bug!
I can confirm that it no longer occurs on TW either (which had been afflicted as well, as mentioned earlier in the thread, and observed by me too). So yeah!rotfl!