Version: (using KDE 4.2.3) Installed from: SuSE RPMs Taken from Novell bugzille, I also see the same issue https://bugzilla.novell.com/show_bug.cgi?id=494665 "Running KDE4 4.2.2, I noticed that $HOME/.kde4/socket-$hostname/ has dozens or hundreds of klauncher socket files (stale). I have 192 on this machine currently. That should not be. klauncher or something should clean up its messes." Thanks for your time =)
the only "klauncher"-sockets i see are klauncherXXXXXX.slave-socket style. these seem to come from kio/kio/connection.cpp. as the object infrastructure should care for the cleanup automatically, i guess that the local server (and its parent object) is not properly deleted, or even that the process is plain killed.
I am cc'ing the reporter from the novell bugzilla. Process killing (or crashed ones) sounds like a valid offender for me, still shouldn't this be cleaned up somewhat? I don't know consequences of these files, so if this is a relevant problem is up to you guys to say =)
the Linux Filesystem Hierachy Standard says that /tmp should be cleaned up by the system both periodically (when files appear stale) and at system boot, IIRC. the stale socket files themselves pose no problem. i.e., no worries.
somebody needs to verify comment #1 and reassign to the crashing component if it applies. as far as klauncher is concerned, this is a WONTFIX as per comment #3.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!